To be fair to Rony, he is not the only one keen to have a release and he has suggested holding back some features for a subsequent release.
I won't rehash the reasons why we need a release - I think we are all familiar with them. So, can I suggest that we mark this enhancement (which I think is very important, but not as important as ending the beta state of 5.0.0) for 5.0.1 And release 5.0.0 as soon as we can? Jon On Wed, 15 Sep 2021, 23:15 Rick McGuire, <object.r...@gmail.com> wrote: > Since you are the one pushing to get 5.0 released, why are you adding new > features to the interpreter at this point? I'm OK with the MacOS changes, > but I'm against adding any new features to 5.0. > > Rick > > On Tue, Sep 14, 2021 at 12:19 PM Rony G. Flatscher < > rony.flatsc...@wu.ac.at> wrote: > >> As long as there is no architecture review board (ARB) in effect and >> developers in "land under water" mode that hinders them to communicate, I >> would like to apply the classic rule: "silence counts as approval" for the >> following planned changes/patches: >> >> - concurrency trace: this is a tested, important feature as it is for >> the first time that one becomes able to really trace concurrently >> executing >> Rexx programs; this is especially helpful for students who learn >> programming and must apply their acquired skills also in mastering >> concurrently executing Rexx programs (e.g. when debugging GUI applications >> from awt/swing and/or JavaFX); in this context also the documentation >> needs >> to be supplemented which I would do (in the area of the existing RXTRACE >> section in rexxref.pdf), RFE with patch: >> <https://sourceforge.net/p/oorexx/feature-requests/794/> >> <https://sourceforge.net/p/oorexx/feature-requests/794/>, >> >> - extract and commit the CMake definitions from Enrico's patch to >> allow ooRexx on MacOS to be optionally built as a universal binary such >> that ooRexx can run with the same binary on Intel and M1 computers. >> >> Will wait at least a week such that there is enough time for >> consideration and communication. >> >> ---rony >> >> P.S.: Also, if time permits (unfortunately I am also in "land under >> water" mode myself) I would like to add the ability to create >> "stick"-versions of ooRexx, such that up-to-date versions can be created >> each time ooRexx gets compiled. >> >> >> _______________________________________________ >> 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
