> Am 28.04.2025 um 13:31 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > Dear P.O., > > On 27.04.2025 22:54, P.O. Jonsson wrote: >> Tomorrow I will review those part related to the release process that I need >> to do, With the script I have developed much of the release process will be >> more automated but not completely. > Which parts of the release process does your script cover? Or with other > words, which steps in the release-steps.md need to be adjusted? > It will do everything from the point where a release candidate (with all the necessary footwork and files that belong to the release) is put in place BUT there is still a lot of manual work around it. I think I could maybe talk about that during the Symposium, walking us through all the steps. > Once this is clarified we should be set for starting the release process by > creating the branches for main, docs and tests. Then updating updated > release-steps.md in the new branch "main/branches/5.1.0", after which we > should execute the release-steps.md one by one. > Bear with me a little bit more, I have other obligations today, I will let you know. >> I think that is not really possible. Also, all the work made by Rick for the >> 5.0.0 release will still need to be done manually (release notes and other >> documents as well as closing tickets etc). > +1 >> Question: should we revise all the documentation (including the copyright >> etc) and build a fresh copy on the day of the release? Or do we just take >> what we have until now? > Hmm, I would suggest (after having created docs/branches/5.1.0) to revise and > build the documentation using the day of the release, which I suggest to be > set to May, 4th, 2024 (the first day of the symposium). The building itself > should be done by Thursday midnight such that the test suite can run against > it. > I have not foreseen to actually run the test suite against the release candidate, the script can deal with switching the building but to change also all testing will take some time for me to do. That is another 20+ xml files to parse & change without breaking anything. > Cheers > I am not able to do the release next week, I need to be in front of the computer here in Berlin, it is much more manual work than you think and I need to have physical contact to my machines while doing so.
I suggest you call me tomorrow and we can talk about how to proceed. > ---rony > > > >> >>> Am 27.04.2025 um 22:02 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at> >>> <mailto:rony.flatsc...@wu.ac.at>: >>> >>> The documented release instructions for 5.0.0 can be found in >>> "main/trunk/release-steps.md", the "tools" directory is in >>> "docs/trunk/tools". >>> >>> It would be nice if everyone would look through it and check whether there >>> are changes needed (other than changing 5.0.0 to 5.1.0 and the like) and >>> post any remarks, feedback. >>> >>> ---rony >>> >>> P.S.: Also, after the 5.1.0 release (and after the symposium) it would be >>> nice to assess whether it is possible to fully automate the creation of a >>> release for future releases. >>> >>> > _______________________________________________ > 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
