SVN: Difference between revisions

Jump to navigation Jump to search
1,356 bytes added ,  17 January 2007
Add repository structure info.
m (Reverted edit of Hhxjxc, changed back to last version by Rflint)
(Add repository structure info.)
Line 2: Line 2:


[http://weblogs.mozillazine.org/preed/2006/08/subversive_subversion_conversi.html Get preed's take on it]
[http://weblogs.mozillazine.org/preed/2006/08/subversive_subversion_conversi.html Get preed's take on it]
=Repository Structure=
The repository is laid out, generally, as follows:
$project/trunk
$project/$Branch_Name
$project/releases
$project/labels
$project/projects/$Project_Name
$project/people/$User
where
* <tt>$project</tt> is the project name (defined later)
* <tt>trunk</tt> is the "root branch"/trunk
* <tt>$Branch_Name/</tt> are the (active?) branches (i.e. MOZILLA_1_8_BRANCH, MOZILLA_1_8_0_BRANCH, etc.) These will include both release and development branches.
* <tt>releases/</tt> are release tags, i.e. FIREFOX_1_5_0_7_RELEASE; they are not writable.
* <tt>labels/</tt> are tags that aren't (necessarily) simple <tt>svn cp</tt>'s; that is, they may have "cherry picked" fixes, and represent uses like the current AUS2_STAGING and AUS2_PRODUCTION tags.
* <tt>$project/projects/$Project_Name</tt> is an area for "project branches," branches that multiple people are working on/interested in, i.e. the "REFLOW" branch.
* <tt>$project/people/$User</tt> is an area for "personal branches," areas of development that you're working on and will merge onto either project branches or development branches.
<tt>$project</tt> will be defined on a case-by-case basis.
Remora/Addons3 is being developed in /addons; Mozilla Labs projects will go in labs/$projectName.
The goal is to not pollute the / namespace with too many individual projects.


=How to get an account=
=How to get an account=
156

edits

Navigation menu