On 15.12.2022 11:00, P.O. Jonsson wrote:

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/>).

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

      o set debug to .false in .rexxinfo

      o 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.

Staging seems to be only possible when creating a new folder entry. So we would need to delete the existing folder and create it again to gain the staging.

5.0.0Gamma sounds weird, I never had a software in „Gamma“.

Alpha would be misleading as that phase comes before the beta phase which we are leaving for 5.0.0. Using "gamma" comes from the 90ies I guess and it would follow the greek alphabet alpha -> beta -> gamma which actually would be actually ga (general available) [1]. But if it is irritating, misleading, we can just use a name likde "5.0.0tmp" indicating a temporaray directory.

Once everything is set and placed into "5.0.0tmp" we could rename it to "5.0.0" indicating the official release folder.

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.

This would be the folder for the trunk version. We should *never* mix the 
release and the trunk version!

Or with other words: the production from trunk should go to "5.1.0beta" ASAP.

[The production for the release 5.0.0 version should go to a different folder, maybe named "5.0.0tmp" as suggested above and if the release notes got prepared rename it to "5.0.0" (no addition indicates a general available, a release version.]

Would that be o.k.?

---rony


[1] https://en.wikipedia.org/wiki/Software_release_life_cycle
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Reply via email to