On Thu, Dec 22, 2022 at 7:55 AM ooRexx wrote:
> We are currently making all changes to
>
> /oorexx/code-0/docs/branches/5.0.0/
> /oorexx/code-0/main/branches/5.0.0/
>
> But the document where to document the changes *release-steps.txt* is in
> the trunk
>
> /oorexx/code-0/main/trunk/
>
> Are we supposed to keep two separat SVN trees active while this is going
> on?
>
Yes, the branch is taken to be a frozen in time version where all changes
necessary to complete
the release can be made. The trunk version is now open for anybody to make
changes to add things
for the next feature release. The downside is some of the changes made to
the release branch also
need to be made to the trunk version. In theory, those sorts of things
should have been done before
creating the release candidate branch, but there's inevitably something
that slips through the cracks.
btw, we should probably add some notes about checking author lists, etc. as
changes that should be
made before creating the release candidate branch.
Rick
>
> I ask because this exercise is a "first" for me
>
> Hälsningar/Regards/Grüsse,
> ooRexx
> 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
