New Release Procedure

For the purposes of this documentation, the assumed aer_rt_release release version is v1.0. The steps for a new release are:

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

git clone git@github.com:AER-RC/aer_rt_utils.git
cd aer_rt_utils
git branch v1.0
git checkout v1.0
... (copy over modified files)
git commit -a -m 'code changes for RT utils v1.0'
git push origin v1.0

Merging and pulling should be done in the web interface.

Alternatively, commit and push new code to master branch:

git clone git@github.com:AER-RC/aer_rt_utils.git
... (copy over modified files)
git commit -a -m 'code changes for RT utils v1.0'
git push origin master

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

3. In repositories that are dependent on aer_rt_utils, point the aer_rt_utils submodule HEAD to the newest release.

git clone --recursive git@github.com:AER-RC/LBLRTM.git
cd LBLRTM/cross-sections
git checkout v1.0
git commit -a -m 'updated aer_rt_utils to v1.0'
cd ..
git commit cross-sections 'updated aer_rt_utils submodule'

Repositories that use aer_rt_utils as a submodule:

a. LBLRTM b. LNFL c. MT-CKD

5. Wiki What's New?
6. Local Version?
7. Release directory on NAS?