Releases:Website Checklist
Jump to navigation
Jump to search
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:
- 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.
- Update the .htaccess file so that /releases/latest points to the new relnotes
- Update /download/releases/index.php file with latest version information
- Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
- Currently copy/pasted from previous release with version numbers updated
- Update agentdetect scripts
- Add new line for release to both config files ('regular' and 'start')
- Add new line for release to message file ('regular' and 'start')
- [message] Update previous releases' lines to warn users to upgrade to latest release; update version numbers specifically ('regular' and 'start')
- [message] Update all 1.0.x release lines to have the latest version in them ('regular' and 'start')
- [message] Update 'default' line to have latest version ('regular' and 'start')
- [message] Add new 'else if' for release further in message file
- Create blog post including adding it to archive and atom feed (manually generated)
- Get release version into Bouncer (pending final release file)
- 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
- Try to get mozillaZine to update their links :P
- Update the tag in Development:Building#FAQ
- Update the dates and links in [[Development:Roadmap]