On Mon, Dec 20, 2004 at 09:49:59PM +0100, Tobias_Ringström wrote:
> While I don't have a problem with delaying the release in general, I
> don't understand why that fix in particular would be that important. In
> fact, I wonder what it's doing in 1.1.x at all. It's hardly an important
> bug fix, and the solution is not completely trivial, at least not in the
> sense that it's 100% risk free. On top of that I wonder how many people
> really need it. One? Two? If they are still running a pre 0.14
> Subversion, they can either use trunk to convert the repository or wait
> for 1.2, IMO.
My decision to wait was based upon the fact that it basically had 3
votes but that one of the voters, maxb, found a problem and fixed it and
that the other 2 voters should have the opportunity to review it.
So I could either punt the issue and ship 1.1.2 without it and then
it'll probably be a month or so before we do another release... Or I
could rush people to review it more. Since the code isn't entirely
trivial I took the middle ground. Push the release back 1 day and give
people time to look at it, while saying that I wouldn't delay the
release more than one day...
It was important enough that the change warrented 3 +1s. It just needed
more time to get finished up. If we can't get it figured out by
tomorrow we punt it and releaes 1.1.2 anyway.
While 1.1.2 has some nice fixes in it I don't think there is anything
earth shatteringly important in it that can't wait till tomorrow. Not
to mention I suspect not many people will feel like messing with it
anyway this week due to the holidays.
--
Ben Reser <ben@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Dec 21 00:49:40 2004