On Mon, Oct 04, 2004 at 03:48:19PM -0600, Michael W Thelen wrote:
> I wouldn't say I feel strongly about it, but I would lean toward
> releasing 1.1.1 (and possibly 1.0.9) with a fix. The reason is that
> I've been hyping Subversion 1.1 at my company, and everyone has been
> excited about upgrading. But the slowdown introduced with the security
> fix is a showstopper for us, and the security fix itself is one that we
> want to have, so we now have a few choices:
>
> - Stick with 1.0.7 (miss out on 1.1 features and miss the security fix)
> - Upgrade to 1.0.8, patched with r11211 (miss 1.1 features, get the
> security fix, but run a custom version)
> - Upgrade to 1.1.0-rc3 (gain 1.1 features but miss the security fix)
> - Upgrade to 1.1.0, patched with r11211 (gain 1.1 features and the
> security fix, but run a custom version)
> None of these options are too appealing... we'll probably go with the
> last option since we want the security fix and 1.1 features, without the
> slowdown. That would work, but I'd rather run a 1.1 released version
> instead. I suspect there may be others in the same boat, so I think
> releasing 1.1.1 soon would be a good idea.
I just don't think a slow down of a command that isn't used that often,
is a serious enough issue to justify a release now. People are making
it sound like the command doesn't work, it does. It's just slower than
it would be otherwise. Is it inconvient, yes. Will we fix it, yes.
But we've got other issues that we'd look really bad releasing a 1.1.1
without fixing. I just don't see a 1.1.1 release any earlier than 2 or
3 weeks out.
--
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 Oct 5 00:13:55 2004