Page History

...

1. Tag the release:

   Code Block
   svn move https://svn.apache.org/repos/asf/zookeeper/tags/release-X.Y.Z-rcR \ https://svn.apache.org/repos/asf/zookeeper/tags/release-X.Y.Z -m "ZooKeeper X.Y.Z release."

2. Copy release files to the distribution directory and make them writable by the zookeeper group. (don't preserve timestamps as it can cause problems for the mirroring s/w)

   Code Block
   ssh people.apache.org cp -r --preserve=mode,ownership public_html/zookeeper-X.Y.Z-candidate-0 /www/www.apache.org/dist/zookeeper/zookeeper-X.Y.Z cd /www/www.apache.org/dist/zookeeper chgrp -R zookeeper zookeeper-X.Y.Z chmod -R g+w zookeeper-X.Y.Z

3. The release directory usually contains just two releases, the most recent from two branches, with a link named 'stable' to the most recent recommended version.

   Code Block
   ssh people.apache.org cd /www/www.apache.org/dist/zookeeper rm -rf zookeeper-A.B.C; rm stable ln -s zookeeper-A.B.D stable

4. Wait 24 hours for release to propagate to mirrors.
5. Prepare to edit the website.

   Code Block
   svn co https://svn.apache.org/repos/asf/zookeeper/site

6. Copy the new release documentation into the content/doc directory

   Code Block
   cd site/trunk/content/doc mkdir rX.Y.Z cd rX.Y.Z tar xvf /www/www.apache.org/dist/zookeeper/zookeeper-X.Y.Z/zookeeper-X.Y.Z.tar.gz 'zookeeper-X.Y.Z/docs' mv zookeeper-X.Y.Z/docs/* . rm -r zookeeper-X.Y.Z cd .. svn add rX.Y.Z

7. Update the release news in site/trunk/content/releases.textile
8. Update the nav panel to include X.Y.Z (which may now be "current") site/trunk/templates/sidenav.textile
9. Regenerate the site, review it, then commit it. (checkout https://svn.apache.org/repos/infra/websites/cms/build if you haven't already)

   Code Block
   cd site/trunk .../apache_cms_build/build_site.pl --source-base . --target-base /tmp/sitegen <open /tmp/sitegen/index.html in your browser and verify the site> svn commit -m "Updated site for release X.Y.Z."

10. Update the "current" doc pointer if necessary (as CMS doesn't currently support symlinks in build/staging we need to push this directly to production)

    Code Block
    svn co https://svn.apache.org/repos/infra/websites/production/zookeeper/content cd content/doc rm current ln -s rX.Y.Z current svn commit -m "Updated current pointer for release X.Y.Z"

11. Review your changes on the staging site: http://zookeeper.staging.apache.org
12. Deploy your site changes.

    Code Block
    https://cms.apache.org/redirect?uri=http%3A//zookeeper.apache.org/ publish the site changes

13. Send announcements to the user and developer lists once the site changes are visible. Here is a sample email:

    No Format

    Subject: [ANNOUNCE] Apache ZooKeeper X.Y.Z The Apache ZooKeeper team is proud to announce Apache ZooKeeper version X.Y.Z ZooKeeper is a high-performance coordination service for distributed applications. It exposes common services - such as naming, configuration management, synchronization, and group services - in a simple interface so you don't have to write them from scratch. You can use it off-the-shelf to implement consensus, group management, leader election, and presence protocols. And you can build on it for your own, specific needs. For ZooKeeper release details and downloads, visit: http://zookeeper.apache.org/releases.html ZooKeeper X.Y.Z Release Notes are at: http://zookeeper.apache.org/doc/rX.Y.Z/releasenotes.html We would like to thank the contributors that made the release possible. Regards, The ZooKeeper Team

14. In Jira, ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
15. In Jira, "release" the version. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in ZooKeeper's Jira for this step and the next.
16. In Jira, close issues resolved in the release. Disable mail notifications for this bulk change.

...