Releases:Website Checklist
Jump to navigation
Jump to search
When preparing for a release, the following things need to be done (this list will probably need to be arranged in an "order" as appropriate):
- Create release notes on wiki
- Create release notes RTF
- Review ReadMe.rtf and change as needed (file is fairly static; mostly version # changes)
- File bug with final release notes and ReadMe.rtf (if applicable) in it (get review and checkin)
- Email Ludo with final release notes and ReadMe.rtf
- Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues).
- Update htaccess file so that /releases/latest points to the new relnotes
- Get release version into Bouncer (pending final release file)
- Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
- Create new "news" notification (remember atom file)
- Update main page version number(s)
- Update agentdetect scripts
- Make sure everything in CVS is correct
- Email yama with a list of changes so jp.cb.o can be updated in time
- Update www.m.o htaccess files to point to cb.o relnotes
- one is located at www.m.o/products/camino/.htaccess
- Update www.m.o/project/camino/homepage.html to list new release
- Make sure to update the "Release Notes" link on www.m.o/project/camino/homepage.html points to the right relnotes on cb.o
- Get someone (reed) to update m.o VARIABLES
- this needs the bouncer urls, file size, etc., and the www.m.o release note url that redirects to cb.o
- Make sure that all l10n.cb.o sites have the correct download link, even if their text is not updated
- Try to get mozillaZine to update their links :P
- Update the tag in Development:Building#FAQ
Camino 1.0.1
This is the process as we did it for Camino 1.0.1: