Difference between revisions of "Version control repository"

From Second Life Wiki
Jump to navigation Jump to search
(w00t)
Line 1: Line 1:
{{CompileNav}}
{{CompileNav}}


Linden Lab doesn't yet provide live access to a central revision control repository for the viewer source code.  However, this is being considered.
Linden Lab runs an official Subversion repository that contains occasional snapshots from the internal Linden Lab source repository.   


== Request for proposals ==
== Using the repository ==


Below is a request for proposals for public Subversion repository hosting.
*  Create a location on your hard drive to check out the code (e.g. Linden Lab developers generally use $HOME/linden)
*  Select which branch you'd like to check out (see [[Source branches]] for explanation of branches)
** release: <nowiki>http://svn.secondlife.com/svn/linden/release</nowiki>
** release-candidate: <nowiki>http://svn.secondlife.com/svn/linden/branches/release-candidate</nowiki>
** maintenance: <nowiki>http://svn.secondlife.com/svn/linden/branches/maintenance</nowiki>
** Branch_1-15-0: <nowiki>http://svn.secondlife.com/svn/linden/branches/Branch_1-15-0</nowiki>


Requirements:
== Browse source ==


*  High capacity, high availability anonymous read access, with corresponding SLA
*  [http://svn.secondlife.com/trac/linden/browser Browse source (using Trac)]
*  Direct user management by Linden Lab (self-service add/remove/disable accounts)
*  [http://svn.secondlife.com/trac/linden Other tools]
*  Self-service password changing for all individual account holders
*  Minimum 40GB capacity
*  Ability to completely delete rogue revisions within one business day
*  Nightly backups
*  Real-time read access to all raw Subversion data files via ssh/sftp or other secure


Additional desirable features:
*  Integration with outside authentication system, either Kerberos or custom XML-RPC based system.
**  If relying on external authentication, user management still needed to provide authorization management


Proposals being accepted through February 9, 2007.
== Write access ==


Please address responses to [mailto:robla@lindenlab.com Rob Lanphier at Linden Lab]
Developers that have signed and submitted [http://secondlife.com/developers/opensource/submitting a contribution agreement] are eligible (not guaranteed) write access to the repository.  Other considerations, such as patches submitted and reasons access is requested will also come into play.
 
== Choices considered ==
 
*  [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
*  [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
* [http://svk.bestpractical.com/view/HomePage svk] - a decentralized revision control system built on top of svn.
* Externally managed repository, via 3rd party site, such as [http://sourceforge.net sourceforge.net],  [http://Berlios.de Berlios.de], or similar.
 
Other systems can be found here:
http://en.wikipedia.org/wiki/Comparison_of_revision_control_software
 
See a discussion of this issue in the [https://lists.secondlife.com/pipermail/sldev/2007-January/thread.html#37 "Version control repository" discussion on SLDev] as well as [[Talk:Version control repository|the talk page for this page]]
 
[[Category:Future Roundtables]]

Revision as of 10:34, 3 May 2007

Open Source Portal

Linden Lab runs an official Subversion repository that contains occasional snapshots from the internal Linden Lab source repository.

Using the repository

  • Create a location on your hard drive to check out the code (e.g. Linden Lab developers generally use $HOME/linden)
  • Select which branch you'd like to check out (see Source branches for explanation of branches)
    • release: http://svn.secondlife.com/svn/linden/release
    • release-candidate: http://svn.secondlife.com/svn/linden/branches/release-candidate
    • maintenance: http://svn.secondlife.com/svn/linden/branches/maintenance
    • Branch_1-15-0: http://svn.secondlife.com/svn/linden/branches/Branch_1-15-0

Browse source


Write access

Developers that have signed and submitted a contribution agreement are eligible (not guaranteed) write access to the repository. Other considerations, such as patches submitted and reasons access is requested will also come into play.

Retrieved from "https://wiki.secondlife.com/w/index.php?title=Version_control_repository&oldid=19637"