HI Erich, good to hear, I’ll work with you on this.

best regards,

René.

> On 31 Jan 2021, at 18:02, Erich Steinböck <erich.steinbo...@gmail.com> wrote:
> 
> René, I'll see what I can do, time and skills permitting.
> I have no experience how to convince distributions to pick up ooRexx 5 or to 
> bring it into the Windows Store.
> 
> Erich
> 
> On Sun, Jan 24, 2021 at 2:02 PM René Jansen <rvjan...@xs4all.nl 
> <mailto:rvjan...@xs4all.nl>> wrote:
> I agree with Rick here.
> 
> But: the problem here is that the notions of GA, ‘golden’ are from the last 
> century and might not be applicable in this day and age. I see a lot of 
> software projects having two lines of release, one stable and one rolling. It 
> is a fact, though, that there are companies still adhering to those older 
> notions, some of them are ex-Open Object Rexx clients from IBM, and RexxLA 
> has obligations towards those clients for maintaining and improving the 
> product, on condition of which it was delivered the source code. The moment 
> that the 4.X releases (our ‘stable release’) don’t work properly anymore, we 
> are defaulting on that agreement. I might all be academic because those 
> companies seem to be moving to other languages; that may or may not be our 
> fault.
> 
> But whatever the state of the code, being in beta for 7 years is not a good 
> sign for viability of any project. The problem here was declaring a beta, 
> when in fact it was still pre-release code. For the future, we should refrain 
> from calling a release a beta when we do not have a plan for a release.
> 
> In my opinion, we need a plan to address this problem. It should be a plan to 
> release on a specific date, on the condition that work has been done on a few 
> issues.
> 
> 1) What: Classify the open issues in ‘showstoppers' and ‘other’ categories. 
> Flag them as such. Who: Rick and Erich, René. When: March 31, 2021
> 2) What: Commit all installers, tests and other improvements we have. Who: 
> P.O., Rony and others. When: February 15, 2021
> 3) What: Identify documentation issues. Who: Rick and Rony, Erich, others. 
> When: Februari 28, 2021
> 4) What: Improve documentation along identified issues. Who: Gil, Jon, René, 
> Rony, Walter, others. When: April 15, 2021
> 5) What: fix, freeze, prepare and test GA release. Who: P.O., Erich, Rick, 
> others. When: May 1st, 2021.
> 
> I know I cannot decide on other people’s time, so I just hope we can agree to 
> this, on a best effort base. I hope we all see the predicament we are in. 
> When we have this in the past, we can decide on release approaches that are a 
> better fit. 
> 
> Please react on, and improve on this planning, so we can have something we 
> can commit to soon.
> 
> best regards,
> 
> René.
> _______________________________________________
> 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

Reply via email to