I am for it, but I think it is up to Erich and Rick. To be precise, I am for freezing, setting a date and prepare. I would like to have the oorexx.org <http://oorexx.org/> website up to date before we announce. I did some work last year, which is accessible through oorexx.org/index2.html <http://oorexx.org/index2.html> , but I need to finish that. Also - documentation. We must be able to build it in a repeatable fashion and not when someone’s pc has the right configuration. We are working towards that, albeit slowly.
I was planning for the symposium, but I can imagine it would be better if we did it earlier. My proposal: freeze now and release March 1st. best regards, René. > On 15 Jan 2019, at 10:15, Rony G. Flatscher <rony.flatsc...@wu.ac.at> wrote: > > What would be the thoughts about releasing the current trunk version of > ooRexx 5.0 as "general > available"? > (In order for organisations/companies to adopt 5.0 or to replace older > versions of Rexx/ooRexx with > 5.0 it would be necessary that it becomes officially GA.) > > It would be still possible to create some ooRexx 5.1, 5.2 and the like > shortly after a GA release, > if new functionality would be added to it (e.g. applying sandbox development > results or implementing > RFEs). > > ---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
