Changes between Version 4 and Version 5 of MapGuideRfc111

Timestamp:

Jan 10, 2012, 9:24:14 PM (12 years ago)

Author:

jng

Comment:

--

MapGuideRfc111

@@ -60 +60 @@
 This RFC imposes some constraints on the build infrastructure that will produce the MapGuide installer.
 
- 1. Due to working copy metadata changes [introduced with Subversion 1.7 http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng], the build machine that will produce the MGOS installer needs to use Subversion 1.6 or older. This way, WC compatibility is retained with SVN 1.6 or older clients. For SVN 1.7 or newer clients, they can detect that these .svn directories are older versions and will direct the user to upgrade said working copies to the 1.7 format.
+ 1. Due to working copy metadata changes [http://subversion.apache.org/docs/release-notes/1.7.html#wc-ng introduced with Subversion 1.7], the build machine that will produce the MGOS installer needs to use Subversion 1.6 or older. This way, WC compatibility is retained with SVN 1.6 or older clients. For SVN 1.7 or newer clients, they can detect that these .svn directories are older versions and will direct the user to upgrade said working copies to the 1.7 format.
 
  2. The installer build must be performed against a SVN working copy (<= 1.6) and not an ***export*** of an SVN repo/working copy. Exported copies lose all svn metadata that this RFC aims to preserve.