CLDR BRS Post Items (Section E) for Rick

Actions for Rick, section "E" of the CLDR Release BRS

Remove the yellow from UTS#35 draft, and clean up everything for posting. Run W3C validations and link checks on all parts. Make sure links to images are correct before posting, and create a symlink to the image directory within the reports/tr35/tr35NN directory. Make sure that the revision is headed with "updated for" rather than "proposed update for". Double check the text and links for the DTD and versions in the header. Check into SVN. Then post as final UTS #35 on unicode site. Double-check the DTD and header pointers again when finished.

Create a new directory, e.g. and populate with the zip files from John. Double check filenames,, (Add and if John made them.) For each of the zip files, create a symlink that is the versioned name of the file. E.g. make a symbolic link to Etc.

Update link to "latest" by modifying /home/httpd/htdocs/.htaccess to change the redirect of /Public/cldr/latest

Change the chart redirects to point to the new versions. For testing, change the links on the page to the right to the new version, eg /22.1/ => /23/. Then spot check. Make the beta-charts links point to 'not found' page (until we regenerate beta-charts). Chart redirects are found in /home/httpd/htdocs/cldr/.htaccess ; of the form "Redirect /cldr/charts". Also see the "RewriteRule" section in /etc/httpd/conf/httpd.conf where it points cldr/charts to the "latest" and "dev" release explicitly (around line 740 of the conf file). There are 2 redirects, one for dev and one for the new version that's being released. See also the "stable links info" on Sites: This must be updated and the server gracefully restarted. (Command "apachectl graceful" works.)

Bug-How-To-Links: (Copy out the text of the test links on that page; Change the {latest} to be current release, and any prev release numbers to the current one, the test them all.) See also info here and update DEV and LATEST as needed: Verify links on work.

Verify that the links on the release page (e.g. ) are correct, and Draft is removed from the text.

Modify so that it includes a new row on the top (Latest:), with the information from the current release (eg ). Might be easiest to do in HTML mode. Most of the latest row should remain standard, but some of the targets of those anchors need to be updated for each release. Click through all and test them.

Change the dtd redirection, in /home/httpd/htdocs/cldr/dtd/.htaccess so that points to is new. Upload the tagged dtd files there. Edit /home/httpd/htdocs/cldr/dtd/.htaccess and bump the version number to "X+1". To verify that these are properly accessible, type the new dtd (X+1) URL into a browser, and if you get to the head of CVS, it's correct. (The tagged DTD files are in, in case they aren't supplied separately; get them from the zip file under common/dtd directory.)

Update and other pages that refer to version files directly. List here:

In the charts page, add a row to the top of the table for the new release.

Update the sidebar for the release, eg: CLDR 1.8 Schedule: 2009-NN
Latest Release: CLDR 1.8
and gray out the schedule. NOTE: Only the "site owner" can change the sidebar. Go to "edit site layout" in the "More" pulldown, then click on the Milestones header to edit that section. List the latest release (26), and delete all but 2 releases. Change "nn Release" to "nn Released" and put a link on "Released" to the release page.

NEW: Go to the bottom of the home page and find the table for "Regular Semi-Annual Schedule". In HTML mode, copy which ever half of the table is for the upcoming release (spring or fall), and update the sidebar with that section of the table by pasting in the different HTML blob of the table.

Create a new blog page from ; publish the blog, and update the Unicode Home page. The announcement listing should be in New Releases, not Other News. Tweet a little announcement pointing to the blog as needed. (Note: Mark and others on the ed committee can update and edit the blog/twitter as

As an announcement, send contents of to all the Unicode mailing lists -- Usually first make sure the list is up to date by logging in as root and running "". Mark, Steven, Rick, and John are all able to send announcements to "". (NOTE: best to double-buffer and check the HTML before sending to the list; HTML pasted in from sites and other places often has quirks.)

Normal announcement mechanism is described in: (for Rick or others to follow)

Verify that these are empty before trunk opens: -- and then Notify that the trunk is open: e.g., say "Now that CLDR X.Y has been released, the SVN trunk ( ) is open for commits towards the next release." Use a subject line something like: "CLDR X.Y - trunk now open", where X.Y is the next release. If report 51 is not empty, verify that anything remaining is either the result of a misticketed item, or that any commits had net zero effect on trunk ( for example, a change that was later backed out ).

Create a new stub release page for the next release by copying the previous page (...downloads/cldr-31 or whatever) and state that it's a stub. Retain the top-level headers from the previous release page. Yellow some sections for the update. Near the top, add this line:
This version is currently in development. See the latest release.

Update these two pages as required with the dev version pointer to the new page:

Update all of the "CURRENT" reports in trac to point to the new current milestones. Make sure $user isn't replaced by your name. The affected reports are (52, 61, 66, 76, 77, 80) and (62, 63).


When making an "alpha" release page, check the header info in the table. Before the release, some links should go to "dev" version rather than a non-existent final version.

Rel note = dev version
Data = no link
Charts = dev version
Spec = proposed
Delta = link to the query for milestone
SVN Tag = dev version
DTD delta = "trunk" version