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

Re: TSVN release cycles

From: Joseph Galbraith <galb_at_vandyke.com>
Date: Wed, 12 May 2010 13:38:14 -0600

On 5/12/2010 12:07, Stefan Küng wrote:
> On 12.05.2010 12:31, Stefan Fuhrmann wrote:
>
>> Maybe, I got yet another idea:
>>
>> * stick with the SVN release schedule for 1.7
>> * once 1.7.0 got released, request a guesstimate for 1.8
>> a) believable 6 month time-frame -> stay in sync w/ SVN
>> b) likely to be 9 month or more -> announce change in TSVN release
>> policy
>> * new release policy (if applicable):
>> - a feature release about every 6 months
>> - the last feature release may be rather close to the next SVN release
>> (but stop releasing new features when SVN enters stabilization)
>> - name releases closely to SVN version numbering:
>> * 1.8.0, 1.8.1, ... for the initial feature set releases
>> * 1.8.10, 1.8.11, ... for the second feature releases
>> * 1.8.20, etc for the third feature release etc.
>> (we don't release more frequently than every 3 weeks,
>> so patch level numbers won't overlap)
>>
>> That way we wouldn't appear to change policies at a "whim"
>> but have plenty of time to inform / educate users upfront, instead.
>
> +1 from me.

I like this (or +1 from me too.)

It seems like I just saw something from the SVN crew that
basically said they were giving up on the 6-month release
cycle because the easy problems were solved and they were
now left with problems that just didn't fit a 6-month
release cycle.

Thanks,

Joseph

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2608289

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-12 21:38:14 CEST

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