Difference between revisions of "HOWTO Create a New Hall D Software Release"

From GlueXWiki
Jump to: navigation, search
m (Instructions updated 04/07/2022)
Line 3: Line 3:
 
''' This should only be done by the Hall D software coordinator '''
 
''' This should only be done by the Hall D software coordinator '''
  
'''1)'''
+
'''1)''' Start with the previous release, usually linked to version.xml. Increment one of the numbers (main, update, bugfix), e.g.:
 
<pre>
 
<pre>
version.xml
+
cp version_5.5.0.xml version_5.6.0.xml
 
</pre>
 
</pre>
  
'''2)''' Source the environment.
+
'''2)''' Edit file, date and description of the xml file:
 
<pre>
 
<pre>
gxenv version.xml
+
<gversions file="version_5.6.0.xml" date="2022-04-07">
 +
<description>Update releases of halld_recon, halld_sim, hdgeant4, and hd_utilities.</description>
 +
</pre>
 +
 
 +
'''3)''' Create new releases of the relevant packages on github.
 +
 
 +
'''4)''' Substitute new releases in xml file, removing eventual dirtags
 +
<pre>
 +
<package name="halld_recon" version="4.36.0"/>
 
</pre>
 
</pre>

Revision as of 13:53, 7 April 2022

Instructions updated 04/07/2022

This should only be done by the Hall D software coordinator

1) Start with the previous release, usually linked to version.xml. Increment one of the numbers (main, update, bugfix), e.g.:

cp version_5.5.0.xml version_5.6.0.xml

2) Edit file, date and description of the xml file:

<gversions file="version_5.6.0.xml" date="2022-04-07">
<description>Update releases of halld_recon, halld_sim, hdgeant4, and hd_utilities.</description>

3) Create new releases of the relevant packages on github.

4) Substitute new releases in xml file, removing eventual dirtags

<package name="halld_recon" version="4.36.0"/>