Subversion 1.7 Support in Flare V8

 Article #: SCC1003F  Product: Flare   Version: 8

Summary:

Flare V8 is now leveraging the new Subversion 1.7 enhancements.

Message: "Your working copy must be upgraded to continue with this operation" when opening projects tied to Subversion Source Control.

Flare V8 will change how the hidden .svn folders appear in the local working copy. There is now only 1 .svn folder at the root, instead of 1 in each folder. According to Subverions release notes for 1.7, this is to pave the way for future enhancements and versions.

Full Description:

  • All Subversions users when opening previous projects in V8, will see a prompt telling them they need to update their local working copy.
    • This must be done in order to use Flare V8 and Subversion integration.
    • Even if you have not upgraded to Subversion 1.7 you will get this prompt. It’s ok, Flare V8 still works with older 1.6 subversion servers
    • Once the project is upgraded, it cannot be opened in Flare V7. You will get a subversion prompt telling you the client is too old.
      • If you must use V7, simply re-import (or rebind) the project from V7.
  • Any user that Binds a project or imports a project in V8 will see no difference.
  • Other users still on Flare V7 will still be able to work on this upgraded project because the upgrade only takes place on the local client side. This only affects the local copies and does not affect the Subversion Server.

 

Snippet from Subversions Website:

A key feature of the changes introduced in Subversion 1.7 is the centralization of working copy metadata storage into a single location. Instead of a .svn directory in every directory in the working copy, Subversion 1.7 working copies have just one .svn directory—in the root of the working copy. This directory includes (among other things) an SQLite-backed database which contains all of the metadata Subversion needs for that working copy.

Attribution:

Last updated:

3/1/2012

Author:

Rob Hollinger

Contributions by:

MadCap QA