Skip to content

LNFL New Release Procedure

Rick Pernak edited this page Jul 27, 2020 · 2 revisions

For the purposes of this documentation, the assumed LNFL release version is v3.3 (coming July 2020). The steps for a new release are:

  1. Push new code to a branch and submit merge/pull request:
git clone --recursive [email protected]:AER-RC/LNFL.git
cd LNFL
git branch v3.3
git checkout v3.3
... (copy over modified files)
git commit -a -m 'code changes for LNFL v3.3'
git push origin v3.3

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/LNFL.git
cd LNFL
... (copy over modified files)
git commit -a -m 'code changes for LNFL v3.3'
git push origin master
  1. Draft a new release. Tag and Release Title should be v3.3, and Target should be master. What's New bullets should be added in description.

  2. Update Wiki pages (certainly What's New, possibly others like References and Publications)

  3. update README.md files (Cloning the Latest Release section and anything else that might refer to previous release)

  4. Download Release/Tag into /nas/project/rc_static/models/aer_lnfl or model of interest

mkdir lnfl_v3.3
cd lnfl_v3.3
wget --output-document lnfl_v3.3.tar.gz https://github.com/AER-RC/LNFL/archive/v3.3.tar.gz
tar xvf lnfl_v3.3.tar.gz
mv LNFL-3.3/ lnfl
  1. Local version update

This procedure is identical to the one for LBLRTM.

Clone this wiki locally