Fedora Websites Release SOP

From FedoraProject

Revision as of 15:10, 25 August 2009 by Tmz (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Artwork DesignService fedorawebsitesbanner 3.png


Contents

Preparing the website for a release

Update gpg key

As the release approaches, watch the fedora-release package for a new key to be added. Use the update-gpg-keys script in the fedora-web git repository to add it to static/. Manually add it to /keys and /verify.

Branch master for stable release in fedora-web git repository

Note.png
Perhaps this should be done right after release?
git branch f12 master && git push origin f12

Freeze website

Edit the branch to checkout in modules/fedora-web/files/syncStatic.sh on puppet1.

Prepare puppet commits

Prior to release day, prepare puppet commits to move the fedora-web branch to the release (alpha, beta, final, whatever) and, edit redirects.conf (in modules/fedora-web/files on puppet1) to do the right thing with /get-prerelease requests.

Fire in the hole

On release day, wait for rel-eng to say go, then push the puppet changes (e.g.: cd ~/puppet && git push). Then, on puppet1 run:

sudo /usr/local/bin/syncPuppetMaster.sh
sudo /usr/local/bin/syncStatic

# Ensure you have the puppet repo checked out to ~/puppet and up to date
cd ~/puppet && make HOSTS="proxy1 proxy2 proxy3 proxy4 proxy5" push

sudo func proxy\* call command run "/usr/local/bin/syncFiles.sh fedoraproject.org /srv/web/fedoraproject.org/"

to push the updated website live.