Difference between revisions of "Releases:Website Checklist"
Jump to navigation
Jump to search
(add that) |
(roadmap, too) |
||
Line 16: | Line 16: | ||
# Try to get mozillaZine to update their links :P | # Try to get mozillaZine to update their links :P | ||
# Update the tag in [[Development:Building#FAQ]] | # Update the tag in [[Development:Building#FAQ]] | ||
+ | # Update the dates and links in [[Development:Roadmap]] | ||
== Camino 1.0.1 == | == Camino 1.0.1 == | ||
This is the process as we did it for Camino 1.0.1: | This is the process as we did it for Camino 1.0.1: |
Revision as of 10:12, 28 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
- Update the dates and links in Development:Roadmap
Camino 1.0.1
This is the process as we did it for Camino 1.0.1: