Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se
> Am 15.12.2022 um 09:00 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > Thanks to Rick we got the version information updated in trunk > (<https://sourceforge.net/p/oorexx/code-0/12539/> > <https://sourceforge.net/p/oorexx/code-0/12539/>). > > Todos: > > add "#define REXX_INTERPRETER_5_1_0 0x00050100" to trunk's api/oorexxapi.h > > on Sourceforge create "files/oorexx/5.1.0beta" to receive the new builds from > trunk > > change branches/5.0.0 such that release builds > > set debug to .false in .rexxinfo > > and "rexx -v" does not append the string "- Internal Test Version" to the > first line > > on Sourceforge create "files/oorexx/5.0.0gamma" to receive the new builds > from branches/5.0.0, this directory will be removed before producing the > final release installation packages for which then the directory > "files/oorexx/5.0.0" gets created and staged for three days such that the > developers can test the location and prepare supporting materials like list > of changes since the last release, announcements and such If can rename 5.0.0.Beta to 5.0.0 already now, is that a problem? I will amend the scripts to upload there until we have a new beta. I do not know how to „Stage“ it, if I rename it the change will be visible automatically. I can put a text warning in there until it is an official release though. 5.0.0Gamma sounds weird, I never had a software in „Gamma“. Why not simply call it 5.1.0alfa (or beta), this is where the rolling version will go once the version in 5.0.0 is frozen. > > ---rony > > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
