Release Steps #

This is a basic rundown of the steps used for a release.

Note that this information applies to the old us1 deployment and should probably only be used as a guide for the rough shape of a future production deployment.

Using the release # of 3.0552

Make sure master matches last release. (should already be set)
cd Lacuna-Server-Open
git checkout develop
git pull --ff-only pb-ls-open develop
git checkout -b rel-3.0552 (release number in Lacuna.pm)
git push pb-ls-open rel-3.0552
cd ../Lacuna-Server
Same routine with master
git checkout develop
git pull --ff-only pb-ls develop
git pull --ff-only pb-ls-open develop (This shouldn't pull over anything new)
git push pb-ls develop
git checkout pt
git pull --ff-only pb-ls-open pt
git merge develop (Again, shouldn't be anything new, if not we shouldn't do a release on non-tested items)
git push pb-ls pt
git checkout develop
git checkout -b rel-3.0552
git push pb-ls rel-3.0552
git checkout us1
git pull --ff-only pb-ls us1
git push pb-ls us1 (should say up to date)
git merge rel-3.0552
ssh to us1.lacunaexpanse.com, us1-db1, us1-util1, us1-web1, us1-web2
scp var/upgrades/3.0552.sql to us1-db1 and run it.
On other four, go to /data/Lacuna-Server as root. (sudo su - should put you in /home/lacuna/server/bin)
Run close to simultaneous git pull origin us1 There should be no merge conflicts.
On us1-web1 and us1-web2 cd into bin and run ./restart_starman.sh (must be done at same time)
On the News Forum you should post a release summary and make an announcement using the admin screen.