Difference between revisions of "Version control repository"
Jump to navigation
Jump to search
Rob Linden (talk | contribs) |
|||
| Line 4: | Line 4: | ||
Choices to consider | Choices to consider | ||
* Subversion - default choice, and the obvious "safe" choice. Pros: familiar to us, used by a lot of people Cons: very centralized model; need to give people access to facilitate effective collaboration | * [http://subversion.tigris.org/ Subversion] - default choice, and the obvious "safe" choice. Pros: familiar to us, used by a lot of people Cons: very centralized model; need to give people access to facilitate effective collaboration | ||
* Mercurial - bleeding edge choice. Pros: Distributed model makes it easier for anyone to distribute patchsets off of the main codebase without needing a central host. Much easier to maintain a private branch. Cons: more complicated model, less familiar, much newer system (I've never used it, just received a recommendation) [http:// | * [http://www.selenic.com/mercurial/ Mercurial] - bleeding edge choice. Pros: Distributed model makes it easier for anyone to distribute patchsets off of the main codebase without needing a central host. Much easier to maintain a private branch. Cons: more complicated model, less familiar, much newer system (I've never used it, just received a recommendation) | ||
* [http://svk.bestpractical.com/view/HomePage svk] - a decentralized revision control system built on top of svn. | |||
Other systems can be found here: | Other systems can be found here: | ||
Revision as of 09:17, 2 January 2007
Linden Lab doesn't yet provide live access to a central revision control repository for the viewer source code. However, this is being considered.
Choices to consider
- Subversion - default choice, and the obvious "safe" choice. Pros: familiar to us, used by a lot of people Cons: very centralized model; need to give people access to facilitate effective collaboration
- Mercurial - bleeding edge choice. Pros: Distributed model makes it easier for anyone to distribute patchsets off of the main codebase without needing a central host. Much easier to maintain a private branch. Cons: more complicated model, less familiar, much newer system (I've never used it, just received a recommendation)
- svk - a decentralized revision control system built on top of svn.
Other systems can be found here: http://en.wikipedia.org/wiki/Comparison_of_revision_control_software