update gpg key
    as release approaches, wath the fedora-release package for a new key to be
    added.  Use the update-gpg-keys script to add it to static/.  Manually add
    it to /keys and /verify.

Branch master for stable release (perhaps this should be done right after
release?) e.g. git branch f12 master && git push origin f12

Freeze website by editing sysncStatic.sh in modules/fedora-web/files on
puppet1.

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.

On release day, wait for rel-eng to say go, then push puppet change, then on
puppet1 run:

    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 update the website