Richard Brooksby

> tho im running on COOL build, ill try RASH build Please let us know if you are seeing a significant difference between HOT and RASH. The RASH build only...

The PowerPC platform was removed in Perforce changelist 178908 on 2012-08-12 which corresponds to Git commit 9e1492305021f675f0beb45b5dec99dbe97f94dd . You can see there what was removed. The changelist resolved these issues:...

Please do ask questions here if you decide to hack on this. We'll try to answer, though our resources are limited.

GCC 13.2 applied as shown in https://github.com/Ravenbrook/mps/issues/256#issuecomment-1712843937 still produces the error in #256 .

We need to ensure the original problem is tested by CI. See #258 or possibly we can use some other "latest" environment.

I'm also wondering where the word "testbench" came from and whether it means anything specific. I think @thejayps introduced it.

The split between MMQA (see also #116 ) and other tests definitely needs tidying.

We should also examine the Python programs related to branch and release procedure: - [tool/branch](https://github.com/Ravenbrook/mps/blob/0d071c0af272a5c323cfd2277b2d6518f4e1f1b2/tool/branch) - [tool/release](https://github.com/Ravenbrook/mps/blob/0d071c0af272a5c323cfd2277b2d6518f4e1f1b2/tool/release) - [Search for others.] Unfortunately, it may be best to delete these if...

The new procedure must ensure the relevant version of the manual is built, published, and linked. See #141 .

> The version-create procedure currently assumes that there is an up to date plan or list of requirements We could bring https://www.ravenbrook.com/project/mps/plan/ in to the repo. See also #95.