Releases:Website Checklist

Major minor release

When releasing a Camino 1.5.x release, the following things need to be done to prepare the website and to update it:

1. Create release notes on website (including anchors for each of the sections, i.e., for easy linking to Known Issues).
   • Currently this is just a copy and paste from the previous release (like 1.5.1) with the added relnotes for that release.
   • Update the release date and add any languages that were added to the ML build in this release
2. Update the .htaccess file so that /releases/latest points to the new relnotes
3. Update /download/releases/index.php file with latest version information
4. Create download links (/download/releases/VERSION# and /download/releases/VERSION#-MultiLang)
   • Currently copy/pasted from previous release with version numbers and release dates updated
   • Add any languages that were added to the ML build in this release
5. Update agentdetect scripts
   1. Add new line for release to both config files ('regular' and 'start')
   2. Add new line for release to message file ('regular' and 'start')
   3. [message] Update previous releases' lines to warn users to upgrade to latest release; update version numbers specifically ('regular' and 'start')
   4. [message] Update all 1.0.x release lines to have the latest version in them ('regular' and 'start')
   5. [message] Update 'default' line to have latest version ('regular' and 'start')
   6. [message] Add new 'else if' for release further in message file
6. Create blog post including adding it to archive and atom feed (manually generated)
7. Get release version into Bouncer (pending final release file)
8. Get the release into Talkback and reports set up/running
9. 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
10. Try to get mozillaZine to update their links :P
11. Email "about:mozilla" so that we show up in the weekly mozilla.org newsletter
12. New post at the Forum
    1. Unsticky the RC thread
    2. Find the thread for the previous release, copy it with s/oldversionnumber/newversionnumber/, and post as a new sticky thread
13. Update the tag in Development:Building#FAQ
14. Update the dates and links in Development:Roadmap

1.5.4 Release

Here's what I did in Coda (for Smokey):

1. Relnotes
   1. Duplicate releases/1.5.3/
   2. Rename it to releases/1.5.4/
   3. Change page title at the top
   4. Change intro to say 1.5.4. (And 1.5.3 instead of 1.5.2)
   5. Copy/Paste notes from wiki page and format like previous notes
   6. At bottom of document, change download links to point to 1.5.4
   7. Change release date
   8. Add any languages (none this release)
   9. Copy the intro 'p' from 1.5.2 to 1.5.3 and s/1.5.2/1.5.3
2. Download
   1. Duplicate /download/releases/1.5.3/
   2. Rename it to /download/releases/1.5.4/
   3. Duplicate /download/releases/1.5.3-MultiLang/
   4. Rename it to /download/releases/1.5.4-MultiLang/
   5. Change page title and URL at top of both pages to be 1.5.4
   6. Change intro text to be 1.5.4 on both pages (including download URLs)
   7. Change relnotes link (x2) on both pages
   8. Change release date on both pages
   9. Add any languages (none this release) on the MultiLang page
3. Downloads Old (1.5.3 + MultiLang)
   1. Change title to "Download" (remove 'ing')
   2. Remove the two $download* variables at the top of the 1.5.3 page.
   3. Copy/paste intro and col2span from a previous release (this removes the graphical instructions)
   4. s/1.5.2/1.5.3
4. Download Releases
   1. Edit /download/releases/index.php
   2. In the "Latest Release" section, s/1.5.3/1.5.4
   3. Copy/Paste the preview release line and s/1.5.2/1.5.3
5. htaccess
   1. Change this line: RewriteRule ^releases/latest/?$ /releases/1.5.3/ [R=302]
6. Header
   1. In header_inc, s/1.5.3/1.5.4
7. Start Pages
   1. In config.inc and config.start.inc:
      1. Change latest to 1.5.4
      2. Add new line for 1.5.4 (copy paste from 1.5.3 and rename)
   2. In messages.inc
      1. Copy/Paste the Release153 line then s/153/154 and s/1.5.3/1.5.4
      2. Copy Release152 and paste in place of the Release153 line then s/1.5.2/1.5.3 in that line
      3. Copy the line "... recommend you upgrade to ..." (starting with "recommend" but not before it, 'til the end)
      4. Do a search and replace for that line. Search for all 1.5.3 and replace with 1.5.4.
      5. In the 'Default' line, s/1.5.3/1.5.4
      6. Near the bottom of the page, copy/paste the 'else if' for Release152, then s/152/153 on that line
      7. On the two lines above that, s/153/154
   3. In messages.start.inc
      1. Copy/Paste the Release152 line then s/152/153 and s/1.5.2/1.5.3 in that line
      2. On the line above, s/153/154
      3. Copy the line "... recommend you upgrade to ..." (starting with "recommend" but not before it, 'til the end)
      4. Do a search and replace for that line. Search for all 1.5.3 and replace with 1.5.4.
      5. Go back to Camino106 line and manually change it if it didn't get changed.
      6. In the 'Default' line, s/1.5.3/1.5.4
      7. Near the bottom of the page, copy/paste the 'else if' for Release152, then s/152/153 on that line
      8. On the two lines above that, s/153/154
8. Blog
   1. Remove the oldest blog post on the main blog page
   2. Copy the 1.5.3 blog post and paste at the top of the page
   3. Fix any wording and version numbers throughout the post
   4. Fix date and time.
   5. Copy and paste it into /blog/2007/
   6. In atom.xml:
      1. Remove the oldest entry in the file
      2. Copy/Paste the most recent blog post to the top of the feed
      3. Fix the date (in Z time too!)
      4. Fix the 'link' to go to the correct post and have the correct title
      5. Up the 'id' incrementally by 1
      6. Fix the 'title'
      7. Remove everything in the 'content->div' tag
      8. Paste the blog post HTML into the 'content->div' tag
      9. Fix links in the post to be absolute, not relative
   7. (Note: If you need to change the post after this point, be sure to change it in all three places.)
9. Update
   1. Nothing for now.
10. Final items (not in Coda)
    1. Go to step 8 "Get the release into Talkback and reports set up/running" in the list above and complete release tasks from there