On 16.09.2011 14:02, Simon Large wrote:
> Hi Stefan,
> Our release procedure says:
> * When we think we're ready for a release, we create a branch from
> trunk, named after the next release version with an 'x' as the last
> version number, e.g. 1.4.x.
> * From this point on, only bug fixes will go to that branch. No new
> features or resource changes are allowed to go in there.
> * The nightly builds for the stable release is switched over to that
> branch, so users can start testing it.
> * After about a week, a first release candidate is built and uploaded
> for all to test.
> * If no major bugs are found in the RC, we create the official release.
> However if some major bugs are found, those are fixed and another RC
> is created.
> Clearly we are not doing that, for the reasons already indicated here:
> If the procedure creates too much work then we need to change the
> procedure so that it is more realistic given the number of main
> developers (1) and the amount of spare time (0).
> Barring major accidents we are only 2 weeks from the next Subversion release :-)
Why are we not doing that?
Ok, we made an RC without having created the branch, but as the first
sentence mentions we create the branch "when we think we're ready".
After the branch is created, the procedure is the same as above, without
the RC :)
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-09-16 16:11:03 CEST