Changes between Version 10 and Version 11 of TighterSubversionIntegration

Timestamp:

Jun 10, 2009, 12:26:48 PM (15 years ago)

Author:

Christian Boos

Comment:

mention BitBucket

TighterSubversionIntegration

@@ -100 +100 @@
 There had been a discussion about the pros and cons of integrating Trac with SVN more tightly. The discussion is summarized on the page [wiki:WhySQLite WhySQLite].
 
-Google's googlecode implementation goes at least partially down this route. The repository root contains the usual
-trunk, branches, and tags, plus wiki, which has all the wiki pages. Tickets/issues and other project metadata
-are not stored in SVN, however.
+Google's googlecode implementation goes at least partially down this route,
+using the [#Aprivatearea private area] approach. The repository root contains
+the usual trunk, branches, and tags, plus wiki, which has all the wiki pages.
+Tickets/issues and other project metadata are not stored in SVN, however.
 For an example, see [http://code.google.com/p/adns-python/ adns-python].
+
+BitBucket, on the other hand, uses the [#Aprivaterepository private repository] 
+approach, which is more natural for Mercurial.
 
 [http://www.ditrack.org/ DITrack] is a ''free, open source, lightweight, distributed issue tracking system implemented in Python'' that ''does'' store tickets/issues and other project metadata directly in SVN.
 
 
-== An Implementation == 
-of using svn for storing WikiPages is in this attachment:svn-wiki-backend-patch . See ticket:1132 for further details.
+=== Example Implementation ===
+of using svn for storing WikiPages is in this attachment:svn-wiki-backend-patch. See ticket:1132 for further details.