Difference between revisions of "Releases:Website Checklist"
Jump to navigation
Jump to search
(this was deleted entirely on the 104 page) |
(remove the relnotes stuff that is handled in bguzilla) |
||
Line 1: | Line 1: | ||
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): | 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). | # 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 | # Update htaccess file so that /releases/latest points to the new relnotes | ||
Line 12: | Line 7: | ||
# Create new "news" notification (remember atom file) | # Create new "news" notification (remember atom file) | ||
# Update main page version number(s) | # Update main page version number(s) | ||
+ | #* ??? | ||
# Update agentdetect scripts | # Update agentdetect scripts | ||
# Make sure everything in CVS is correct | # Make sure everything in CVS is correct | ||
− | |||
− | |||
− | |||
− | |||
− | |||
# Get someone (reed) to update m.o VARIABLES | # Get someone (reed) to update m.o VARIABLES | ||
− | #* this needs the bouncer urls, file size, etc., and the | + | #* this needs the bouncer urls, file size, etc., and the cbo release note url |
− | # Make sure that all l10n.cb.o sites have the correct download link, even if their text is not updated | + | <!--# 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 | # Try to get mozillaZine to update their links :P | ||
# Update the tag in [[Development:Building#FAQ]] | # Update the tag in [[Development:Building#FAQ]] |
Revision as of 10:54, 18 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
- Get someone (reed) to update m.o VARIABLES
- this needs the bouncer urls, file size, etc., and the cbo release note url
- 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: