Re: [Oorexx-devel] Release preparations for ooRexx

2025-04-29 Thread Gilbert Barmwater
P.O., I think updateCopyright.rex was written by Rony IIRC.  The change I made was just a commit of a (manually) updated legal.ent.  If I have time tomorrow, I will look at that script and report what I find. Gil On 4/29/2025 3:08 PM, ooRexx wrote: Hi Gil, Thanks for the explanation, I did

Re: [Oorexx-devel] Release preparations for ooRexx

2025-04-29 Thread ooRexx
Hi Gil, Thanks for the explanation, I did run the updateCopyright.rex and found that there was no update in ooRexxBuild.ent (there are 16 of them, that I found at least): I guess that should also be amended? Can that be done by your script? Since I ran the program from within the work a

Re: [Oorexx-devel] Release preparations for ooRexx

2025-04-29 Thread Gilbert Barmwater
Hi P.O., Just a small note re. the copyright notice in the various books. For books like RexxRef, the line Copyright © 2005-2024 Rexx Language Association. All rights reserved. is generated from the Legal_Notice.xml file which is in the "common" folder "oorexx" and which uses the entity file

[Oorexx-devel] Release preparations for ooRexx

2025-04-29 Thread ooRexx
Dear all,as you might have noted I have revised the release-steps.md document to reflect 5.0 -> 5.1 to the best of my knowledge.I propose that we follow the strategy from version 4 releases and put a release candidate in main/branches/5.1/trunk/ and that we release it in main/releases/5.1.0/trunk/