Releases:Website Checklist
Revision as of 09:42, 24 December 2008 by Sardisson (talk | contribs) (→Milestone release: missed this one)
Contents
Major release
There's no clear path to doing a major release yet, however I want to keep track of a few things here for future reference.
- Line up some blog coverage and start writing a press release about 2 weeks out.
- Contact host (Network Redux) two to three days before release so they know load will be high.
- Go through documentation changes and make them as needed. Be sure to read over all pages in /documentation/, since there will be changes to things you've forgotten are in certain sections. Make sure to update the TOC links.
- Update the main page screenshot and CSS feature call-out
- Update /features/ for new features
- Copy the folder for the previous major release (e.g., 1.5 for the 1.6 release) in /releases/
- Update the index.php file with text from Releases:1.6:Notes
- Update the complete.php file with text from Releases:1.6:Complete
- Find/replace 1.5 with 1.6, and 1.0 with 1.5
- Update the release date in the box
- Update the ML languages
- Note that getting these pages from the wiki into Coda (and into decent HTML) requires some manipulation
- Be sure to preserve any class or id attributes from the previous version when pasting in the new information.
- /press/
- Add new screenshots
- Add the new press release
- /downloads/
- Do the Download, Downloads Old, and Download Releases steps from the #1.5.4 release information
- Make downloads/releases/nightly/ point to the "latest-" folder for the active development branch
- /contribute/
- Hide the "Preview" box
- ua-detection
- Steps TBD
- what to do about 10.3.x<9?
- add oldRelease/one16Release equivalent for EOL branch that drops OS support
- For new major releases, comment out the active messageOldPreRelease and un-comment the other
- System requirements boxes
- On home and /features/, update the system requirements and version number
- Staging the release
- For the most part, follow the Major/Minor release
- QA the RC and the ML build
- Get the builds in bouncer
- Stage the software update definition and update descriptions for each language
- disable/redirect the preview site to the main page
Milestone release
There's no clear path to doing a milestone (alpha/beta) release yet, however I want to keep track of a few things here for future reference.
- Add/re-enable the right
messageOldPreRelease
in ua-messages{-start).js (see relevant section in Major minor release below) - Blog (see relevant section in Major minor release below)
- preview.cbo
- Be sure to fix the "latest stable version" link/text
- cbo/contribute (unhide the Preview box and/or update the version number)
- Software update (see relevant section in Major minor release below)
- Lock down wiki release notes
Major minor release
When releasing a Camino 1.5.x/1.6.x release, the following things need to be done to prepare the website and to update it:
In Coda
- Update any files you might be touching before starting
- Relnotes (
/releases/
)- Duplicate
releases/1.5.3/
- Rename it to
releases/1.5.4/
- Change page title at the top
- Change intro to say 1.5.4. (and 1.5.3 instead of 1.5.2)
- For M.m->M.m.x, replace intro ("After over a year of hard work") with "Camino 1.6.1 is a stability...") and add "notes_changes" and "notes_about" sections (see any previous M.m.x page)
- For M.m.1->M.m.2, change "update for Camino 1.6" to "update for Camino 1.6.x"
- Copy/Paste notes from wiki page and format like previous notes
- Update any Known Issues changes
- At bottom of document, change download links (en and ML) to point to 1.5.4
- Change release date
- Add any languages (none this release)
- Copy the intro 'p' ("no longer latest release") from 1.5.2 to 1.5.3 and s/1.5.2/1.5.3
- For M.m->M.m.x, prepend this into 'p' before the "After over a year of hard work" 'p'
- For EOL-OS releases, copy the format from 0.8.5/1.0.6 and point to
/releases/latest/
until that branch becomes EOL as well (then point to the final release on the newly-EOLed branch).
- Duplicate
- Download
- Duplicate
/download/releases/1.5.3/
- Rename it to
/download/releases/1.5.4/
- Duplicate
/download/releases/1.5.3-MultiLang/
- Rename it to
/download/releases/1.5.4-MultiLang/
- Change page title and URL at top of both pages to be 1.5.4
- Change intro text to be 1.5.4 on both pages (including download URLs)
- Change relnotes links (en, ML) near the bottom on both pages
- Change release date on both pages
- Add any languages (none this release) on the MultiLang page
- Duplicate
- Downloads Old (1.5.3 + MultiLang)
- Change title to "Download" (remove 'ing' and '…')
- Remove the two $download* variables at the top of the old (1.5.3) page.
- Copy/paste "intro" and "col2span" from a previous release and ML release (this removes the graphical instructions)
- s/1.5.2/1.5.3 (3x per page)
- Download Releases
- Edit
/download/releases/index.php
- In the "Latest Release" section, s/1.5.3/1.5.4
- Copy/Paste the previous release line and s/1.5.2/1.5.3
- Edit
- htaccess
- Change this line: RewriteRule ^releases/latest/?$ /releases/1.5.3/ [R=302]
- Header
- In header_inc, s/1.5.3/1.5.4 (3x; text+2 links)
- Start Pages (ua-messages.js and ua-messages-start.js)
- Change latestRelease to 1.6.1
- Add the last release to the front of oldRelease array
- For new major releases, comment out the active messageOldPreRelease and un-comment the other
- For alphabeta releases:
- increment the latestPreRelease, oldPreRelease array (if needed), and the text version in messageLatestPreRelease
- Choose the correct messageOldPreRelease; uncomment the one linking to preview.cbo and comment out the other one
- Fix the plain-text release name in messageLatestPreRelease ("Thank you for testing Camino 2.0 Alpha 1.")
- Blog
- Remove the oldest blog post on the main blog page
- Copy the 1.5.3 blog post and paste at the top of the page
- Fix any wording and version numbers throughout the post (h2 id, h2 text, p text, p links, and bottom p text and links)
- Update any languages added in this release
- Fix date and time (and PST/PDT)
- Copy and paste it into
/blog/2007/
or/blog/2008/
, creating it if necessary - In atom.xml:
- Remove the oldest entry in the file
- Copy/Paste the most recent blog post to the top of the feed
- Fix the date
- Issued is in local time (-700/-800)
- Created and Modified are in Z time [1]
- Fix the 'link' to go to the correct post and have the correct title
- Up the 'id' incrementally by 1
- Fix the 'title'
- Remove everything in the 'content->div' tag
- Paste the blog post HTML into the 'content->div' tag
- Fix links in the post to be absolute, not relative
- Fix the date/time in the "Posted on" paragraph between the “headers” and the first entry (PST/PDT change, too).
- Fix the Modified of the entire feed near the top of the file (in Z time too!)
- (Note: If you need to change the post after this point, be sure to change the post in all three files and the <modified> in the feed itself, the entry, and "Posted on" text [used to read "it in all four places"].)
- Update
- Duplicate the M.m.x update description files
- N.B. Major releases and milestone releases have different description formats (intro pgh of their relnotes, plus link to preview.cb.o)
- In each description file:
- Change the current version number at the beginning of the sentence to the current version
- If M.m.1, change "stability update for Camino 1.6" to "1.6.x"
- Change the version number in the relnotes link
- Duplicate the M.m.x update definition files for en-only and ML
- In each definition file:
- Duplicate the M.m.x update description files
Final items (not in Coda)
- Get release version into Bouncer (pending final release file; usually you can—and need to—do this at least the day before, and typically ardissone or mento files the bug [release, milestone] when staging the files)
- Get the release into Talkback and reports set up/running (contact Sam)
- 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
- File a bug to hide the release's flag and add a new flag for the next release.
- Try to get mozillaZine to update their links :P
- Email mozilla-news-submissions@mozilla.org about release so we end up in newsletter.
- Fix the /topic in #camino
- New post at the Forum
- Unsticky the RC thread
- Find the thread for the previous release, copy it with s/oldversionnumber/newversionnumber/, and post as a new sticky thread
- Update the tag in Development:Building#FAQ
- Update the dates and links in Development:Roadmap