Having not heard any objectsions I just created branches/5.0.0 for the docs and
the code.
This should allow us to change the branches/5.0.0 whatever changes need to be
done for the release.
@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?
Anyone who gives a helping hand is highly appreciated! :)
---rony
P.S.: Will try to document the necessary steps and create a wiki item for
future releases.
P.P.S.: Here the svn commands to create the branches:
svn copy --username=userIdsvn+ssh://or...@svn.code.sf.net/p/oorexx/code-0/docs/trunk
svn+ssh://or...@svn.code.sf.net/p/oorexx/code-0/docs/branches/5.0.0 -m "Creating
docs branch 5.0.0 to prepare release."
svn copy --username=userIdsvn+ssh://or...@svn.code.sf.net/p/oorexx/code-0/main/trunk
svn+ssh://or...@svn.code.sf.net/p/oorexx/code-0/main/branches/5.0.0 -m "Creating
code branch 5.0.0 to prepare release."
On 13.12.2022 12:51, Rony G. Flatscher wrote:
Not being sure what the proper sequence and steps are to create and release ooRexx 5.0.0, so here
a few items that come to mind:
- create a branch/5.0.0 from trunk if no show-stopper errors show up on Jenkins
- change the version information from ooRexx to indicate the version is a
release version
- question: possibly change the date in the documentation PDF files?
- create the release ooRexx 5.0.0 installation packages from branch/5.0.0
- move the branch/5.0.0 to releases/5.0.0
- upload installation packages to a new staged directory "files/oorexx/5.0.0"
- update the trackers to reflect the release 5.0.0 took place
- change the attribute for each installation package to indicate for which operating system it got
built (Windows, Mac, various Linuxes): this will cause a link to appear on the web page that
allows for downloading the proper version depending on the operating system used to get to the
Sourceforge website
- change the name of the directory on Sourceforge that receives the current builds from trunk
(e.g. rename from "5.0.0beta" to "5++beta" or the like)
- communicate the availability of the ooRexx 5.0.0 release in all possible
channels
Suggestion for a time table:
* t0: if the tests on Jenkins show no show-stopper errors from the latest
trunk, then create the
branch: ASAP
* t1: apply the necessary changes in the branch (version information update,
release information
update): < =(t0+7 days)
* t2: create the installation packages from the branch and upload them to a
staged directory
"5.0.0": after a week (t1+1)
* t3: communicate the availability: t2+1
Is there anything missing?
---
ad ooRexx releases thereafter:
- if possible let us use a "rolling release" [1] scheme
- there should be at least one release per year before the International Rexx symposium, the
RexxLA owner's yearly conference on Rexx related technologies, a premier opportunity to report on
new abilities, features of ooRexx by anyone who is able and willing to do so
- in between any time new samples, new documentation gets added and the tests do not exhibit any
show stopper bugs
- in between any time new features get added on any platform and the tests do not exhibit any show
stopper bugs
What do you think?
---rony
[1] <https://en.wikipedia.org/wiki/Rolling_release>
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
