-
Notifications
You must be signed in to change notification settings - Fork 0
RADSUM New Release Procedure
Rick Pernak edited this page Jan 15, 2021
·
1 revision
For the purposes of this documentation, the assumed RADSUM release version is v2.7.1. The steps for a new release are:
- Push new code to a branch and submit merge/pull request:
git clone --recursive [email protected]:AER-RC/RADSUM.git
cd RADSUM
git branch v2.7.1
git checkout v2.7.1
... (copy over modified files)
git commit -a -m 'code changes for RADSUM v2.7.1'
git push origin v2.7.1
Merging and pulling should be done in the web interface.
Alternatively, commit and push new code to master branch:
git clone --recursive [email protected]:AER-RC/RADSUM.git
cd RADSUM
... (copy over modified files)
git commit -a -m 'code changes for RADSUM v2.7.1'
git push origin master
-
Draft a new release. Tag and Release Title should be
v2.7.1
, and Target should bemaster
. What's New bullets should be added in description. -
Update Wiki pages (certainly What's New, possibly others like References and Publications)
-
update
README.md
files (Cloning the Latest Release section and anything else that might refer to previous release) -
Download Release/Tag into
/nas/project/rc_static/models/aer_RADSUM
or model of interest
mkdir RADSUM_v2.7.1
cd RADSUM_v2.7.1
wget --output-document RADSUM_v2.7.1.tar.gz https://github.com/AER-RC/RADSUM/archive/v2.7.1.tar.gz
tar xvf RADSUM_v2.7.1.tar.gz
mv RADSUM-2.7.1/ RADSUM
- Local version update
This procedure is identical to the one for LBLRTM.