You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by da...@apache.org on 2011/09/14 04:29:14 UTC

svn commit: r1170417 - /subversion/branches/fs-successor-ids/BRANCH-README

Author: danielsh
Date: Wed Sep 14 02:29:14 2011
New Revision: 1170417

URL: http://svn.apache.org/viewvc?rev=1170417&view=rev
Log:
On the fs-successor-ids branch, update BRANCH-README.

* BRANCH-README: Update status and round up a todo list.

Modified:
    subversion/branches/fs-successor-ids/BRANCH-README

Modified: subversion/branches/fs-successor-ids/BRANCH-README
URL: http://svn.apache.org/viewvc/subversion/branches/fs-successor-ids/BRANCH-README?rev=1170417&r1=1170416&r2=1170417&view=diff
==============================================================================
--- subversion/branches/fs-successor-ids/BRANCH-README (original)
+++ subversion/branches/fs-successor-ids/BRANCH-README Wed Sep 14 02:29:14 2011
@@ -48,7 +48,7 @@ one or another flavor of successor (copy
 STATUS
 ======
 
-Only the BDB backend has been tweaked so far.  The code is believed to
+The BDB backend has been tweaked.  The code is believed to
 cover the basic maintenance of the successor ID mapping, adding map
 items when new nodes are created, removing them when nodes are
 deleted.  The code assumes that the only node revisions every removed
@@ -56,26 +56,33 @@ from the filesystem are those which have
 not hold up if an obliteration feature is added, depending on the
 implementation).
 
-The branch needs to implement the correct FS format bumping for both
-backends.
+FSFS has been tweaked too.
 
-The branch needs to be synced with 21 months of trunk changes.
+This branch adds svn_fs_history_next() to the public API.
 
-[ The branch does not currently add any public APIs. ]
+TODO
+====
 
-Lacking also are C unit tests for this functionality.
+- implement FS format bumping for both backends
 
-FSFS support for this enhancement is under development; see below.
+- expand the unit test
 
-'svnadmin verify' could validate the successors cache against the
-revisions and predecessors data.
+- convert all internal APIs to return results via s/array/callback/
 
+- update design docs (both backends) and move out them out of this file (FSFS)
 
-FSFS WHITEBOARD
-===============
+- implement successors data construction logic on top of existing filesystem
+  for 'svnadmin upgrade'
+    http://mid.gmane.org/20110906154244.GA3863@daniel3.local
+    http://mid.gmane.org/20110913172801.GB18110@jack.stsp.name
+
+- danielsh: review FSFS readers code
+
+- (optional) sync merge from trunk
+
+- 'svnadmin verify' could validate the successors cache against the
+  revisions and predecessors data.
 
-TODO: 'svnadmin upgrade'
-(see <ht...@daniel3.local>)
 
 Implementation proposal
 =======================