> Am 22.05.2025 um 11:41 schrieb Rony G. Flatscher <rony.flatsc...@wu.ac.at>: > > On 20.05.2025 18:03, ooRexx wrote: >> I just realized that /main/branches/5.1.0/ was moved to >> /main/releases/5.1.0/, not copied, as it was done in earlier releases, >> including 5.0. What is the rationale behind that? I intended to use it for a >> further release test, now that is not possible :-( > Of course, it is possible! > > Just copy main/releases/5.1.0 to wherever you want (including > main/branches/5.1.0, but see below) and work on it! > >> IMO the /main/branches/5.X.Y should stay also after a release. > The rationale to move instead of copy: once a branch turned into a release, > it is not a branch anymore. If however, we would need to create some 5.1.1 > branch for whatever reasons (e.g. bug fixes), then we should create a new > main/branches/5.1.1 (by copying either main/releases/5.1.0 to it and add > selected commits, or copy main/trunk to main/branches/5.1.1 for a direct > release from the then current trunk.) > I think it would have much better to keep the main/branches/5.1.0 (or 5.1 as I would have called it), then one could apply changes that are intended for 5.1.1 DIRECTLY to an existing branch, so that once one would like to release it most of the commit work would already have been done. Now we need to copy back 5.1.0 release to /branches and THEN start unwinding all the fixes.
I will not argue my point any further, I will adjust the script and make a release test som time next week. There is still things to be done. > ---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
