Re: [Oorexx-devel] Ad oorexx-announcement list

I have tried. No Bounce, but I don't see it on the list nor do I get a request for moderation. Sourceforge may be running slow. Jon On Fri, 23 Dec 2022 at 23:22, Rony wrote: > Just received a rejection from the oorexx-announcement list. Can someone > else try to send the announcement to that

[Oorexx-devel] Thanks and the next steps …

This is to thank everyone who has helped releasing 5.0.0 in the past eight days! This was a great job by everybody! —- Personally, I will be off for some time as I will be visiting my mother for the Christmas holidays. Afterwards I will tackle whatever is open (changing the tickets from pendin

[Oorexx-devel] Ad oorexx-announcement list

Just received a rejection from the oorexx-announcement list. Can someone else try to send the announcement to that list please? —-rony Rony G. Flatscher (mobil/e) ___ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourcefor

[Oorexx-devel] Updated binary attributes

Just updated the attributes of the binaries in https://sourceforge.net/projects/oorexx/files/oorexx/5.0.0/ to define the operating system of each. This should have the effect that the default download link at the top of the Sourceforge page now honors the operating system of the browser with th

Re: [Oorexx-devel] Release of ooRexx 5

yes, that is the plan. And thanks for delivering the first change - I know I have to know these things, but it will proceed most quickly if I am sent lots of these links. Kudos for all the work (and you P.O.!) and for getting the message out. best regards, René. > On 23 Dec 2022, at 18:53, R

[Oorexx-devel] Announcing the Release of ooRexx 5.0.0

The ooRexx (open object Rexx) team is pleased to release ooRexx 5.0.0 and make it generally available to the world via the web from .  ooRexx is the object-oriented successor to IBM's famous Rexx language which remains easy to learn, easy to program in and easy to mai

Re: [Oorexx-devel] Release of ooRexx 5

Thank you René!Could you change the download link to < https://sourceforge.net/projects/oorexx/files/oorexx/5.0.0/> ? TIA!—-ronyRony G. Flatscher (mobil/e)Am 23.12.2022 um 23:50 schrieb René Jansen :Also,have a look at https://www.oorexx.org/index2.html - as soon as all the changed info is know, I

Re: [Oorexx-devel] Release of ooRexx 5

Also, have a look at https://www.oorexx.org/index2.html - as soon as all the changed info is know, I can work on updating the rest of the site. best regards, René. > On 23 Dec 2022, at 18:36, P.O. Jonsson wrote: > > In my opinion yes, I think we can deal with the details after the holidays.

Re: [Oorexx-devel] Release of ooRexx 5

In my opinion yes, I think we can deal with the details after the holidays. I would appreciate if Rick and Erich had a look as well. Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > Am 23.12.2022 um 23:32 schrieb Rony : > > Super! +1 > > So we are good to send the announcement e

Re: [Oorexx-devel] Release of ooRexx 5

Super! +1 So we are good to send the announcement e-mail? —-rony Rony G. Flatscher (mobil/e) > Am 23.12.2022 um 21:04 schrieb ooRexx : > > Dear all, > > I have finally managed to finalise the work for the release. It is clear that > we should do it differently in the future, the small hiccu

Re: [Oorexx-devel] Release of ooRexx 5

Yes it’s 22.04 LTS Von meinem iPhone gesendet > Am 23.12.2022 um 21:33 schrieb Michael Lueck : > > Greetings ooRexx'ers, > > ooRexx wrote: >> All other Platforms now report version 12583 and are available for download. > > > Bravo! > > >> I have renamed the documentation to 5.0.0 >> I will

[Oorexx-devel] ooRexx v5.0 GA passes Hello World! on Xubuntu v20.04

Bye bye old version... mdlueck@jaakob:~$ rexx -v Open Object Rexx Version 5.0.0 r12279 Build date: Jul 7 2021 Addressing mode: 64 Copyright (c) 1995, 2004 IBM Corporation. All rights reserved. Copyright (c) 2005-2021 Rexx Language Association. All rights reserved. This program and the accompanyi

Re: [Oorexx-devel] Release of ooRexx 5

Greetings ooRexx'ers, ooRexx wrote: All other Platforms now report version 12583 and are available for download. Bravo! I have renamed the documentation to 5.0.0 I will shut down Jenkins for a few days, after which I will go through and change all things back to “normal”. One question

[Oorexx-devel] Release of ooRexx 5

Dear all, I have finally managed to finalise the work for the release. It is clear that we should do it differently in the future, the small hiccups that pop up last minute create lots of extra work. Let’s discuss this after the holidays. 3 caveats, FreeBSD is revision 12563, Jenkins does not

Re: [Oorexx-devel] Fwd: [oorexx:code-0] New commit [r12584] by orexx

Saw that new Windows builds were available so I downloaded the 64-bit version and installed it.  Works great and the docs are correct!  Well done everyone! Gil On 12/23/2022 11:45 AM, Gilbert Barmwater wrote: Rony, P.O. indicated that he can trigger a build manually on Jenkins so it should

Re: [Oorexx-devel] Fwd: [oorexx:code-0] New commit [r12584] by orexx

Rony, P.O. indicated that he can trigger a build manually on Jenkins so it should NOT be necessary to do any further SVN updates.  FWIW, Gil On 12/23/2022 11:33 AM, Rony G. Flatscher wrote: On 23.12.2022 17:29, ooRexx wrote: Due to this unnecessary commit Windows and macOS are now getting a

Re: [Oorexx-devel] [oorexx:code-0] New commit [r12584] by orexx

There is the possibility to revert a skunky commit, along the lines of svn merge -c 12584 Can you do that? > > > ___ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel ___

Re: [Oorexx-devel] [oorexx:code-0] New commit [r12584] by orexx

> On 23. Dec 2022, at 17:33, Rony G. Flatscher wrote: > > On 23.12.2022 17:29, ooRexx wrote: >> Due to this unnecessary commit Windows and macOS are now getting another >> revision than the rest. Should we accept that or should I try to manually go >> back one version? This is causing a LOT of

Re: [Oorexx-devel] Fwd: [oorexx:code-0] New commit [r12584] by orexx

On 23.12.2022 17:29, ooRexx wrote: Due to this unnecessary commit Windows and macOS are now getting another revision than the rest. Should we accept that or should I try to manually go back one version? This is causing a LOT of stress one day before Christmas. If you apply the patch to branche

[Oorexx-devel] Fwd: [oorexx:code-0] New commit [r12584] by orexx

Due to this unnecessary commit Windows and macOS are now getting another revision than the rest. Should we accept that or should I try to manually go back one version? This is causing a LOT of stress one day before Christmas. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se > Begin forward

[Oorexx-devel] trigger.patch (Re: Wrong documentation in latest builds ...

Will have to leave the office, so maybe you can trigger the building of the binaries by applying the enclosed "trigger.patch"? * save the attached "trigger.patch" (the result of doing a "svn diff > trigger.patch" in "main/branches/5.0.0") to your "main/branches/5.0.0" directory * change i

Re: [Oorexx-devel] Wrong documentation in latest builds ...

Dear P.O., On 23.12.2022 17:00, ooRexx wrote: I am working like hell, I have to do chases in some 70 different places, please do not send any more mail and for Gods sake do not make ANY more check-ins, the whole build system is in a transition state and you are messing everything up. Well, so

Re: [Oorexx-devel] Wrong documentation in latest builds ...

Dear Rony, I am working like hell, I have to do chases in some 70 different places, please do not send any more mail and for Gods sake do not make ANY more check-ins, the whole build system is in a transition state and you are messing everything up. Can ALL people refrain from doing ANY changes

Re: [Oorexx-devel] Another observation, Sourceforge "release API"

On 23.12.2022 16:27, Sahananda Sahananda wrote: I have a question about defaulting to the 64bit version for Windows. Is it still the case that if you use Mark's extensions (ie: Rexx/SQL etc) you need to have the 32 bit version even if running on a 64 bit machine? Honestly, I do not know,  may

Re: [Oorexx-devel] Wrong documentation in latest builds ...

On 23.12.2022 15:38, Rony G. Flatscher wrote: On 23.12.2022 15:16, ooRexx wrote: Since the documentation was not built it was outdated when Windows was built, The documentation in was o.k. already! It seem

Re: [Oorexx-devel] Current state, lists to write to (Re: Proposed text ...

On 23.12.2022 15:40, Gilbert Barmwater wrote: Fix typo: "...you may consider to joining..." -> "... you may consider joining..." Great, thank you, Gil! Here the corrected current text: --- cut --- Subject: Announcing the Release of ooRexx 5.0.0 The ooRexx (open object Rexx) team is

Re: [Oorexx-devel] Current state, lists to write to (Re: Proposed text ...

Fix typo: "...you may consider to joining..." -> "... you may consider joining..." On 12/23/2022 8:52 AM, Rony G. Flatscher wrote: First of all, thank you all for your feedback on the text! On 23.12.2022 14:41, Sahananda Sahananda wrote: Just a reminder, we have the ooRexx Announcements list

Re: [Oorexx-devel] Wrong documentation in latest builds ...

On 23.12.2022 15:16, ooRexx wrote: Since the documentation was not built it was outdated when Windows was built, The documentation in was o.k. already! It seems that the build process for ooRexx picks the do

Re: [Oorexx-devel] Wrong documentation in latest builds ...

Since the documentation was not built it was outdated when Windows was built, I will fix this, will take one hour. Hälsningar/Regards/Grüsse, ooRexx oor...@jonases.se > On 23. Dec 2022, at 15:13, Rony G. Flatscher wrote: > > Just downloaded the new 64-bit windows build that includes unfortun

[Oorexx-devel] Wrong documentation in latest builds ...

Just downloaded the new 64-bit windows build that includes unfortunately the *wrong* documentation. It looks as if the build process picks up the documentation from https://sourceforge.net/projects/oorexx/files/oorexx-docs/5.0.0beta/ instead of https://sourceforge.net/projects/oorexx/files/oor

[Oorexx-devel] Current state, lists to write to (Re: Proposed text ...

First of all, thank you all for your feedback on the text! On 23.12.2022 14:41, Sahananda Sahananda wrote: Just a reminder, we have the ooRexx Announcements list on Sourceforge with 26 members Ah, would not have realized that, thank you very much! :) So suggesting: * RexxLA member list *

Re: [Oorexx-devel] Proposed text ...

Just a reminder, we have the ooRexx Announcements list on Sourceforge with 26 members Jon On Fri, 23 Dec 2022 at 13:37, WalterPachl via Oorexx-devel < oorexx-devel@lists.sourceforge.net> wrote: > Two suggestions: > > OLD-> statements, boiler plate text, base64 encoded binary data ...) and > muc

Re: [Oorexx-devel] Proposed text ...

Two suggestions: OLD-> statements, boiler plate text, base64 encoded binary data ...) and much NEW-> statements, boiler plate text, base64 encoded binary data ...) and many OLD-> samples directory which demonstrates some of its capabilities. The NEW-> samples directory which contains program

Re: [Oorexx-devel] Proposed text ...

Just a few minor language changes :-) general -> generally (first sentence) to join -> joining (paragraph near the bottom) Gil On 12/23/2022 7:46 AM, Rony G. Flatscher wrote: Here the proposed (it should not be too long, it should carry the most important information and make the readers inte

[Oorexx-devel] Proposed text ...

Here the proposed (it should not be too long, it should carry the most important information and make the readers interested in downloading and using it, as well as giving them the idea to join RexxLA if they have not done so) text: - cut here - Subject: Announcing the Release

[Oorexx-devel] Kicking a new build for release ...(Re: Only 1 version for a release (candidate) (Re: Preparing the release

Just saw that the versions in 5.0.0_Release_Candidate are from Tuesday and Wednesday. In order to have the latest documentation included into the installation packages I will try to kick a new build by changing some arbitrary file and committing in branches/5.0.0 in a minute or two. Once the

Re: [Oorexx-devel] Only 1 version for a release (candidate) (Re: Preparing the release

On 23.12.2022 11:52, P.O. Jonsson wrote: Am 23.12.2022 um 10:09 schrieb Rony G. Flatscher : On 22.12.2022 21:54, ooRexx wrote: There should be at maximum 5 versions of every platform, which makes it 10 for Windows (32/64 bit). We do build and test Windows 7,8.1,10 and recently also 11 but we

Re: [Oorexx-devel] Only 1 version for a release (candidate) (Re: Preparing the release

> Am 23.12.2022 um 10:09 schrieb Rony G. Flatscher : > > On 22.12.2022 21:54, ooRexx wrote: >> There should be at maximum 5 versions of every platform, which makes it 10 >> for Windows (32/64 bit). We do build and test Windows 7,8.1,10 and recently >> also 11 but we only upload Windows 10, which

Re: [Oorexx-devel] Question ad updating copyright statement in sources

In general, we only update the copyrights in the source files if they have an update. It doesn't always get done, but it's ok if the files have different copyright dates. Rick On Fri, Dec 23, 2022 at 5:34 AM Rony G. Flatscher wrote: > Just noticed that there are plenty of files in the code area

[Oorexx-devel] Question ad updating copyright statement in sources

Just noticed that there are plenty of files in the code area that have their copyright statements not updated to 2022. Question: shall we update the copyright notice there like we did for the documentation? If so, what patterns should we use for SysFileTree to look for existing copyright text

Re: [Oorexx-devel] Making a request for a future release

On 23.12.2022 10:40, Sahananda Sahananda wrote: Looking at the docs, I think that the *NEW* & *CHANGED* markers are hard to distinguish from the text and I would like to request that we look into either using some symbolic markers or text in a different style for these markers. However, I don'

Re: [Oorexx-devel] Preparing the release

On 23.12.2022 10:35, Sahananda Sahananda wrote: Regarding the 11 minute wait I reported. Soon after this incident it became clear that a massive Windows Update was brewing, which occupied my laptop for the rest of the evening. This morning I reverted to ooRexx-5.0.0-12359 then back to ooRexx-

[Oorexx-devel] Making a request for a future release

Looking at the docs, I think that the *NEW* & *CHANGED* markers are hard to distinguish from the text and I would like to request that we look into either using some symbolic markers or text in a different style for these markers. However, I don't want this request to hold up this release. Is the

Re: [Oorexx-devel] Preparing the release

Regarding the 11 minute wait I reported. Soon after this incident it became clear that a massive Windows Update was brewing, which occupied my laptop for the rest of the evening. This morning I reverted to ooRexx-5.0.0-12359 then back to ooRexx-5.0.0-12558 and in both cases the install started im

[Oorexx-devel] Only 1 version for a release (candidate) (Re: Preparing the release

On 22.12.2022 21:54, ooRexx wrote: There should be at maximum 5 versions of every platform, which makes it 10 for Windows (32/64 bit). We do build and test Windows 7,8.1,10 and recently also 11 but we only upload Windows 10, which should work on all Windows platforms supported. It should be th

Re: [Oorexx-devel] Question ad copyright string

On 23.12.2022 00:08, Chip Davis wrote: While I agree with Jon about readability, I scanned the web for "how to format a copyright notice" and found not a single example that used a comma (or any break besides a space) between the date and the copyright holder. Thank you too! As you both are n

Re: [Oorexx-devel] docs/branches/5.0.0: updated copyright, added & committed "${book}/revision_info.txt", updated & commited EDITION entity; scripts checked in

On 22.12.2022 23:18, Gilbert Barmwater wrote: So, as Jon has noted, on Windows the installer includes the documentation which will be the "current" set as of the time the Windows build is executed.  Now if one updates one (or more) of the documents - which we have been doing quite a bit over t

Re: [Oorexx-devel] Preparing the release

On 22.12.2022 21:54, ooRexx wrote: H Jon, There should be at maximum 5 versions of every platform, which makes it 10 for Windows (32/64 bit). We do build and test Windows 7,8.1,10 and recently also 11 but we only upload Windows 10, which should work on all Windows platforms supported. The pr

Re: [Oorexx-devel] docs/branches/5.0.0: updated copyright, added & committed "${book}/revision_info.txt", updated & commited EDITION entity; scripts checked in

On 22.12.2022 21:48, ooRexx wrote: The building and uploading of the documentation is, and has been for quite some time, automatic. The documentation will be built within an hour of any amendment to the documentation (and I mean ANY amendment changing the SVN revision). What is on Sourceforge sh

Re: [Oorexx-devel] Ad Jenkins: build portable ooRexx for release versions ...

Dear P.O., On 22.12.2022 21:26, ooRexx wrote: On 22. Dec 2022, at 19:08, Rony G. Flatscher wrote: It would be great, if it was possible to automatically create those portable versions for all platforms and upload them to Sourceforge in a proper subdirectory named "portable” If I unders