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

Re: Release targets and timeline for 1.4?

From: Ben Collins-Sussman <sussman_at_red-bean.com>
Date: 2006-01-30 04:38:57 CET

FWIW, this project has never had any official policy regarding
time-schedules and releases.

After releasing 1.0 in February 2004, we spent the following few
months debatiing about what the 'next big features' should be... and
all the while we were heads-down, focusing on releasing patch-releases
in March, Aprli, May, June, July.

By August, we still weren't sure of our roadmap. But then somebody
turned around and said, "hey wait, we weren't planning on releasing
1.1 yet, but heck, look at all these features: FSFS, symlinks,
pegrevs... we've got enough for 1.1 already!" So we released 1.1 in
September. Totally unplanned.

So we've never released on a timetable. Our precedent has always
been: "we do the next minor release whenever we've got 'enough' new
things to justify it."

And that's what's going on here: a number of people are saying that
trunk has surpassed the magic fuzzy threshold of 'new things' that
justify a new release. If serf is fully functional and butt-kicking
come next April, then that will probably be enough (or really close)
to push trunk over the same magic threshold to justify a freeze for

In other words, I don't think the argument "hold 1.4 for serf! else
it won't be out till 2007!" has any truth to it. Serf is going to be
a big deal. Whenever it's ready, it will almost certainly cause a 1.5
to happen... there's no rule here that says it will have to wait for
the next bus in 6 months. In the meantime, I think we *do* have
enough new stuff for 1.4 right now.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 30 04:39:24 2006

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.