New Release Procedure

For the purposes of this documentation, the assumed XS release version is v3.8. The steps for a new release are:

1. Push new code to a branch and submit merge/pull request:

git clone [email protected]:AER-RC/cross-sections.git
cd cross-sections
git branch v3.8
git checkout v3.8
... (copy over modified files)
git commit -a -m 'code changes for XS v3.8'
git push origin v3.8

Merging and pulling should be done in the web interface.

Alternatively, commit and push new code to master branch:

git clone [email protected]:AER-RC/cross-sections.git
... (copy over modified files)
git commit -a -m 'code changes for XS v3.8'
git push origin master

2. Draft a new release. Tag and Release Title should be v3.8, and Target should be master. What's New bullets should be added in description.

3. Update Wiki pages (certainly What's New), possibly others.

4. In repositories that are dependent on cross-sections (right now, only LBLRTM), point the cross-sections submodule HEAD to the newest release:

git clone --recursive [email protected]:AER-RC/LBLRTM.git
cd LBLRTM/cross-sections
git checkout v3.8
git commit -a -m 'updated XS to v3.8'
cd ..
git commit cross-sections 'updated XS submodule'

5. Download Release/Tag into /nas/project/rc_static/models/aer_cntnm or model of interest [NEED TO EDIT THIS ITEM!]

mkdir mt_ckd_3.4
cd mt_ckd_3.4
wget --output-document cntnm_v3.4.tar.gz https://github.com/AER-RC/mt-ckd/archive/v3.4.tar.gz
tar xvf cntnm_v3.4.tar.gz
mv mt-ckd-3.4 cntnm

6. Local version update

This procedure is identical to what is done for LBLRTM.