+++ This bug was initially created as a clone of Bug #617983 +++ For better documentation of release day work, I'm filing this step as well this time, might also be a good idea in the future. It also might be a good idea if a website person would support the release driver on release day to get this done. For making the SeaMonkey 2.1b2 public, we'll need to update the website. This can happen once mirror saturation is good enough, though it's usually a good idea to also have final_verification run and OK before going public on the website.

Following steps done: * > cp -a src/releases/index.en.html src/releases/2.1b2.en.html * Edit src/releases/2.1b2en.html: - Copy everything from start to <div class="key-point"> from 2.1b1en.html, replacing the value of the smversion var on top and the <p class="release-date"> with the correct 2.1b2 values. - Remove commented out parts of <h2 id="contrib"> section - Remove the <h2><a name="[% betaversion %]">, <hr> and <div class="para" id="old"> at the bottom - Update locale build and langpack lists as appropriate for this release, being sure the "odd"/"even" css classes cycle appropriately. * Verify that diff to 2.1b1en.html is only what needs to be. * > cvs add src/releases/2.1b2.en.html * > cvs ci -m "add archive page for 2.1b2" src/releases/2.1b2.en.html [As well as 2.1b1, and 2.1a3 getting the "outdated beta" text] * > cvs ci -m "Note that 2.1b1 and 2.1a3 builds are outdated" src/releases/2.1b1.en.html src/releases/2.1a3.en.html The above could be dome any time during release preps, doesn't have to be release day. The steps below can be *prepared* before release day but the checkin should only be done once mirror saturation is good and final_verification is OK. * Edit src/releases/index.en.html: - Update <p class="release-date"> to 2.1b2 release day [in the betaversion section]. * Edit src/news.en.xml: --- Created a new entry for the announcement - Change showfront attribute of the last beta release to false so that only the newest beta release appear on the front page. * Edit src/download.jst the relevant locales (i.e. those that weren't in b1) changed for the beta version to use the beta version and not the release version * Edit lib/config.tmpl: - Update betaversion to 2.1b2. - Update betaname to "SeaMonkey 2.1 Beta 2" - Update develversion to 2.1b3pre * Edit lib/sitemap.xml: - Copy and change the <page url="releases/index"> block so that 2.1b2 has its own one. * Edit src/releases/seamonkey2.1b1/index.en.html: - Add note about being an outdated beta version. [Should have been in a3 page; but actually pulled from a2] - Did the same for src/releases/seamonkey2.1a3/index.en.html per above. As I said, wait for being ready to really go public with the release before checking those changes in, they are the actual push that makes it known to the world and counts as "we released".

Did all of the above, with one mini error [its 2011 not 2010] and checked in, in stages. I created diffs and put on pastebin for "all in one" diffs for reference. Linking below (in order) $ cvs ci -m "add archive page for 2.1b2" src/releases/2.1b2.en.html RCS file: /www/seamonkeyproject-org/src/releases/2.1b2.en.html,v done Checking in src/releases/2.1b2.en.html; /www/seamonkeyproject-org/src/releases/2.1b2.en.html,v <-- 2.1b2.en.html initial revision: 1.1 done $ cvs ci -m "Note that 2.1b1 and 2.1a3 builds are outdated" src/releases/2.1b1.en.html src/rel eases/2.1a3.en.html Checking in src/releases/2.1b1.en.html; /www/seamonkeyproject-org/src/releases/2.1b1.en.html,v <-- 2.1b1.en.html new revision: 1.5; previous revision: 1.4 done Checking in src/releases/2.1a3.en.html; /www/seamonkeyproject-org/src/releases/2.1a3.en.html,v <-- 2.1a3.en.html new revision: 1.3; previous revision: 1.2 done $ cvs ci -m "This is 2011, not 2010" src/releases/2.1b2.en.html Checking in src/releases/2.1b2.en.html; /www/seamonkeyproject-org/src/releases/2.1b2.en.html,v <-- 2.1b2.en.html new revision: 1.2; previous revision: 1.1 done $ cvs ci -m "Release SeaMonkey 2.1 beta 2" Checking in lib/config.tmpl; /www/seamonkeyproject-org/lib/config.tmpl,v <-- config.tmpl new revision: 1.50; previous revision: 1.49 done Checking in lib/sitemap.xml; /www/seamonkeyproject-org/lib/sitemap.xml,v <-- sitemap.xml new revision: 1.54; previous revision: 1.53 done Checking in src/download.jst; /www/seamonkeyproject-org/src/download.jst,v <-- download.jst new revision: 1.7; previous revision: 1.6 done Checking in src/news.en.xml; /www/seamonkeyproject-org/src/news.en.xml,v <-- news.en.xml new revision: 1.69; previous revision: 1.68 done Checking in src/releases/index.en.html; /www/seamonkeyproject-org/src/releases/index.en.html,v <-- index.en.html new revision: 1.164; previous revision: 1.163 done Checking in src/releases/seamonkey2.1a3/index.en.html; /www/seamonkeyproject-org/src/releases/seamonkey2.1a3/index.en.html,v <-- index.en.html new revision: 1.6; previous revision: 1.5 done Checking in src/releases/seamonkey2.1b1/index.en.html; /www/seamonkeyproject-org/src/releases/seamonkey2.1b1/index.en.html,v <-- index.en.html new revision: 1.10; previous revision: 1.9 done http://callek.pastebin.mozilla.org/1062566 http://callek.pastebin.mozilla.org/1062569 http://callek.pastebin.mozilla.org/1062571 http://callek.pastebin.mozilla.org/1062572

(In reply to comment #0) > It also might be a good idea if a website person would support the release > driver on release day to get this done. Sure. I was in IRC yesterday (well, "my" yesterday) in case you wanted to contact me. In the future, feel free to contact me directly to agree on some time window.