Difference between revisions of "Releases:Website Checklist"

From Camino Wiki
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 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).
 
# 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
−
# 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
 
# 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
+
#* 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):

  1. Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues).
  2. Update htaccess file so that /releases/latest points to the new relnotes
  3. Get release version into Bouncer (pending final release file)
  4. Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
  5. Create new "news" notification (remember atom file)
  6. Update main page version number(s)
    •  ???
  7. Update agentdetect scripts
  8. Make sure everything in CVS is correct
  9. Get someone (reed) to update m.o VARIABLES
    • this needs the bouncer urls, file size, etc., and the cbo release note url
  10. Try to get mozillaZine to update their links :P
  11. Update the tag in Development:Building#FAQ

Camino 1.0.1

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

Retrieved from "http://wiki.caminobrowser.org/index.php?title=Releases:Website_Checklist&oldid=8235"