Changes between Version 10 and Version 11 of TighterSubversionIntegration
- Timestamp:
- Jun 10, 2009, 12:26:48 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TighterSubversionIntegration
v10 v11 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]. 101 101 102 Google's googlecode implementation goes at least partially down this route. The repository root contains the usual 103 trunk, branches, and tags, plus wiki, which has all the wiki pages. Tickets/issues and other project metadata 104 are not stored in SVN, however. 102 Google's googlecode implementation goes at least partially down this route, 103 using the [#Aprivatearea private area] approach. The repository root contains 104 the usual trunk, branches, and tags, plus wiki, which has all the wiki pages. 105 Tickets/issues and other project metadata are not stored in SVN, however. 105 106 For an example, see [http://code.google.com/p/adns-python/ adns-python]. 107 108 BitBucket, on the other hand, uses the [#Aprivaterepository private repository] 109 approach, which is more natural for Mercurial. 106 110 107 111 [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. 108 112 109 113 110 == An Implementation ==111 of using svn for storing WikiPages is in this attachment:svn-wiki-backend-patch 114 === Example Implementation === 115 of using svn for storing WikiPages is in this attachment:svn-wiki-backend-patch. See ticket:1132 for further details.