+++ This bug was initially created as a clone of Bug #678756 +++ For making SeaMonkey 2.3.1 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. ----- Release date is undetermined so far for 2.3.1, I expect Monday or Tuesday. This needs new files on seamonkey-project.org since the actual app version will be 2.3.1 not 2.3. I'm ok with redirects for some stuff here, as long as we present the version appropriately. (we can share relnotes, possibly even changes page, etc.) If you would rather copy and forward the 2.3 stuff to the 2.3.1 dir thats fine too.

added archive page RCS file: /www/seamonkeyproject-org/src/releases/2.3.1.en.html,v done Checking in 2.3.1.en.html; /www/seamonkeyproject-org/src/releases/2.3.1.en.html,v <-- 2.3.1.en.html initial revision: 1.1 done

This time the review is for real, to let you check the news item and debate which changes to the relnotes are needed. The changes to the beta version are just preparations; the corresponding areas on the index page are currently commented out. The staging site already has the changes, but as always beware: the news item links go to the live site.

Note that the patch does not yet include a redirect for the 2.3.1 relnotes (.htaccess addition).

(In reply to Jens Hatlak (:InvisibleSmiley) from comment #3) > Note that the patch does not yet include a redirect for the 2.3.1 relnotes > (.htaccess addition). I might not be available when the changes are supposed to go live, and updating the patch is a bit complicated for me right now so here's how: Simply copy and adapt the line about seamonkey2.1pre in src/.htaccess. Note that even with all of the above applied, the relnotes (releases/seamonkey2.3/) will not mention 2.3.1 at all yet. Should I really not be available, just add a note somewhere what the 2.3.1 update/release is about.

I updated the patch as suggested here, I hope this doesn't conflict with your other work. Review back at you to be sure that my changes make sense/don't mess anything up you were planning. I'll be around a bit to make sure that nothing goes awol here. Please resolve when confident. Checking in lib/config.tmpl; /www/seamonkeyproject-org/lib/config.tmpl,v <-- config.tmpl new revision: 1.70; previous revision: 1.69 done Checking in lib/sitemap.xml; /www/seamonkeyproject-org/lib/sitemap.xml,v <-- sitemap.xml new revision: 1.70; previous revision: 1.69 done Checking in src/.htaccess; /www/seamonkeyproject-org/src/.htaccess,v <-- .htaccess new revision: 1.20; previous revision: 1.19 done Checking in src/news.en.xml; /www/seamonkeyproject-org/src/news.en.xml,v <-- news.en.xml new revision: 1.93; previous revision: 1.92 done Checking in src/releases/2.3.1.en.html; /www/seamonkeyproject-org/src/releases/2.3.1.en.html,v <-- 2.3.1.en.html new revision: 1.2; previous revision: 1.1 done Checking in src/releases/2.3.en.html; /www/seamonkeyproject-org/src/releases/2.3.en.html,v <-- 2.3.en.html new revision: 1.3; previous revision: 1.2 done Checking in src/releases/index.en.html; /www/seamonkeyproject-org/src/releases/index.en.html,v <-- index.en.html new revision: 1.184; previous revision: 1.183 done Checking in src/releases/seamonkey2.3/changes.en.html; /www/seamonkeyproject-org/src/releases/seamonkey2.3/changes.en.html,v <-- chan ges.en.html new revision: 1.12; previous revision: 1.11 done Checking in src/releases/seamonkey2.3/relnote.var; /www/seamonkeyproject-org/src/releases/seamonkey2.3/relnote.var,v <-- relnote. var new revision: 1.2; previous revision: 1.1 done

Comment on attachment 555297 [details] [diff] [review] Updates (including .htaccess) Did the changes page fix for the TOC and the anchor. Checking in src/releases/seamonkey2.3/changes.en.html; /www/seamonkeyproject-org/src/releases/seamonkey2.3/changes.en.html,v <-- chan ges.en.html new revision: 1.13; previous revision: 1.12 done

(In reply to Justin Wood (:Callek) from comment #5) > I updated the patch as suggested here, I hope this doesn't conflict with > your other work. Not at all. I was planning to have it like this. CVS is bad at managing multiple states, but it can handle merging in changes during update that had already been made locally before (as in this case). > Review back at you to be sure that my changes make sense/don't mess anything > up you were planning. I wouldn't have changed relnote.var (i.e. the version shown on the release notes), but now that you did I think we can leave it. No idea why the news didn't update; I hope it will now. If not, well... We'll see about that. Leaving open until we have an answer. removed "security update" bit from news item Checking in src/news.en.xml; /www/seamonkeyproject-org/src/news.en.xml,v <-- news.en.xml new revision: 1.94; previous revision: 1.93 done

FYI, the website front page, and news has not yet updated, I poked IT to peek at apache logs incase there is/was any errors in there.

(In reply to Justin Wood (:Callek) from comment #8) > FYI, the website front page, and news has not yet updated, I poked IT to > peek at apache logs incase there is/was any errors in there. Front page and news just updated. Not sure if anything was stuck, IT person I poked wasn't able to (timely) find docs on how to get at our sites logs, so I dismissed them from the duty for now. I chose to update the relnote.ver since I was planning on doing 2.3.x instead of 2.3.1 but it appeared as if that was used for slightly more. And includes some download links using the relnote vars, so rather than point at 2.3.0 downloads, wanted to point at 2.3.1 and didn't want to hack too much in those pages.