> Branko Čibej <email@example.com> writes:
>>Thanks for the review and tests, everyone. I've committed this in
>>r18882, and the BDB-4.4-related changes should be complete now.
>>I've also updated STATUS for 1.3.x; please review and vote for r18144, etc.
> Thank you, Brane!
> I will review & vote. +1 on letting 1.3.2 out very soon after 1.3.1
> (within weeks, if we can), in order to get this change out to the
> Another strategy would be to release 1.4 soon, with these fixes and
> some new cancellation responsiveness (à la DannyB, though perhaps that
> should be "au DannyB") in the command-line client. The reason these
> two great tastes go great together is that raw-exit cancellation
> becomes more acceptable for file:// users if BDB is less sensitive to
> unplanned exits.
> Any thoughts on the merits of 1.3.2 vs 1.4 for your changes?
As I've stated in the past, I want us to run this code on svn.collab.net
*before* we release it to the public in a *final* tarball. There also
exists a policy (a soft one, one of our own making, but IMO a *good* one) of
only running publicly released code on svn.collab.net. Taken together, that
means Brane's work sees it first public release in 1.4.0-rc1, at which time
svn.collab.net and other folks who accept RCs for testing can start playing
with this code.
So, in terms of in which release to put this stuff:
-1 on 1.3.2
+1 on 1.4.0
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Mar 14 19:16:56 2006