We are getting close to creating the 1.6.x branch.  This file lists the tasks
we want to complete before branching.  "Blocker" tasks must be done before we
branch, while "optional" tasks would be nice to have completed, but aren't
essential.

Tasks which need to happen before the 1.6.0 release, but aren't related to when
we branch should be put in the issue tracker with the 1.6 milestone.

Blocker:

 * Properly wrap BDB rep-sharing code for use in pre-1.6 FS formats, as
   noted by cmpilato here: http://svn.haxx.se/dev/archive-2008-10/0968.shtml
   [STATUS:  cmpilato is on this]

 * Add 'svnadmin --pre-1.6-compatible', or preferably something more
   generic (--compatible-with=X.Y or somesuch).

Optional:

 * Merge the sparse-directories deselection branch, as noted by kfogel:
   http://svn.haxx.se/dev/archive-2008-10/1001.shtml

 * Secure certificate passphrase caching on Windows, to bring it upto the
   same level as the other password stores. (Issue 2489)

We are getting close to creating the 1.6.x branch.  This file lists the tasks
we want to complete before branching.  "Blocker" tasks must be done before we
branch, while "optional" tasks would be nice to have completed, but aren't
essential.

Tasks which need to happen before the 1.6.0 release, but aren't related to when
we branch should be put in the issue tracker with the 1.6 milestone.

Blocker:

 * Lose the FSGUIDs BDB stuff, and use a unique key specific to the
   checksum-reps table.  (It was a fine idea, but cmpilato worries
   about the additional contention if we move toward a universal
   source of uniqueness.)  This also will simply some of the
   rep-sharing format-conditional logic.

 * Add 'svnadmin --pre-1.6-compatible', or preferably something more
   generic (--compatible-with=X.Y or somesuch).

Optional:

 * Merge the sparse-directories deselection branch, as noted by kfogel:
   http://svn.haxx.se/dev/archive-2008-10/1001.shtml

 * Secure certificate passphrase caching on Windows, to bring it upto the
   same level as the other password stores. (Issue 2489)

Remove a TODO item, and add another.
Remove a TODO item, and add another.
