+1 Jon
On Sat, 10 Dec 2022 at 22:34, René Jansen <rvjan...@xs4all.nl> wrote: > Me too. Let’s do it! > > René. > > > On 10 Dec 2022, at 18:21, P.O. Jonsson <oor...@jonases.se> wrote: > > I am in favor of making an official release of ooRexx 5; It is building > without error on all platforms on Jenkins and with the exception of a few > glitches due to testing in a VM all tests pass on all platforms. In > particular Windows 10 and macOS Monterey pass all tests. > > Hälsningar/Regards/Grüsse, > P.O. Jonsson > oor...@jonases.se > > > > > Am 08.12.2022 um 14:41 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at > >: > > The post <http://www2.marist.edu/htbin/wlvtype?LINUX-VM.97729> on the > Linux on Z mailing list points the programmers to a set of updated > programs. It is interesting among other things to note that it includes > ooRexx! :) > > It is ooRexx 4.2 though, which was released on 2014-02-24, almost nine > and three quarters of a year ago. > > The current ooRexx 5.0*beta* has many bugs of ooRexx 4.2 fixed, it has > many more and very useful features, and it is noticeably faster! So - we > all know that here - ooRexx 5.0*beta* would be definitely a huge > improvement to anyone who has been using and deploying ooRexx 4.x! > > Why not create a release "ooRexx 5.0" from the current trunk and remove > "beta" from it? Continue with enhancing and fixing ooRexx 5.0 and have at > least once a year a new version to be dubbed a "release" when it passes the > ooRexx test suite without any show-stopper errors (preferably right before > the yearly International Rexx Symposium). > > Or maybe even a "rolling release": whenever changes occur, but the test > suite passes without any show-stopper errors, place it in a release folder > on SourceForge rather than in a beta folder. This way anyone - including > companies - have the ability to download and use the latest version being > sure that the test-suite ran without any show-stopper errors. It would also > allow for an "up-to-date" feeling and having the world see that it gets > continually enhanced! > > If ooRexx 5.0 just had lost the word "beta" in it I am quite sure that the > poster of "Sir Santa's Bag for 2022" would have included ooRexx 5.0 instead > of the almost ten year old 4.2 version. Linux on Z user would then had been > able to take advantage of all those great enhancements and improvements in > ooRexx 5.0. > > All it would take is a consensus among the developers and decide which > version (the trunk version?) should be picked for a formal release to > signal the world that it is good enough to be used in production. > > ---rony > > > > > _______________________________________________ > 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 > > > _______________________________________________ > 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
