Sadly enough I understand and have to agree with Rick. Aren't you (we) lacking some workers?
Where are the times when I wrote a ticket (then for the compiler) and it was handled in a couple of days if not hours. All the best Walter > Rick McGuire <object.r...@gmail.com> hat am 23. Januar 2021 um 17:06 > geschrieben: > > No answer from me means I'm just tired of having to answer this question > over and over. In my opinion, it is not ready for release yet. We still have > no checked in installer solution for the mac, there are a number of unfixed > bugs, the docs really, really need a thorough review and update, and there > are still incomplete doc/test items on some fixed bugs and features. > > Rick > > PS, if you're looking for me to be the one to do all of the above, it's > probably not going to happen. ` > > On Sat, Jan 23, 2021 at 10:33 AM Rony G. Flatscher < > rony.flatsc...@wu.ac.at mailto:rony.flatsc...@wu.ac.at > wrote: > > > > As so far there has been no feedback whatsoever by Erich or Rick, > does that mean that there is a > > silent consent to release the current beta version of ooRexx 5.0 by > > the end of February 2021? > > > > If so, should we create a release candidate (RC) for all supported > > platforms and communicate it to > > allow developers and users to test it ASAP? Or do we take the fact > > that for the past months and past > > years there has been plenty of time to check out and test ooRexx > > 5.0 beta and that we have therefore > > everything relevant to know about it in our track system? > > > > Should there be no showstopper-errors found, let us say within the > > next fourteen days, then prepare > > the general availability (GA) release to be announced and > > distributed by the end of February by > > RexxLA from a (to be created) main/releases/5.0.0 in svn. > > > > Would that be acceptable for everyone? > > > > ---rony > > > > P.S.: Taking no answers as silent consent! > > :) > > > > > > On 11.01.2021 17:14, Rony G. Flatscher wrote: > > > On February 24th 2021, it will be seven (!) years since the last > > official release of ooRexx took > > > place, believe it or not! > > > > > > People who do not follow this list or the ooRexx code updates on > > Sourceforge will think, that > > > maintenance, let alone development, of ooRexx has ceased seven > > years ago! :( > > > > > > This puts pressure on those people in organisations/businesses > > who use Rexx/ooRexx but are faced > > > with demands of replacements with more modern, maintained and > > continuously developed programming > > > languages like Python, Ruby and the like. > > > > > > Also, people who suggest to allow usage of ooRexx in > > organisations/businesses will usually get > > > turned down as ooRexx is outdated and not maintained, so why > > using it? Learning about a beta version > > > does not help as everyone knows that beta means error-prone, > > unstable software and the like, and as > > > a result organisations/businesses usually prohibit usage and > > deployment of beta software. > > > > > > As ooRexx 5.0 beta has been in an excellent condition for many > > years, it could have been released > > > years ago! ooRexx 5.0 beta adds a wealth of great new features, > > in addition very notable speed > > > improvements and fixes many bugs of the seven years old ooRexx > > 4.2, the last official release of > > > ooRexx! > > > > > > As no show-stoppers are present I think that the current version > > of ooRexx 5.0 beta should be > > > released ASAP as is. The only thing needed would be a new package > > that is declared to be the release > > > package! > > > > > > Is there a will for a release? If so, can the release be done by > > February 24th 2021? > > > > > > ---rony > > > > > > P.S.: Also, once a release is done, I would suggest to make sure > > to create a yearly (!) release, > > > even if they are only microreleases! This will signal ongoing > > maintenance and development to > > > outsiders/users of ooRexx, which has been the case for all those > > past years (but lacking releases > > > this was not communicated successfully to outsiders/users of > > ooRexx). > > > > > > P.P.S.: In today's world the release cycles are critical to > > public reception of the healthiness of > > > (software) projects it seems, probably the main reason why Linux > > creates even twice a year a > > > release, but also Java/OpenJDK and others. > > > > > > > > > > > _______________________________________________ > > Oorexx-devel mailing list > > Oorexx-devel@lists.sourceforge.net > > mailto: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 > LG Walter
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
