> > I also feel that we seem to be too hung up on creating a 'perfect'
> > release. For example, we've had enough signatures for 1.4.0-rc1 to
> > release for a while, but we held it up because of a theoretical problem
> > that only manifested itself with BDB-backed --bdb-txn-nosync repositories.
>
> Um. No. This was no theoretical problem. Tests were failing. Garrett and
> I both experienced the problem independently. We held up the 1.4.0-rc1
> release because we felt rc2 was gonna be out in a matter of days. In
> retrospect, that might not have been such a good plan. Maybe better to
> release rc1 with a warning message about known problems (I mean, I'm running
> rc1 on svn.collab.net right now with no issues, so presumably others could,
> too) and then continue as usual towards rc2.
Right, but we use in our test suite an option which we explicitly
advise against for production environments.
Also, I said that we definitely should have released RC1 after the
initial fix: it may not have been the perfect one, but it did work for
that moment and the perfect fix could have been in RC2...
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 10 18:00:29 2006