Am 19.04.2017 um 18:18 schrieb Andrea Pescetti:
Matthias Seidel wrote:
But as I understand it, the SVN tag is done after the (last) RC is
promoted to be final. (That is the point where we know the Revision to
checkout). So it should be further down in the documentation.
Correct. It happens after a successful vote, and the tag is done
retroactively (but usually a few hours/days later, not six months later
as it happened this time!).
before changing the documentation I want to clarify the following:
OK, but then we need to make a difference which version type we are
talking about.
1. Mirco (x.y.Z) or minor version (x.Y.z)
This may work as we continue the work on an already branched code. So,
it's OK to do some hacking until the final release and then to tag the
specific SVN revision.
2. Major version (X.y.z)
But for this it's not working. Here we first need to agree at which
point we create a new branch from trunk that will be used for a new
major release.
As our last major release is long ago, it's not that common in our
processes. ;-)
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
