Branko Čibej <firstname.lastname@example.org> writes:
> 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.
Hmm, looks like we've been flying by the seats of our collective pants
on release schedules :-).
I always thought that micro (patch) release schedules were based more
on what fixes are available than on how many weeks/months have passed
since the previous minor release in that line. If the fixes are for
severe bugs, for example, than a quicker release is justified.
Whether the changes in 1.3.1 meet that criterion is a different
question -- I personally think we could wait for some more. But the
overall point is that it's more about content than timing.
> > 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.
Yeah, I think a month would be enough. We do want the changes to be
on a live repository where is used, for a while...
> (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.)
Why, just this morning, before breakfast :-).
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Jan 29 23:09:04 2006