OK thanks Rick. At least I'm not totally delusional :-)
Gil
On 12/14/2022 3:11 PM, Rick McGuire wrote:
On Wed, Dec 14, 2022 at 2:05 PM Gilbert Barmwater
<gi...@bellsouth.net> wrote:
I seem to remember, perhaps incorrectly, that there was some
documentation on the steps necessary in order to create a new
release of ooRexx. However, my cursory attempt at locating it has
come up empty. If anyone else remembers such a document and, more
importantly, where it is, please let us know. In our attempt to
get 5.0.0 "out the door", I would hate to think that we might be
making mistakes either of omission or commission. Just my two
cents worth.
I have a vague memory of doing this after the 4.2.0 release, but I
don't remember where it was. I believe it was just an email to this
list, but a cursory search didn't turn up anything. I suspect a lot of
that information was made obsolete by moving to the cmake-based build.
Rick
Gil
On 12/14/2022 12:39 PM, Rony G. Flatscher wrote:
Hi P.O.,
On 14.12.2022 16:06, P.O. Jonsson wrote:
Am 14.12.2022 um 15:41 schrieb Rony G. Flatscher
<rony.flatsc...@wu.ac.at>:
@P.O.: is it possible for you to have the Jenkins creations
work on /docs/branches/5.0.0 and main/branches/5.0.0?
Yes, I can do the necessary changes to the Jenkins build and
test scripts as well as to the uploading scripts for the
Artifacts and the Documentation when we are ready.
Super!
We will need to look whether and what we need to change in the
documentation and installation production for ooRexx 5.0.
Also an idea: once we have the installation packages for all the
operating systems created it may be helpful for people wishing to
evaluate ooRexx 5.0.0 without installing it to create portable
versions of those packages (make portable) and place the
resulting zip-archives either in a subdirectory "portable" or
into a different location in the files menu. This may prove
helpful for future versions as well as starting with ooRexx 5.0.0
there may be different versions usable in parallel/concurrently.
Anyone who gives a helping hand is highly appreciated! :)
Ideally we should have a 5.0.0 folder on sourceforge for the
frozen „Release“ version and then a 5.0.1beta for all the work
committed to the next release. I assume there is a lot of work
to be done with the status of all bug reports as well, I have no
experience of these parts so I hope someone else can come
forward for doing that.
Yes, this has a little time though. When creating a new folder
there is an option for staging it for three days which means that
we as developers can use it, but no one would see it. This allows
us to experiment and to change the content of that directory.
Until then (next week?) I would not change anything there at this
point in time.
---
Also, we probably need to increase the version number of ooRexx
in trunk from 5.0.0 probably to 5.1.0 and the standard
installation packages produced by Jenkins would then go to
"5.1.0beta"?
Are there other changes we should apply to trunk?
---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
_______________________________________________
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
