Releases:Website Checklist - Revision history

Sardisson: /* In Coda */ add langs step

2012-02-19T05:25:39Z

In Coda: add langs step

Sardisson: /* In Coda */ put full text there, since it gets deleted over time as new releases come out

2012-02-19T04:53:27Z

In Coda: put full text there, since it gets deleted over time as new releases come out

Sardisson: /* Major release */ add preview, which somehow was inexplicably missing!

2011-11-29T02:52:28Z

Major release: add preview, which somehow was inexplicably missing!

Sardisson: /* In Coda */ add a note here for updating ua-messages when 2.1.1 is released

2011-11-29T02:46:38Z

In Coda: add a note here for updating ua-messages when 2.1.1 is released

Sardisson: /* Major release */ clarify confusing statement

2011-11-19T05:10:21Z

Major release: clarify confusing statement

Sardisson: /* Major release */ update the JS section: one part for versions.js and one part for messages; also separate sub-lists for "if dropping OS" items

2011-11-19T04:08:11Z

Major release: update the JS section: one part for versions.js and one part for messages; also separate sub-lists for "if dropping OS" items

Sardisson: /* Major release */ one more thing here

2011-11-19T03:52:07Z

Major release: one more thing here

Sardisson: /* Major release */ bleh, fix the busted links I just copied from :P

2011-11-19T00:57:21Z

Major release: bleh, fix the busted links I just copied from :P

Sardisson: fix one more stray anchor link

2011-11-19T00:54:49Z

fix one more stray anchor link

Sardisson: /* Major release */ legal

2011-11-17T20:26:16Z

Major release: legal

@@ Line 140: / Line 140: @@
 ## Edit <code>/download/index.php</code>
 ## Edit the version numbers in the download button URLs
 ## 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

@@ Line 108: / Line 108: @@
 ## 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->M.m.x, replace intro ("After over a year of hard work") with "Camino 2.0.1 is a stability and security update for Camino 2.0. All users are urged to upgrade.") 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

@@ Line 41: / Line 41: @@
 * /contribute/
 ** Hide the "Preview" box
 * /js/ - ua-detection

@@ Line 146: / Line 146: @@
 ## Change latestRelease to 1.6.1 in versions.js
 ## Add the last release to the front of oldRelease array in versions.js
 ## ''For new major releases, comment out the active messageOldPreRelease and un-comment the other''
 ## For alphabeta releases:

@@ Line 57: / Line 57: @@
 **** Add one6Release and one6xReleases messages, and update the versions/OS versions
 **** Add 'if statements' for new one6Release and one6xReleases near the bottom
-**** Before 1.6.10 is declared EOL, remove the "not supported" sentence from 'messageOne6Release'
+**** In the period before 1.6.10 is declared EOL, remove the "not supported" sentence from 'messageOne6Release'
 **** When 10.4 support is being dropped, rewrite the JS to parse OS version, and send different messages to 10.4 2.x users and 10.5± 2.x users
 ** Watch out for typos!

@@ Line 43: / Line 43: @@
 * /js/ - ua-detection
-** Set the latestRelease to 2.0
+** <code>versions.js</code>
-** Set the latestPreRelease and associated variables to 2.1a1
+*** Set the latestRelease to 2.0
-** Add the last beta to oldPreRelease
+*** Set the latestPreRelease and associated variables to 2.1a1
-** If you had multiple release candidates, update the <code>ua-messages-*</code> if logic to handle those versions appropriately (see {{bug|699335}} comment 11 for an overview)
+*** Add the last beta to oldPreRelease
-** Update the minimum OS in defaultMessage
+*** Update the minimum OS in latestReleaseOS if necessary
-** Add one6Release and one6xReleases variables and messages, and update the versions/OS versions, when new release series drops OS support
+*** ''If the new release drops OS support''
-*** Before 1.6.10 is declared EOL, remove the "not supported" sentence from 'messageOne6Release'
+**** Remove prior releases from 'oldRelease' (this may clear the entire 'oldRelease' array)
-*** When 10.4 support is being dropped, rewrite the JS to parse OS version, and send different messages to 10.4 2.x users and 10.5± 2.x users
+**** Add new one6Release and one6xReleases variables, filled with the appropriate versions
-** Remove 1.6 releases from 'oldRelease' (this may clear the entire 'oldRelease' array)
+** <code>ua-messages-*</code>
-** Add 'if statements' for new one6Release and one6xReleases near the bottom
+*** If you had multiple release candidates, update the 'if' logic to handle those versions appropriately (see {{bug|699335}} comment 11 for an overview)
-** Comment out the active messageOldPreRelease and un-comment the other
+*** Comment out the active messageOldPreRelease and un-comment the other
 ** Watch out for typos!

@@ Line 36: / Line 36: @@
 * /downloads/
-** Do the Download, Downloads Old, and Download Releases steps from the [[#Major/Minor release]] information
+** Do the Download, Downloads Old, and Download Releases steps from the [[#Major minor release]] information
 ** Make downloads/releases/nightly/ point to the "latest-" folder for the active development branch
@@ Line 59: / Line 59: @@
 * Other
-** Double-check that you've done everything required from [[#Major/Minor release|Major/Minor release]] (htaccess, header, blog, update)
+** Double-check that you've done everything required from [[#Major minor release|Major minor release]] (htaccess, header, blog, update)
 * Staging the release
-*: For the most part, follow the [[#Major/Minor release|Major/Minor release]]
+*: For the most part, follow the [[#Major minor release|Major minor release]]
 ** QA the RC and the ML build
 ** Get the builds in bouncer

@@ Line 30: / Line 30: @@
 ** Add new screenshots
 ** Add the new press release
 * /downloads/