Difference between revisions of "Releases:Website Checklist"
Jump to navigation
Jump to search
(→Major release: update) |
|||
Line 8: | Line 8: | ||
* Go through [[Website:Documentation Changes for 1.6|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. | * Go through [[Website:Documentation Changes for 1.6|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 '''TODO for 1.6''' | * Update the main page screenshot and CSS feature call-out '''TODO for 1.6''' | ||
− | * Update /features/ for new features | + | * Update /features/ for new features |
* Copy the folder for the previous major release (e.g., 1.5 for the 1.6 release) in /releases/ | * 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 index.php file with text from [[Releases:1.6:Notes]] | ||
Line 18: | Line 18: | ||
*: Be sure to preserve any '''class''' or '''id''' attributes from the previous version when pasting in the new information. | *: Be sure to preserve any '''class''' or '''id''' attributes from the previous version when pasting in the new information. | ||
− | * /press/ | + | * <s>/press/ |
** new screenshots | ** new screenshots | ||
− | * /downloads/ | + | * /downloads/ |
− | ** EULA link/legal | + | ** EULA link/legal</s> |
* ua-detection '''TODO for 1.6''' | * ua-detection '''TODO for 1.6''' | ||
** what to do about 10.3.x<9? | ** what to do about 10.3.x<9? | ||
− | * Sysreqs boxes | + | * <s>Sysreqs boxes |
** s/10.3/10.3.9/ | ** s/10.3/10.3.9/ | ||
− | ** s/1.5/1.6/ | + | ** s/1.5/1.6/</s> |
* Press Release '''(will we have one for 1.6?)''' | * Press Release '''(will we have one for 1.6?)''' |
Revision as of 04:39, 17 April 2008
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.
unless otherwise noted with a TODO or the like, the tasks here are completed for 1.6
- Line up some blog coverage and start writing a press release about 2 weeks out not done for 1.6
- 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 TODO for 1.6
- 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 TODO for 1.6
- 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/- new screenshots
/downloads/EULA link/legal
- ua-detection TODO for 1.6
- what to do about 10.3.x<9?
Sysreqs boxes- s/10.3/10.3.9/
s/1.5/1.6/
- Press Release (will we have one for 1.6?)
- Staging the release
- For the most part, follow the Major/Minor release
- QA the RC and the ML build TODO for 1.6
- Get the builds in bouncer TODO for 1.6
- SWupdate definition, and descriptions for each language TODO for 1.6
- disable/redirect the preview site to the main page TODO for 1.6
- remove/hide the "visit our preview site" link on /contribute/ TODO for 1.6
- Do the "Downloads Old" step from the #1.5.4 release to the last security release (1.5.5) TODO for 1.6
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
messages.inc
/messages.start.inc
messages (see relevant section in Major minor release below) - preview.cbo
- cbo/contribute
- appcast stuff
- lock down wiki release notes
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:
- 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
- Update the .htaccess file so that /releases/latest points to the new relnotes
- Update /download/releases/index.php file with latest version information
- 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
- Update agentdetect scripts
- Add new line for release to both config files ('regular' and 'start')
- Add new line for release to message file ('regular' and 'start')
- [message] Update previous release's lines to warn users to upgrade to latest release; update version numbers specifically ('regular' and 'start')
- [message] Update all 1.0.x release lines to have the latest version in them ('regular' and 'start') -- this now uses the
{$this->latest}
syntax, so no further tweaking should be necessary - [message] Update 'default' line to have latest version ('regular' and 'start') -- this now uses the
{$this->latest}
syntax, so no further tweaking should be necessary - [message] Add new 'else if' for release further in message file
- Create blog post including adding it to archive and atom feed (manually generated)
- Get release version into Bouncer (pending final release file)
- Get the release into Talkback and reports set up/running
- 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
- 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
1.5.4 Release
Here's what I did in Coda (for Smokey):
- Update any files you might be touching before starting
- Relnotes
- 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)
- Copy/Paste notes from wiki page and format like previous notes
- At bottom of document, change download links to point to 1.5.4
- Change release date
- Add any languages (none this release)
- Copy the intro 'p' from 1.5.2 to 1.5.3 and s/1.5.2/1.5.3
- 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 link (x2) on both pages
- Change release date on both pages
- Add any languages (none this release) on the MultiLang page
- Downloads Old (1.5.3 + MultiLang)
- Change title to "Download" (remove 'ing' and '…')
- Remove the two $download* variables at the top of the 1.5.3 page.
- Copy/paste intro and col2span from a previous release (this removes the graphical instructions)
- s/1.5.2/1.5.3
- Download Releases
- Edit /download/releases/index.php
- In the "Latest Release" section, s/1.5.3/1.5.4
- Copy/Paste the preview release line and s/1.5.2/1.5.3
- htaccess
- Change this line: RewriteRule ^releases/latest/?$ /releases/1.5.3/ [R=302]
- Header
- In header_inc, s/1.5.3/1.5.4
- Start Pages
- In config.inc and config.start.inc:
- Change latest to 1.5.4
- Add new line for 1.5.4 (copy paste from 1.5.3 and rename)
- For alphabeta releases, increment the latestPre (though it might be unused)
- In messages.inc
- Copy/Paste the Release153 line then s/153/154 and s/1.5.3/1.5.4
- Copy Release152 and paste in place of the Release153 line then s/153/154 and s/1.5.2/1.5.3 in that line
Copy the line "... recommend you upgrade to ..." (starting with "recommend" but not before it, 'til the end)Do a search and replace for that line. Search for all 1.5.3 and replace with 1.5.4.In the 'Default' line, s/1.5.3/1.5.4- Near the bottom of the page, copy/paste the 'else if' for Release152, then s/152/153 on that line
- On the two lines above that, s/153/154
- In messages.start.inc
- Copy/Paste the Release152 line then s/152/153 and s/1.5.2/1.5.3 in that line
- On the line above, s/153/154
Copy the line "... recommend you upgrade to ..." (starting with "recommend" but not before it, 'til the end)Do a search and replace for that line. Search for all 1.5.3 and replace with 1.5.4.- Go back to Camino106 line and manually change it if it didn't get changed. ???
In the 'Default' line, s/1.5.3/1.5.4- Near the bottom of the page, copy/paste the 'else if' for Release152, then s/152/153 on that line
- On the two lines above that, s/153/154
- In config.inc and config.start.inc:
- 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
- Fix date and time.
- 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
- 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 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 it in all four places.)
- Update
- Nothing for now.
- Final items (not in Coda)
- Go to step 8 "Get the release into Talkback and reports set up/running" in the list above and complete release tasks from there