Releases:Website Checklist

Major minor release

When releasing a Camino 1.5.x release, the following things need to be done to prepare the website and to update it:

1. Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues).
   • Currently this is just a copy and paste from the previous release (like 1.5.1) with the added relnotes for that release.
2. Update the .htaccess file so that /releases/latest points to the new relnotes
3. Update /download/releases/index.php file with latest version information
4. Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
   • Currently copy/pasted from previous release with version numbers updated
5. Update agentdetect scripts
   1. Add new line for release to both config files ('regular' and 'start')
   2. Add new line for release to message file ('regular' and 'start')
   3. [message] Update previous releases' lines to warn users to upgrade to latest release; update version numbers specifically ('regular' and 'start')
   4. [message] Update all 1.0.x release lines to have the latest version in them ('regular' and 'start')
   5. [message] Update 'default' line to have latest version ('regular' and 'start')
   6. [message] Add new 'else if' for release further in message file
6. Create blog post including adding it to archive and atom feed (manually generated)
7. Get release version into Bouncer (pending final release file)
8. Update m.o VARIABLES
   • this needs the bouncer urls, file size, etc., and the cbo release note url
   • Sam has blanket-a=reed to update VARIABLES for Camino; if Sam is missing, get reed to do it for us
9. Try to get mozillaZine to update their links :P
10. Update the tag in Development:Building#FAQ
11. Update the dates and links in [[Development:Roadmap]