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

Re: Releasing 1.6

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Thu, 07 Aug 2008 21:34:40 +0200

Karl Fogel wrote:
> "David Glasser" <glasser_at_davidglasser.net> writes:
>> On Thu, Aug 7, 2008 at 10:01 AM, Arfrever Frehtes Taifersar Arahesis
>> <arfrever.fta_at_gmail.com> wrote:
>>> I would like very much that 1.6 have these features:
>>> * `svn diff --svnpatch` / `svn patch`
>>> * ctypes Python bindings
>>> * File externals
>>> * Improved handling of tree conflicts
>>> I think that we should finish implementing these features before
>>> creating the 1.6.x branch.
>> This sort of approach to release management was what caused the 1.5 disaster.
Hm, this statement is a bit to general a response to Arfrever's email.
Yes defining a number of 'should have' features for the next release is a risk, certainly so in an open source environment. OTOH, I think we should all list the features we like to see implemented, at least,
those where we are personally planning to work on.

We can prioritize such a list based on importance of the feature, where
importance is the number of devs willing to spend time on them. We
really need a way to gather all devs around a set of key features.
Release disasters happen when 20 new features are started at the sam
time, and in the end not a single one is finished.

> Agreed. We should release 1.6 about six months after 1.5 -- whatever is
> ready is ready :-).
Agreed on the six months.


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-07 21:34:59 CEST

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

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