Subversion Release Planning

There was consensus of people in the summit that we ought to go to predictable time-based releases. Everyone seemed to like 6 month releases, likely in June and December.

The following is just a sketchpad of what might be deliverable in upcoming releases.

1.6: December 2008

• Tree conflicts - files
• Plain-text password storage improvements
• Gnome Keyring and KDE KWallet support
• Caching of SSL certificate passphrase using same mechanisms as passwords
• Single file externals
• Relative URL command line syntax
• BDB forward-deltas
• BDB and fsfs rep sharing
• SQLite usage in WC, some initial code cleanup
• Merge tracking refinements
  • reintegrate improvements to checking for subtree mergeinfo
  • reduce creation of mergeinfo on copy/move
  • consider removing elision and updating mergeinfo on subtrees

1.7: June 2009

• WC rewrite
  • Centralized metadata
  • Huge performance gains
  • Optional/compressed text base
  • Improved API == easier to make future changes
• Tree conflicts -- directories
• Reflective merge algorithm

1.8: December 2009

• Server-side configuration
• New HTTP Protocol
• Unicode encoding fixes
• Tree conflicts -- resolution
• True block/unblock support in merge

1.9: June 2010

• Offline commits

Back to FrontPage