• Home
  • Line#
  • Scopes#
  • Navigate#
  • Raw
  • Download
1---
2layout: default
3title: Announcements
4parent: Release & Milestone Tasks
5grand_parent: Contributors
6nav_order: 10
7---
8
9<!--
10© 2021 and later: Unicode, Inc. and others.
11License & terms of use: http://www.unicode.org/copyright.html
12-->
13
14# Announcements
15{: .no_toc }
16
17## Contents
18{: .no_toc .text-delta }
19
201. TOC
21{:toc}
22
23---
24
25## First milestone/candidate for a release
26
27We write drafts of announcements in the ["ICU announcements" Google
28doc](https://docs.google.com/document/d/1rSVKZaus2K3rF66bMfDjYZnA2KTSJZUBz4C58GQMHsQ/edit).
29
30When there is no section yet for the upcoming release, then copy the whole
31section from one of the previous two full releases and adjust the version
32numbers everywhere in the copied headings and text.
33
34### Announcement for a release candidate
35
36Adjust the release candidate announcement subsection with a very brief summary
37gleaned from the download page.
38
39Share the draft as a link to the doc heading with the ICU team, invite comments
40and edits.
41
42When ready, send to the mailing lists as indicated in the doc. Make sure to use
43bcc as noted for the "announce" lists.
44
45### Announcement for a new major version
46
47Adjust the final-release announcement subsection with a very brief summary
48gleaned from the download page. Adjust the blog & tweet texts as well.
49
50Share the draft as a link to the doc heading with the ICU team, invite comments
51and edits.
52
53Share the draft as a link with the Unicode editorial committee, invite comments,
54discuss, adjust as agreed.
55
56When ready, send to the mailing lists as indicated in the doc. Make sure to use
57bcc as noted for the "announce" lists.
58
59Notify Rick McGowan for the Unicode blog posting and Ken Lunde for tweeting.
60
61Notify Ken Whistler (Unicode) to update the ICU version & date on
62<https://www.unicode.org/releases/>
63
64Put a News item on the ICU project site.
65
66### Announcement for a maintenance update
67
68Same as for a release candidate, but start by copying the section for the last
69maintenance update in the doc.
70
71## Update the reference for ICU in the external sites
72
73**For freshmeat.net**
74
751.  <http://www.freshmeat.net/>
762.  Login under the correct account.
773.  I usually search for: icu unicode
784.  Click on the project returned
795.  Under the 'project' drop down, choose 'Add release'
806.  We have (thankfully) only one branch of development- choose Default
817.  Release info
82    *   release focus: Choose the one which best fits
83    *   Version
84    *   Changes: be VERY brief, and include links if needed.
85        Please read the other ICU4C/ICU4J updates to get an idea for how we are
86        wording these. DO NOT use bulleted lists. DO use short 'sentences'.
87        Remember they can go to the release list and/or bug DB for the full
88        scoop!
89        Put the URL to the 'release notes' (i.e.
90        http://oss.software.ibm.com/icu/download/(version)/ ) in the changes
91        list.
92    *   tar/gz, zip: Put the FULL URLs to the actual files, here
93    *   Changelog: Leave BLANK. This is for a single page of ALL release changes
94        (Actually: http://oss.software.ibm.com/icu/download/ fits this fairly
95        well.)
96    *   License - leave at MIT/X
97    *   mailing list: I set this to the main mailing list page.
98        (http://oss.software.ibm.com/icu/archives/)
99    Click 'go on..'
1008.  PREVIEW.
101    Very important- Check:
102    *   SPELLING
103    *   links!!!!! Make sure they go where we want
104    *   accuracy - version number is OK?
105    Remember that this is an important PR face for ICU4C and ICU4J.
1069.  Submit!
107
108That's it. Submissions take some time (<24 hrs) to go on. I guess they check the
109accuracy as well- not sure here. (Steven Loomis, 2001-06-14)
110
111**Other sites**:
112
113[slashdot](http://slashdot.org/), [newsforge](http://newsforge.com/),
114[developerWorks unicode zone](http://www.ibm.com/developerworks/unicode/),
115[developerWorks open-source
116zone](http://www.ibm.com/developerworks/opensource/), [developerWorks java
117zone](http://www.ibm.com/developerworks/java/) (send email to `dWnews <at>
118us.ibm.com`)
119
120[ICU sourceforge News](http://sourceforge.net/projects/icu) - login here, go to
121News, Admin, and submit a news item as an administrator.
122
123---
124
125#### LanguageTech Net News (tm)
126
127"LanguageTech Net News" features the latest news for language technology and
128multilingual computing. It is prepared from materials compiled and maintained by
129the research editors at "[MultiLingual Computing &
130Technology](http://www.multilingual.com/)" and the Language Technology Research
131Center.
132
133Press releases and submissions are always welcomed and encouraged. Please send
134e-mail to [news@multilingual.com](mailto:news@multilingual.com), faxes to
135208-263-6310 and postal mail to MultiLingual Computing, Inc., 319 North First
136Avenue, Sandpoint, ID 83864 USA, or call 208-263-8178.
137
138To view archived issues of "LanguageTech Net News" visit
139<http://www.multilingual.com/>.
140
141To subscribe to "LanguageTech Net News" go to
142<http://www.multilingual.com/multilingualpress/> or send an e-mail to
143[news-l-subscribe@multilingual.com](mailto:news-l-subscribe@multilingual.com).
144