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

Re: Subversion release planning.

From: <kfogel_at_collab.net>
Date: 2005-06-21 21:53:52 CEST

Branko Čibej <brane@xbc.nu> writes:
> >Solution C -- A Lovely Compromise:
> >
> > Aim to release around a given date, and say that the release will
> > contain one or more new features (or significant differentiators)
> > from the previous maintenance line -- but do not promise any
> > specific new feature. Of course, we can still aim to have certain
> > things done by a certain release, but the point is that a release
> > can still go out the door without those things, as long as there's
> > *something* present to justify the release.
> Isn't this exactly what we've been doing?

Not really. For 1.2, for example, we promised for ages and ages that
locking would be the big feature. We kept that promise, somewhat at
the expense of 1.2's release date IIRC.

Under the new proposal, 1.2 could have come out sooner, with some
other feature if it was ready, and locking would have come out in 1.3

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 21 22:38:18 2005

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.