[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Status of TODO-1.6

From: Hyrum K. Wright <hyrum_wright_at_mail.utexas.edu>
Date: Wed, 24 Dec 2008 11:30:21 -0600

The following items are listed as blocking the branch of 1.6.x:

 * Actually document how to build with SQLite (ie, make the part in
   INSTALL not blank, explain how to build against a newer version
   of SQLite than what may be installed in your system, figure out
   if the text in sqlite.m4 about being able to use a sqlite/
   subdirectory is in any way true, etc etc)

I don't think this should block the branch, but we should certainly update the
docs and/or build system prior to 1.6.0.

 * #3334: Tree conflicts "merry-go-round" about update updating the base.
   Julian Foad is working on this. Done for when victim is a file, still
   doing for when victim is a directory.

Julian, I understand that you are working on this. Do you have an estimate for
when you might be finished?

 * #3343: Switch to skel for TC information, rather than using another
   serialization format. (Also listed under "Optional". Not really a blocker?)

Greg mentioned that he's 80% done with the implementation. Greg, do you have an
estimate on this item?

 * Test failures in tree conflicts tests on RA-Serf:

Who's looking at this? Serf people? Tree conflicts folks? Nobody?

 * Test failures in Ruby bindings.

These just look like they are the result of wrong expectations due to tree
conflicts, but my understanding of ruby and the swig-rb bindings is so
rudimentary as to remove all confidence in my ability to track it down. Kou,
Joe, any suggestions?

Thanks for everybody's patience as we try to track down the last of the 1.6
issues. Once we receive estimates of when these items will be looked at, we can
have a better idea of when we can branch.



Received on 2008-12-24 18:30:58 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.