[u/mrichter/AliRoot.git] / html / management.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
               "http://www.w3.org/TR/REC-html40/loose.dtd">
<HTML>
<HEAD>
<TITLE>Code Management</TITLE>
<link rev="made" href="mailto:Federico.Carminati@cern.ch">
<STYLE>
BODY	{	
	background:	#FFFFFF;
	}	

COL, COLGROUP, TABLE, TBODY, TD, TR	{	
	color:	black;
	text-decoration:	none;
	border-color:	black;
	border-style:	none;
	background:	#FFFFFF;
	}			

</STYLE>
<link rel="stylesheet" href="http://www.w3.org/StyleSheets/Core/Swiss" type="text/css">
</HEAD>

<BODY background=#FFFFFF>
<TABLE>
<TR>
<TD><img src="picts/MadHatter.gif" alt="ALICE Off-line Project Logo">
<TD><img src="picts/management_name.gif" alt="Code Management">
<TD><img src="picts/AliceLogo.gif" alt="ALICE Logo">
</TR>
</TABLE>

<h2>Code Management</h2>

<p> The code is maintained under <a
href="http://www.cyclic.com/"><b>cvs</b></a>. <b>cvs</b> allows parallel
concurrent development by different authors, but for the moment only the
versioning capabilities of <b>cvs</b> are used. The code is maintained by
<b>cvs</b> into a <em>repository</em>.

<p> A <em>remote cvs server</em> has been installed, that allows read-only
access to the AliRoot code for download. To gain access to it, it is
necessary to have an internet connection to CERN. It is practical to define
an alias:

<p><b><center>
cvsa = cvs -d :pserver:cvs@pcepaip01.cern.ch:/soft/cvsroot
</center></b>

<p> To activate the access to the remote repository the command <b>cvsa
login</b> should be issued the first time. The user is then prompted to
enter the password that is <em>cvs</b>. This password is stored once and
forall in a file in his/her home directory, so there is no need to repeat 
the login procedure.

<p> All <em>read</em> commands of <b>cvs</b> are available to download
code, compare local versions with the official ones and so on. The reader
is referred to the <b>cvs</b> manual for more information. <em>Write</em>
commands are forbidden, and an error message is issued.

<p> At the moment the control of the <b>cvs</b> repository is in the hands
of one person, but with time a more flexible policy will be put in place,
where project coordinators will be allowed to modify the pre-release
version of the code independently.

<p> The development of the code and the release procedure is explained by
this schema:

<br><center><img src="picts/cvs_release.gif" height=75%
               alt="The ALICE release procedure"></center>

<p> When a release is tagged (Release-3-01), the a <em>cvs branch</em> is
created (Release-3-01-Patch-00) and this is the code distributed and
installed at CERN. Patches to the released code are tagged on this branch,
while pre-releases are tagged on the main branch.

<p> When the release code is ready, it is tagged, and the Patch-00 branch
is created. The previous release code and libraries are moved in the old
directory tree on the machines where the AliRoot is installed, the Patch-00
of the new release is moved onto the pro directory tree and the cycle begins
again.

<p> As said before we are studying how to allow single Detector Groups to
tag their own module, while maintaining a single tag for the release.

<hr>
<address>
          <script language="JavaScript">
             document.write("Last modified "+ document.lastModified)
             // end of script -->
          </script>
by <a href="mailto:Federico.Carminati@cern.ch">Federico Carminati</a>
</address>
</BODY>
</HTML>
Commit	Line	Data
14c31136	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
	2	"http://www.w3.org/TR/REC-html40/loose.dtd">
	3	<HTML>
	4	<HEAD>
	5	<TITLE>Code Management</TITLE>
	6	<link rev="made" href="mailto:Federico.Carminati@cern.ch">
	7	<STYLE>
	8	BODY {
	9	background: #FFFFFF;
	10	}
	11
	12	COL, COLGROUP, TABLE, TBODY, TD, TR {
	13	color: black;
	14	text-decoration: none;
	15	border-color: black;
	16	border-style: none;
	17	background: #FFFFFF;
	18	}
	19
	20	</STYLE>
	21	<link rel="stylesheet" href="http://www.w3.org/StyleSheets/Core/Swiss" type="text/css">
	22	</HEAD>
	23
	24	<BODY background=#FFFFFF>
	25	<TABLE>
	26	<TR>
	27	<TD><img src="picts/MadHatter.gif" alt="ALICE Off-line Project Logo">
	28	<TD><img src="picts/management_name.gif" alt="Code Management">
	29	<TD><img src="picts/AliceLogo.gif" alt="ALICE Logo">
	30	</TR>
	31	</TABLE>
	32
	33	<h2>Code Management</h2>
	34
	35	<p> The code is maintained under <a
	36	href="http://www.cyclic.com/"><b>cvs</b></a>. <b>cvs</b> allows parallel
	37	concurrent development by different authors, but for the moment only the
	38	versioning capabilities of <b>cvs</b> are used. The code is maintained by
	39	<b>cvs</b> into a <em>repository</em>.
	40
	41	<p> A <em>remote cvs server</em> has been installed, that allows read-only
	42	access to the AliRoot code for download. To gain access to it, it is
	43	necessary to have an internet connection to CERN. It is practical to define
	44	an alias:
	45
	46	<p><b><center>
	47	cvsa = cvs -d :pserver:cvs@pcepaip01.cern.ch:/soft/cvsroot
	48	</center></b>
	49
	50	<p> To activate the access to the remote repository the command <b>cvsa
	51	login</b> should be issued the first time. The user is then prompted to
	52	enter the password that is <em>cvs</b>. This password is stored once and
	53	forall in a file in his/her home directory, so there is no need to repeat
	54	the login procedure.
	55
	56	<p> All <em>read</em> commands of <b>cvs</b> are available to download
	57	code, compare local versions with the official ones and so on. The reader
	58	is referred to the <b>cvs</b> manual for more information. <em>Write</em>
	59	commands are forbidden, and an error message is issued.
	60
	61	<p> At the moment the control of the <b>cvs</b> repository is in the hands
	62	of one person, but with time a more flexible policy will be put in place,
	63	where project coordinators will be allowed to modify the pre-release
	64	version of the code independently.
65
66	<p> The development of the code and the release procedure is explained by
67	this schema:
68
69	<br><center><img src="picts/cvs_release.gif" height=75%
70	alt="The ALICE release procedure"></center>
71
72	<p> When a release is tagged (Release-3-01), the a <em>cvs branch</em> is
73	created (Release-3-01-Patch-00) and this is the code distributed and
74	installed at CERN. Patches to the released code are tagged on this branch,
75	while pre-releases are tagged on the main branch.
76
77	<p> When the release code is ready, it is tagged, and the Patch-00 branch
78	is created. The previous release code and libraries are moved in the old
79	directory tree on the machines where the AliRoot is installed, the Patch-00
80	of the new release is moved onto the pro directory tree and the cycle begins
81	again.
82
83	<p> As said before we are studying how to allow single Detector Groups to
84	tag their own module, while maintaining a single tag for the release.
85
86	<hr>
87	<address>
88	<script language="JavaScript">
89	document.write("Last modified "+ document.lastModified)
90	// end of script -->
91	</script>
92	by <a href="mailto:Federico.Carminati@cern.ch">Federico Carminati</a>
93	</address>
94	</BODY>
95	</HTML>