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.

Update LINGUAS and languages.conf file

Let's clean our directories and update the po files

$ make clean all

Checks file listing vs what's in LINGUAS (left side is the correct one)

The ones that only have a " <" on the right side are the ones that are needed

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

On bapp1, run:

# Once /usr/local/bin/syncStatic on bapp1 is updated with your changes, run
sudo -u apache /usr/local/bin/syncStatic

This takes about 15 minutes, so try to do this well before you need to push the
final site out.

Finally, when releng gives the OK, run the following on the proxies to make the
site live:

# To sync the changes out, you can use func from puppet1 if you have sudo on puppet1.
# Otherwise, SSH to the proxies and call the below command.
sudo /usr/bin/rsync -a --no-owner --no-group bapp01::fedoraproject.org/* /srv/web/fedoraproject.org/

Push commit to redirect get-prerelease to get-fedora. If you have sudo on puppet1, run: