Re: STATUS of 1.6

Any new updated on this? What can we do to get TODO cleaned up and
cut this release? For those of you that are "signed up" for these
items is there anything that can be done to help? Review a branch,
write a test etc.?

Here is the current list, it is pretty much the same list we've had
for 3-4 weeks:

Blocker:

 * #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. [julianfoad]
   See: <http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1019712>.

 * Review the new "svn_dirent/svn_uri" API and ensure we aren't putting
   functions into the public name space that we won't want to support.
   See <http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1010183>.

 * #3209: Tests XFAIL due to changed tree-conflicts behaviour
     http://svn.haxx.se/dev/archive-2009-01/0538.shtml summarizes the tests
     that are failing because of real differences in pre-TC vs. post-TC
     functionality.

 * Fix failing JavaHL test. The root cause is a change made in r35199 as part
   of the work for issue #3356.

Optional:

 * Tree conflicts - non-essential issues:

   - #3329: Update/switch fails if the target itself is a tree conflict victim.
     Should print a 'Skipped' message instead. Update of an item that is
     inside a tree conflict, and that no longer exists in the repo, does
     nothing. Should print a 'Skipped' message instead.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1059273