Create a release branch in SVN

See "Tag related svn files".

Once the branch is created, only changes necessary for the target release are merged in from the trunk.

Upgrade LocaleExplorer and other demos/samples

... to the ICU project site.

Build the icuapps module following the README's. Update code and/or docs as needed. "Reference" platforms for icuapps are: RedHat Linux and win32. On Linux, icuapps is built against the "make install "'ed ICU. So, run ICU4C's configure with --prefix=/some/where pointing to where ICU4C should be installed, and also follow icuapps's README.

Install the new locale explorer and other demos/samples onto the public demo hosting site.

ICU Collation Demo

Update the ICU collation demo's index.html with the new ICU version’s available collators. For example, by running icuapps/trunk/webdemo/collation/build.sh (after modifying it for your system) and copy-pasting the output available-collators.txt into index.html. See for example the changes for http://bugs.icu-project.org/trac/ticket/11355

For details see the comments at the start of the build.sh file.

Tag related svn files

⚠ Careful! The following examples contain specific version, revision and ticket numbers. Adjust them for the current release! Easiest: Paste into an editor, fix, then paste into the terminal.

Also, the following command lines use repository-relative paths. For this to work, you have to be in an svn workspace for the ICU repository. Alternatively, replace the "^" with the repository root (svn+ssh://source.icu-project.org/repos/icu).

Before you tag

Sanity check: Update to the lastest repository revision. (Trunk if you copy from trunk, maintenance branch if you copy from there.)

Release candidate

Create the maintenance branch from the current known good trunk revision, using the rc release ticket.

Create the rc tag from there.

Release

Create the release tag from the maintenance branch.

Update the "latest" tag.

Maintenance release

Create the maintenance release tag from the maintenance branch.

Update the "latest" tag.

ICU 58 and earlier

Tag related svn files, for icu, icu4j and (for final releases) tools file trees. We tag the tools tree so that we can reproduce the Unicode tools that were used for the Unicode data files in this release.

For a Release Candidate, just tag, don't branch, and only tag icu & icu4j.

For the final release, branch then tag. Copy the trunk to maint/maint-4-8 and copy that to tags/release-4-8. Specify the source revision explicitly via -r so that you don't inadvertently pick up an unexpected changeset. Make sure that the trunk at the source revision is good.

We do not tag the data & icuapps trees. Steven Loomis writes on 2011-may-23:

My thought had been (in the CVS days) to take a 'snapshot' of these items. However, in SVN all you need is a date or a revision number (such as r30140).

So, probably, we don't need to tag these two (icuapps or data).

Tools are more important because those tools are actually used in the release.

Create ICU download page

Create the download page before the first milestone, if we have one, or before the release candidate.

Log into the ICU homepage Google Site. (If you don't have write access, ask one of the editors to grant you access.)

Verify that there is not already a page for the upcoming release: Either via the sitemap, or on the bottom of the main download page where it says something like "Subpages (27): View All".

Copy the download page for the last release: Go to that page, gear menu, Copy page; "Name your page" using just the major version number for now (e.g., "61") so that the page URL is just that number, select "Put page under Downloading ICU", click the red COPY button.

Adjust the new page as needed: Change the title to "Download ICU 61 Release Candidate" (with the right version number...), remove contents specific to the previous release, update all version numbers, update all links.

Put a big, bold+italics, red warning at the top like "This version has not been released yet. Use it for testing but not in production!"

Save the page. It is generally a good idea to save frequently. For further edits, simply go back into edit mode. (Keyboard shortcut 'e' for edit, ctrl+s for save.)

Add new contents for the upcoming release: Grab some text from the sibling Unicode and CLDR release notes, look at the proposal status doc for this release, make a pass through the api/enhancement tickets fixed in this release or under reviewing/reviewfeedback.

Look at the download pages of the last two releases for templates for things like a Migration Issues section etc.

Ask everyone on the team to add stuff & details.

Once the page has been created and various people are invited to edit it, everyone should keep editing short so that the page is not locked for others for long periods of time.

Maintenance release

For a maintenance release, look at the ICU 60 page which includes 60.2.

Milestone on the main download page

We had the following HTML on the main download page for ICU 4.8M1 = 4.7.1:

Upload Release Source/Binaries

Download Directories are located at, for example, 
  icu-project.org:/home/htdocs/ex/files/icu4c/4.4.2
corresponding to  http://download.icu-project.org/ex/files/icu4c/4.4.2/

Look at previous releases for an example.

Java Source/Bin:   See Building ICU4J Release Files

C source/binary: WORK IN PROGRESS

• Source and Linux Bins: requirements:   Unix make + docker
• (You need to install docker and docker-compose, do not proceed until docker run hello-world works!)
• $ git clone https://github.com/unicode-org/icu-docker
• $ cd icu-docker
• $ svn co https://ssl.icu-project.org/repos/icu/tags/release-XXX src/icu
• $ less README.md
• Follow those instructions.
• Source and binaries will show up in ./dist/ but the names don't match what's needed on output.
• Windows Bin:
• Build with MSVC x64 Release. (See the ICU readme.html file for details).
• Open a command prompt.
  
• > cd C:\icu\icu4c\  (or wherever you have ICU located).
• > powershell
  
• > Set-ExecutionPolicy -Scope Process Unrestricted
• > .\packaging\distrelease.ps1
• This will produce the file "source\dist\icu-windows.zip", which will need to be renamed before uploading.
• For example, the binaries for ICU4C v61.1 generated with VS2017 were named "icu4c-61_1-Win64-MSVC2017.zip".
  
• AIX Bin: (AIX is broken and ignored for now.)
• login to gcc119.fsffrance.org and copy the ICU4C source archive created above to there.
• $ gzip -dc icu4c-XXX-src.tgz | tar xf -
• $ cd icu
• $ PATH=/opt/IBM/xlC/13.1.3/bin:$PATH source/runConfigureICU AIX
• (The above command line doesn't actually work, see ICU Ticket #13639 for a workaround.)
• $ gmake DESTDIR=/tmp/icu releaseDist
• That last step will create a directory in /tmp/icu - zip that up to make the release.
• In case /tmp happens to be full, see the mailing list archive for advice.

Sign all archives created above with your own personal PGP key:

$ gpg --armor --detach-sign icu4c-xxx-xxx.zip

Create three different '.md5' files for icu4j (all files),  icu4c (source) and icu4c (binaries).

Use cfv: http://cfv.sf.net like this to create a .md5 file:
     cfv -t md5 -C -f icu-……-src.md5      somefile.zip somefile.tgz …

SHASUM512.txt