[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: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-01-22 19:34:00 CET

On 1/22/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:

> What's the plan for 1.4? Timeline? Features? I've seen the issue tracker's
> list, but that's fairly vague and doesn't have the timeline as far as I can
> tell. (Project status just says 'future'.)

"The Plan", as I understand it, is for 1.4.x to happen sooner after
1.3.x than 1.3.x was after 1.2.x. The general idea is that there are
enough interesting new things already in trunk that we should really
avoid sitting around for months and months before releasing them.

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.

I believe the timeline people had been kicking around were 3-4 months
from now, although I can't remember exactly. It's a conversation that
needs to occur in order for it to get finalized, and I don't think
that's happened yet.

> As discussed back in November, I'll be starting work on the serf integration
> this week with the goal to be wrapped up by April. As we talked about then,
> I'm planning to do this work in the trunk. neon will, of course, still be the
> default for now. However, I'd like to be able to plan how the serf work will
> be integrated into the next minor release.

As long as it's not going to be turned on by default, I don't see any
problem with the code going into trunk.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jan 22 19:34:21 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.