On Tue, Dec 3, 2024 at 02:42 Dave Wade via <dave.g4ugm=[email protected]> wrote:
Not sure where we are! We lost the person who built the last
version, so there is a bit of a void
It might help future releases if the person who leads this one puts together a checklist of the tasks that go into releasing VM/370.? As a newcomer to retrocomputing, I know I lost quite a bit of time to the fact that the GCCLIB DCSS hadn't been saved in VM/370 CE 1.2. ?(I'm not complaining, just noting it as something even long-time VMers like me wouldn't know to do.)
but I think we are getting to
the stage where there is enough new stuff for another release.
I'm going to sign out a bunch of CMS update numbers, and package the fixes I've posted to the GitHub issue tracker, so they can get into the next release.? And for my RXSYSFN as well.
I was waiting for EE to get to a stable state before plugging
ahead....
I'll be off the grid for the next few weeks, but I expect to release a second beta of bREXX 1.1.0 before EOY, or possibly even Christmas.? There has been one reported bug against the first beta, and in fixing it, I found another related to it - both side effects of supporting the FAILURE condition, but only affecting the TRACE facility.? Absent complex bugs, bREXX will be ready before the end of January.
