Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: add step - mark maven artifacts as released

...

  1. Tag the release:
    No Format
    svn move https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z-rcR \
    https://svn.apache.org/repos/asf/hive/tags/release-X.Y.Z -m "HiveX.Y.Z release."
    
  2. Copy release files to the distribution directory and make them writable by the hive group.
    No Format
    ssh people.apache.org
    cp -pR public_html/hive-X.Y.Z-candidate-0/ /www/www.apache.org/dist/hive/hive-X.Y.Z
    cd /www/www.apache.org/dist/hive
    chgrp -R hive hive-X.Y.Z
    chmod -R g+w hive-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.
    No Format
    ssh people.apache.org
    cd /www/www.apache.org/dist/hive
    rm -rf hive-A.B.C; rm stable
    ln -s hive-A.B.D stable
    
  4. Wait 24 hours for release to propagate to mirrors.
  5. Prepare to edit the website.
    No Format
    svn co https://svn.apache.org/repos/asf/hive/site
    
  6. Copy the new release docs to publish/docs/rX.Y.Z:
    Code Block
    tar xvf hive-X.Y.Z.tar.gz '*/docs'
    mv hive-X.Y.Z/docs publish/docs/rX.Y.Z
    svn add publish/docs/rX.Y.Z
    
  7. If this is a bugfix release, delete the documentation for the obsoleted release.
    Code Block
    svn rm publish/docs/rX.Y.Z-1
    
  8. Update the documentation links in author/src/documentation/content/xdocs/site.xml.
  9. Update the release news in author/src/documentation/content/xdocs/releases.xml.
  10. Update publish/.htaccess with the current release and any new redirects for obsoleted releases.
  11. Regenerate the site, review it, then commit it. The live site is automatically deployed from subversion after a few minutes.
    Code Block
    ant -Dforrest.home=/usr/local/forrest -Djava5.home=/usr/local/jdk1.5
    firefox publish/index.html
    svn commit -m "Updated site for release X.Y.Z."
    
  12. Update JIRA
    1. Ensure that only issues in the "Fixed" state have a "Fix Version" set to release X.Y.Z.
    2. Release the version. Visit the "Administer Project" page, then the "Manage versions" page. You need to have the "Admin" role in Hive's Jira for this step and the next.
    3. Close issues resolved in the release. Disable mail notifications for this bulk change.
  13. Login to the Apache Nexus server and mark the release candidate artifacts as released.
  14. Send a release announcement to Hive user and dev lists as well as the Apache announce list. This email should be sent from your Apache email address:
    No Format
    From: you@apache.org
    To: user@hive.apache.org, dev@hive.apache.org, announce@apache.org
    Subject: [ANNOUNCE] Apache Hive X.Y.Z Released
    
    The Apache Hive team is proud to announce the the release of Apache
    Hive version X.Y.Z.
    
    The Apache Hive (TM) data warehouse software facilitates querying and
    managing large datasets residing in distributed storage. Built on top
    of Apache Hadoop (TM), it provides:
    
    * Tools to enable easy data extract/transform/load (ETL)
    
    * A mechanism to impose structure on a variety of data formats
    
    * Access to files stored either directly in Apache HDFS (TM) or in other
      data storage systems such as Apache HBase (TM)
    
    * Query execution via MapReduce
    
    For Hive release details and downloads, please visit:
    http://hive.apache.org/releases.html
    
    Hive X.Y.Z Release Notes are available here:
    https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310843&version=12316178
    
    We would like to thank the many contributors who made this release
    possible.
    
    Regards,
    
    The Apache Hive Team
    

...