> On 15. Dec 2022, at 16:33, Rick McGuire <object.r...@gmail.com> wrote: > > > > On Thu, Dec 15, 2022 at 10:15 AM P.O. Jonsson <oor...@jonases.se > <mailto:oor...@jonases.se>> wrote: > I am a bit confused so could someone (Rony?) please let me know what I should > change for Jenkins? At the moment the commits are processed but they may be > going to the wrong place. Please fill in the new places below. I will add > this to the todo list once it is complete > > > Build Repository URL > > https://svn.code.sf.net/p/oorexx/code-0/main/trunk > <https://svn.code.sf.net/p/oorexx/code-0/main/trunk> > > That's the trunk. You need to be building from the release candidate branch: > https://svn.code.sf.net/p/oorexx/code-0/main/branches/5.0.0 > <https://svn.code.sf.net/p/oorexx/code-0/main/branches/5.0.0> CHECK
> > > Test Repository URL > > https://svn.code.sf.net/p/oorexx/code-0/test/trunk > <https://svn.code.sf.net/p/oorexx/code-0/test/trunk> > > We haven't yet branched the tests, but we probably should. For now, this is > correct. I Changed this Switching from https://svn.code.sf.net/p/oorexx/code-0/test/trunk to https://svn.code.sf.net/p/oorexx/code-0/test/branches/5.0.0 > > > Documentation Repository URL > > https://svn.code.sf.net/p/oorexx/code-0/docs/trunk > <https://svn.code.sf.net/p/oorexx/code-0/docs/trunk> > > Again, you need to be building from the release candidate, not trunk: > https://svn.code.sf.net/p/oorexx/code-0/docs/branches/5.0.0 > <https://svn.code.sf.net/p/oorexx/code-0/docs/branches/5.0.0> CHECK > > > The upload of docs go to (two folders, PDF and html) > > /oorexx-docs/5.0.0beta' > /oorexx-docs/5.0.0html' > > PDF CHANGED TO oorexx-docs/5.0.0_Release_Candidate (staged) > The upload of artifacts go to > > sourceforgeFiles = "/home/frs/project/oorexx/oorexx/5.0.0beta" > CHANGED TO oorexx/5.0.0_Release_Candidate (staged) > The following artifacts are selected for upload: > ooRexx-CentOS9-build > ooRexx-Debian11-build > ooRexx-Fedora35-build > ooRexx-FreeBSD13-build > ooRexx-linux-aarch64-build > ooRexx-LinuxMint20-build > ooRexx-macOS11-build > ooRexx-macOS12-build > ooRexx-NetBSD9-build > ooRexx-OpenBSD7_1-build > ooRexx-OpenIndiana-build > ooRexx-OpenSuse15-build > ooRexx-RaspberryPiOS32-build > oorexx-ubuntu16-build > oorexx-ubuntu16debug-build > ooRexx-Controller-Ubuntu20-build > ooRexx-Ubuntu22-build > ooRexx-windows32-build > ooRexx-windows64-build > ooRexx-Z-build > > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se <mailto:oor...@jonases.se> > > > > >> Am 15.12.2022 um 15:53 schrieb Gilbert Barmwater <gi...@bellsouth.net >> <mailto:gi...@bellsouth.net>>: >> >> Just one more comment that I feel should not be overlooked. As we review >> the "accepted" items we may find a small change - adding a test or updating >> the docs - would allow the status to be upgraded to "pending". If that is >> the case and those changes are made, they MUST be made in TWO places - the >> "branches" subtree AND the "trunk". Otherwise they will only apply to the >> 5.0.0 release and 5.1.0 will NOT contain them. This may be obvious but it >> is too easy to overlook. >> >> Gil >> >> On 12/15/2022 9:30 AM, Rick McGuire wrote: >>> >>> >>> On Thu, Dec 15, 2022 at 9:26 AM Rony G. Flatscher <rony.flatsc...@wu.ac.at >>> <mailto:rony.flatsc...@wu.ac.at>> wrote: >>> On 15.12.2022 11:24, Rick McGuire wrote: >>>> One more TODO. The CHANGES file needs to be finished off. It's in decent >>>> shape but is definitely missing some of the recent changes. >>> Added it to the "release-steps.txt" file: please note, there are a few >>> entries with "??" in the first two columns where I was not sure whether >>> that is correct that way. >>> >>> Looking through the Tickets (bugs, feature-requests, documentation, >>> patches) I notice that some tickets have a status of "accepted". Shall >>> these be added to the CHANGES file in branches/5.0.0 as well, or only the >>> ones with a status of "pending"? >>> >>> Accepted means that there's still some work pending on the item, generally >>> either doc or test work. It usually means the code changes have been >>> committed, so they should be included. >>> >>> >>> After finalizing the CHANGES file in branches/5.0.0 should all "pending" >>> tickets be changed to "closed" and the CHANGES file in trunk be "emptied" >>> to allow for adding what is new while working on 5.1.0? >>> >>> Yes. >>> >>> ---rony >>> >>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >>> >>> >>> >>> _______________________________________________ >>> Oorexx-devel mailing list >>> Oorexx-devel@lists.sourceforge.net >>> <mailto:Oorexx-devel@lists.sourceforge.net> >>> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >>> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> >> _______________________________________________ >> Oorexx-devel mailing list >> Oorexx-devel@lists.sourceforge.net >> <mailto:Oorexx-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> <https://lists.sourceforge.net/lists/listinfo/oorexx-devel> > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net <mailto:Oorexx-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > <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
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
