> On 1. Jan 2023, at 17:43, Rony G. Flatscher <[email protected]> wrote: > > Brief info on today's work: > > updating the tickets from "pending" and "accepted" with no open items to > "closed": did not write a utility after finding out about "bulk-edit", all > four categories got updated > added missing processedTickets.rex utility to new > main/trunk/support/sourceForge > updated text files in main/trunk (changing 4.2.0->5.0.0, 5.0.0->5.1.0), also > release-steps.txt which got updated to reflect what I was able to learn > today, including helpful links related to SourceForge > updated the milestones for the four ticket categories such that the milestone > list gets more manageable; did not change the ooDialog-related milestones, > though we probably should, what do you think? > --- > > Ad Jenkins: here we probably need to help P.O. to update the scripts w.r.t. > the "lessons learned" in this release cycle. Please, P.O. let us know what we > can do to help! > > I have made much of the work already but it is in a transitional state so PLEASE refrain from doing anything to the build machine & it’s scripts, I will let you know when I have something working. > --- > > Ad release version of ooRexx without revision information: once we can create > the binaries without revision information we could create new distributions > of 5.0.0, once the Jenkins scripts got updated to allow P.O. to do much of > the work without manual interventions. I would suggest to then also create > the portable versions for each platform (the build scripts need to get an > additional command added, "nmake portable" for Windows and "make portable" > for Unix plus uploading the two zip-archives to a new 5.0.0/portable > directory). >
Same here, I think I know what needs to be done but it takes time and I can only work limited time so bear with me for a couple of weeks. We waited 9 years, a couple of days more does not harm. > --- > > In order to re-iterate the release process to check out the updated scripts > and steps I would like to add the little oleinfo-utiltity and dbus-support > with tests (both in my sandbox, need to be updated w.r.t. license etc.) and > the multithreaded trace feature in the next weeks to trunk and then suggest > to build another release cycle 5.1.0 which hopefully goes much easier than > this one where we had to learn all that is necessary for a proper release. A > pre-requisite would be to have the Jenkins build scripts updated and being > able to create a revision-free release version of the binaries. > > Agreed, this will be a good test. I suggest a dummy test before that on 5.0.1 or similar that we can delete afterwards. Maybe end of January? > ---rony > > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
