Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2 URGENT

> On 15. Dec 2022, at 16:33, Rick McGuire wrote: > > > > On Thu, Dec 15, 2022 at 10:15 AM P.O. Jonsson > 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

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2 URGENT

On 15.12.2022 16:33, Rick McGuire wrote: ... cut ... Test Repository URL 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. Great, just added that branch as well (test/branches/5.0.0). ...

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2 URGENT

On Thu, Dec 15, 2022 at 10:15 AM P.O. Jonsson 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

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2 URGENT

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

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

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

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

On Thu, Dec 15, 2022 at 9:26 AM Rony G. Flatscher 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

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

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

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

On 15.12.2022 11:47, P.O. Jonsson wrote: Am 15.12.2022 um 11:44 schrieb Rick McGuire : Another suggestion. Create a file in the root directory of the trunk detailing all of the steps taken to make the release and update it immediately for every action that is taken for making

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

I noticed that there is a Wiki page created for this purpose created by someone, maybe we can use that and later move it to the repository? https://sourceforge.net/p/oorexx/rel5wiki/Home/ To edit it simply use the „Pencil“ in the upper right

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

> Am 15.12.2022 um 11:44 schrieb Rick McGuire : > > > Another suggestion. Create a file in the root directory of the trunk > detailing all of the steps taken to make the release and update it > immediately for every action that is taken for making the release. That will > result in a fairly

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

> > > Another suggestion. Create a file in the root directory of the trunk > detailing all of the steps taken to make the release and update it > immediately for every action that is taken for making the release. That > will result in a fairly easy to follow checklist in a known location that >

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

I have created a staged folder „5.0.0_Release_Candidate under /files/oorexx. I changed existing 5.1.0beta to staged at the same time. 3 days to do the work then. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 15.12.2022 um 11:19 schrieb Rony G. Flatscher : > > On 15.12.2022

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

> > 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. Rick ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

On 15.12.2022 11:17, Rick McGuire wrote: How about calling it "5.0.0 Release Candidate"? +1 That would be the best! ---rony ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

How about calling it "5.0.0 Release Candidate"? Rick On Thu, Dec 15, 2022 at 5:01 AM P.O. Jonsson wrote: > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > > > Am 15.12.2022 um 09:00 schrieb Rony G. Flatscher >: > > Thanks to Rick we got the version information updated in

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

On 15.12.2022 11:00, P.O. Jonsson wrote: Am 15.12.2022 um 09:00 schrieb Rony G. Flatscher : Thanks to Rick we got the version information updated in trunk (). Todos: * add "#define REXX_INTERPRETER_5_1_0 0x00050100" to trunk's

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2

Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 15.12.2022 um 09:00 schrieb Rony G. Flatscher : > > Thanks to Rick we got the version information updated in trunk > ( > ). > >

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2, release builds as release :)

On 15.12.2022 10:02, Rony G. Flatscher wrote: On 15.12.2022 09:00, Rony G. Flatscher wrote: Thanks to Rick we got the version information updated in trunk (). Todos: * add "#define REXX_INTERPRETER_5_1_0  0x00050100" to trunk's

Re: [Oorexx-devel] Release ooRxx 5.0.0: Step 2, new item

On 15.12.2022 09:00, Rony G. Flatscher wrote: Thanks to Rick we got the version information updated in trunk (). Todos: * add "#define REXX_INTERPRETER_5_1_0  0x00050100" to trunk's api/oorexxapi.h done with r12540

[Oorexx-devel] Release ooRxx 5.0.0: Step 2

Thanks to Rick we got the version information updated in trunk (). Todos: * add "#define REXX_INTERPRETER_5_1_0  0x00050100" to trunk's api/oorexxapi.h * on Sourceforge create "files/oorexx/5.1.0beta" to receive the new builds from trunk *