After emails phone conversation, we (Greg Stein, Ben, Mike, me, a few
others) agreed on this plan:
- Include the #1429 checkout improvements into 0.33 (because it's a
big improvement, not likely to lead to repository corruption, and
at this point just needs wide exposure to find any compatibility
problems)
- Merge the #1578 fs history algorithm fixes to trunk immediately
after 0.33 (because those are subtle and it would be good to have
a gentler review & ramp-up time for them; and also we didn't want
to combine an fs schema change with a working copy format upgrade
*and* a client/server protocol upgrade)
- Merge the #1595 transaction removal improvements to trunk right
after 0.33, because they are non-trivial, and Mike only has 24
hours in a day and doesn't want to rush them into a release :-).
Also, same concerns about giving them some "soak time" apply. In
general, it's nice to have a change be in HEAD for a while before
it appears in a blessed release, though we're making an exception
for #1429 above.
- 0.33 will still be Alpha. Either 0.34 or 0.35 will be Beta;
we'll make that call when we have a better impression of their
stability.
So. Don't want to be some private Star Chamber here, so if anyone
thinks this is a wildly bad plan, please speak up :-). But we think
it's a good compromise between stability & distributing improvements.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Nov 13 17:38:10 2003