Closed Bug 634171 Opened 14 years ago Closed 14 years ago

Send out 2.1b2 announcement

Categories

(SeaMonkey :: Release Engineering, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Callek, Assigned: Callek)

References

Details

+++ This bug was initially created as a clone of Bug #617985 +++ 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. As soon as the website is live with the new release, the announcement for it should be put up on the blog and sent to the newsgroups as well as the announce list. Also update the /topic in #seamonkey with the release.
* SeaMonkey blog is done * Newsgroups done: - Newsgroups: mozilla.dev.apps.seamonkey,mozilla.support.seamonkey,mozilla.dev.planning,netscape.public.mozilla.seamonkey,mozilla.dev.l10n - Followup-To: mozilla.dev.apps.seamonkey * announce@lists.mozilla.org sent
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
If I can support you here in the future, let me know.
The "improvements" and "Known Issues" links on the SeaMonkey blog go to SM 2.1b1.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Ahh thanks for the catch; (I also had the mistake in the news.en.xml from the webpage announcements too)
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
I wonder whether we should send a mail to about-mozilla[at]mozilla.com in the future. Either they're not picking up SM announcements themselves or are not interested in them. I only noticed that they listed Bugzilla 4.0 under Software Updates even though that announcement appeared after ours on Planet, but it's possible that someone sent them a mail for that.
About Mozilla might be a good idea as well, yes. And please ping me (or someone else with moderator access) after sending to the announce list so that it actually gets moderated and appears on the list (done that now for this one).
You need to log in before you can comment on or make changes to this bug.