Releases:Website Checklist

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):

1. Create release notes on wiki
2. Create release notes RTF
3. Review ReadMe.rtf and change as needed (file is fairly static; mostly version # changes)
4. File bug with final release notes and ReadMe.rtf (if applicable) in it (get review and checkin)
5. Email Ludo with final release notes and ReadMe.rtf
6. Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues).
7. Update htaccess file so that /releases/latest points to the new relnotes
8. Get release version into Bouncer (pending final release file)
9. Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
10. Create new "news" notification (remember atom file)
11. Update main page version number(s)
12. Update agentdetect scripts
13. Make sure everything in CVS is correct
14. Email yama with a list of changes so jp.cb.o can be updated in time
15. Update www.m.o htaccess files to point to cb.o relnotes
    • one is located at www.m.o/products/camino/.htaccess
16. 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
17. 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
18. Make sure that all l10n.cb.o sites have the correct download link, even if their text is not updated
19. Try to get mozillaZine to update their links :P
20. Update the tag in Development:Building#FAQ

Camino 1.0.1

This is the process as we did it for Camino 1.0.1: