On 1/29/06, Greg Stein <email@example.com> wrote:
> On Sun, Jan 29, 2006 at 02:23:30PM -0600, firstname.lastname@example.org wrote:
> > One advantage of the shorter release schedule (appx every 4 months) is
> > that when a release encounters unpredictable delays, it still only
> > puts us out at 5 or 6 months, instead of 7 or 8. And if we don't
> > encounter delays, so much the better.
> The question/problem under discussion isn't about when users see the
> release, but how long features have for development before they get
> into a release. With a short cycle and a standard soak, then there is
> *very* little time for feature development.
Really? Subversion 1.4 has been in active development since September
28, when we branched for 1.3. If we branch for Subversion 1.4 in late
February, that means we had 5 months for development.
After branching 1.3, it took 3 months to release the final version of
Subversion. If we branch for 1.4 in February, and Subversion 1.4
follows the same schedule as 1.3, it'll be ready in late May or early
June. That gives us 5 months between releases.
At this rate, new features merged to trunk wait a maximum of 8 months:
- 5 months for feature development
- 3 months for release stabilization
- Total: 8 months
Example: The "wc-replacements" branch was merged to trunk on October
13. If we release Subversion 1.4 in late May, wc-replacements will
have been soaking in trunk for almost 8 months.
Here's another look at the new features, courtesy of Garrett Rooney:
> The specific new features are the WC replacements work (bugfixes and
> speedups to libsvn_wc), svndiff1 (smaller repositories due to
> compression of newly added data in the svndiff format),
> ra_replay/svnsync (repository replication via a new ra layer API), and
> probably something else I've forgotten along the way.
svndiff1 isn't merged to trunk yet, but Daniel Berlin said on December
10 that it's "ready to merge". Should we do the merge now? If it's
ready, let's make sure we merge it before release.
David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jan 30 00:42:13 2006