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):
<!ENTITY PRODUCT "Documentation"> <!ENTITY BOOKID "ooRexxBuild"> <!ENTITY YEAR "2005-2023"> <!ENTITY HOLDER "Rexx Language Association. All rights reserved."> <!ENTITY VERSION "5.1.0"> <!ENTITY EDITION "2023.01.01 (last revised on 20221220 with r12560)"> I guess that should also be amended? Can that be done by your script? Since I ran the program from within the work area I also got an update in updateCopyright.rex itself, I guess that should be excluded? Do you want to amend that script before I go along? I will try to make a list of documents where a manual intervention is needed and add it to the release documentation after the release. Unfortunately I will be AFK most of the day tomorrow afternoon so I cannot respond to any urgent business until late in the afternoon. Just a heads-up. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se > Am 29.04.2025 um 19:24 schrieb Gilbert Barmwater <gi...@bellsouth.net>: > > 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 legal.ent also in that folder. I > have recently updated the .ent file to reflect 2005-2025 for the date range. > Any other documents that DON'T use Legal_Notice will need individual changes. > > Thanks, > Gil > > On 4/29/2025 12:43 PM, ooRexx wrote: >> 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/ (exactly as that) and same for documentation and >> testing. >> >> If there are objections to that (we did it slightly different in 5.0.0) I >> need to know since this will have to be modified in the “switching” script I >> have done. >> >> I have taken a complete backup of all jobs so I am ready to carry out my >> part of the work, once there is a release candidate in place. >> >> I have attached the list with steps I need to perform during the switch just >> to give you an idea of the many manual items still. Not complicated but >> tedious. After this release we might merge this list with release-steps.md >> (or keep it as a separate item). >> >> >> >> >> >> Hälsningar/Regards/Grüsse, >> ooRexx >> oor...@jonases.se <mailto:oor...@jonases.se> >> >> >> >> >> >> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- > Gil Barmwater > _______________________________________________ > 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
