I agree with Rony that version 5 of ooRexx should be formally released, I just did not raise my voice since this is a discussion amongst the developers.
Due to the delay we may already have lost a major „client, my former employer, the European Patent Office, with more than 4000 ooRexx 4 installations. They are now going all-in for Python instead, they will never be able to upgrade to 5.0.0 unless there is an official release. Can Rick and/or Erich provide a list of „showstoppers“ so they can be worked off? Are there REALLY any problems that are so severe that they would prohibit a release? I doubt it. I can offer to set up the macOS Installer on the Jenkins machine. It is Cmake driven and uses standard Unix commands in the post-processing. It also includes the latest documentation, license, HowTo etc. Example can be found in „MacBuilds“ here <https://www.dropbox.com/sh/p66c7g01h4jz5ss/AAAZd_Q2yQddrTHagxPo_UiTa?dl=0> I have also written test cases for all sample files, they can be uploaded but require a little fix in the testing framework (that I can provide as well). I have set up the documentation (PDF and HTML) to be built on Jenkins every new revision (this is where I get it for the macOS installer) what is missing is an upload to Sourceforge, this needs to be done with someone with R/W access there. So what is really missing that prohibits a release? Is it not about time now to kill our baby and go ahead and release 5.0 and start working on 5.1? Hälsningar/Regards/Grüsse, P.O. Jonsson oor...@jonases.se > > _______________________________________________ > 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
