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

Re: Time for a 1.3.1 release? (without the bdb fixes)

From: Branko Čibej <brane_at_xbc.nu>
Date: 2006-01-28 02:47:28 CET

David James wrote:
> Now that Subversion 1.3.0 has been out for a while, we have
> accumulated a number of very useful fixes for 1.3.1.
What's this rush with releases all of a sudden? 1.3.0 hasn't been out a
month. Our usual schedule was 2--3 months for a patch release.

> I'd say it's time
> for a 1.3.1 release, as soon as we can finish voting on the items in
> STATUS. Could we make it a goal to wrap up the voting next week, so
> that we can release 1.3.1 in short order?
> Given this schedule, I'd like to propose that we delay the BDB fixes
> (proposed by brane) until after 1.3.1. These fixes to BDB library will
> be very helpful for end users, but I think we need to test them
> thoroughly on production repositories (such as svn.collab.net) for a
> few months before we push it out in any release.
I disagree about the "few months". Yes, they need to be tested in
production (and also a pool cleanup bug fixed, one which will probably
involve not using pools in the first place, sigh). But these changes
have already been tested a lot more thoroughly than most things that go
into a patch, or even minor, release.

(Just as an example -- when did you last run 9 stress.pl's, three local,
three over svnserve and three over mod_dav_svn, against the same
repository, on a dual-cpu machine, with another shell doing "svn
crashtest" on that repo every second? And without wedging the
repository, I might add.)

-- Brane

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 28 02:47:42 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.