[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Update the release procedure?

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Fri, 16 Sep 2011 15:53:19 +0100

On 16 September 2011 15:10, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> 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:
>> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2834031
>>
>> 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 :)

In that case my only issue is with the terminology. We should have
called our RC a Beta instead. In reality it was no different from any
other nightly build.

Having said that, the point of a stable branch is that we get lots of
people to test our RC and fix only the bugs that they find. But I
suppose we were never going to have a lot of testers anyway,
particularly with the WCNG format change making it a one-way trip to
1.7 land. We have some very good testers, but not a large number of
them, so most of the real-world testing is going to come after 1.7.0
is released :-/

So I am (reluctantly) agreeing with the strategy ;-)

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2839975
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-09-16 16:53:26 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.