Subversion/layout
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. MediaWiki used the Subversion version control system, but has since migrated MediaWiki core and nearly all extensions to Git. |
Current
editThe current layout was migrated from CVS. There are a few annoyances:
- Many different projects are mixed together
- There's not an easy mediawiki-version snapshot available for extensions, though it could be done manually
- version branch and tag names are ugly :)
- svnroot
- mediawiki
- trunk
- phase3
- extensions
- branches
- REL1_9
- phase3
- REL1_9
- tags
- REL1_9_0
- phase3
- REL1_9_0
- trunk
- mediawiki
Proposal 1
edit- Renames branches and tags to clean style
- but... no room for extensions in the version branches. since extensions aren't always properly maintained for backwards compatibility this can be an annoyance
- svnroot
- mediawiki
- trunk
- mediawiki
- extensions
- branches
- 1.9 mediawiki only
- tags
- 1.9.0 mediawiki only
- trunk
- mediawiki
Proposal 2
edit- cleans up branch/tag names
- keeps the pretty subdirectories so mediawiki and extensions can be versioned together
- but... what to do about other stuff? leave it where it is (lots of dirs in 'trunk') or try to rearrange things so mediawiki/trunk is just mediawiki & extensions?
- svnroot
- mediawiki
- trunk
- mediawiki
- extensions
- branches
- 1.9
- mediawiki
- extensions
- 1.9
- tags
- 1.9.0
- mediawiki
- extensions
- 1.9.0
- trunk
- mediawiki
either move everything _else_ out of trunk to another area or.... hmm
Proposal 3
edit- separates mediawiki and extensions to separate modules
- looks like it would be harder to make and maintain consistent snapshots between mw itself and the extensions module
- svnroot
- mediawiki
- trunk
- branches
- 1.9
- tags
- 1.9.0
- mw-extensions
- trunk
- branches
- tags
- mediawiki