Difference between revisions of "Releases:Website Checklist"

Revision as of 22:42, 19 August 2007

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

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

@@ Line 10: / Line 10: @@
 # Update agentdetect scripts
 # Make sure everything in CVS is correct
-# Get someone (reed) to update m.o VARIABLES
+# 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
 <!--# 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