Difference between revisions of "HOWTO Create a New Hall D Software Release"
From GlueXWiki
m (→Instructions updated 04/07/2022) |
m (→Instructions updated 04/07/2022) |
||
| Line 11: | Line 11: | ||
<pre> | <pre> | ||
<gversions file="version_5.6.0.xml" date="2022-04-07"> | <gversions file="version_5.6.0.xml" date="2022-04-07"> | ||
| − | <description>Update releases of halld_recon, halld_sim, | + | <description>Update releases of amptools, halld_recon, halld_sim, gluex_root_analysis, and hd_utilities.</description> |
</pre> | </pre> | ||
Revision as of 15:07, 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 amptools, halld_recon, halld_sim, gluex_root_analysis, and hd_utilities.</description>
3) Create new releases of the relevant packages on github. The simplest way is to go through this link:
https://halldweb.jlab.org/halld_versions/version.xml
4) Substitute new releases in xml file, removing eventual dirtags
<package name="halld_recon" version="4.36.0"/>
5) Source new xml file, e.g.
gxenv version_5.6.0.xml
6) Add dirtags for each "version mismatch found"
<package name="hdgeant4" version="2.33.0" dirtag="hdr4360"/>
