Announcements
Contents
First milestone/candidate for a release
We write drafts of announcements in the “ICU announcements” Google document.
When there is no section yet for the upcoming release, then copy the whole section from one of the previous two full releases and adjust the version numbers everywhere in the copied headings and text.
Announcement for a release candidate
Adjust the release candidate announcement subsection with a very brief summary gleaned from the download page.
Share the draft as a link to the doc heading with the ICU team, invite comments and edits.
When ready, send to the mailing lists as indicated in the doc. Make sure to use bcc as noted for the “announce” lists.
Announcement for a new major version
Adjust the final-release announcement subsection with a very brief summary gleaned from the download page. Adjust the blog & tweet texts as well.
Share the draft as a link to the doc heading with the ICU team, invite comments and edits.
Share the draft as a link with the Unicode editorial committee, invite comments, discuss, adjust as agreed.
When ready, send to the mailing lists as indicated in the doc. Make sure to use bcc as noted for the “announce” lists.
Notify Rick McGowan for the Unicode blog posting and Ken Lunde for tweeting.
Notify Ken Whistler (Unicode) to update the ICU version & date on https://www.unicode.org/releases/
Put a News item on the ICU project site.
Announcement for a maintenance update
Same as for a release candidate, but start by copying the section for the last maintenance update in the doc.