On 23.12.2022 11:52, P.O. Jonsson wrote:
Am 23.12.2022 um 10:09 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>:
On 22.12.2022 21:54, ooRexx wrote:
There should be at maximum 5 versions of every platform, which makes it 10 for
Windows (32/64 bit). We do build and test Windows 7,8.1,10 and recently also 11
but we only upload Windows 10, which should work on all Windows platforms
supported.
It should be the case that the release folder and candidate folder only contain
the very latest builds.
Once there is an agreement on what build should be the last one I will block
the building on Jenkins (or even shut it down for some time)
If the latest build contain the latest documentation I would think that that build should be the
release build from now on.
I suppose we can just rename 5.0.0_Release_Candidate to to 5.0.0 ? I can do
that manually. If there are no objections I will go in and remove the older
versions manually and make sure that we have the latest build for all platforms.
Yes, that would be the best, also please remove 5.0.0beta at the same time.
Be aware that all Artifacts (installers) have the revision in the filename
I assume that I should redirect the Jenkins build to go to 5.1.0 on Sourceforge
and use trunk for SVN after that?
Yes!
---
Once the release is done we should look into the possibilities to make the
current Jenkins scripts flexible in the sense, that the trunk builds have
versions, the release/candidates have only the latest version. Also, it may be
helpful, if it was possible to trigger builds manually. Also, the portable
versions should be produced and uploaded such that everybody interested can
also run different versions of ooRexx in parallel, check them out and compare
them.
If possible this should allow us for future releases to be much faster and
service the community better.
Rony, I know you like to complicate things :-)
:) ... but only for the price to get more flexibility ...
but given that we have had one release in 9 years I see no reason to complicate
the build machine.
No, it should not be made more complex, the intent would be to make it easier for future builds.
E.g. I noted that during the release phase no builds from trunk took place, which is o.k. But why
not allow for both, continuing creating builds for the release branch and for the trunk, if it is
possible?
With rolling releases, it makes sense to automate as much as possible which probably means to add
flexibility where necessary. Currently the expierences and knowledge is very fresh.
Maintaining it now is tedious (because of the large number of platforms) but
simple, Let´s keep it like that. Manually triggering a build is out-of-the-box
on Jenkins, all you need to do is go in a click on the Build button for the
platform you are interested in.
Let us stop here and maybe come back later to this, in the new year maybe.
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
