Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Build the release & run unit tests.

    No Format
    ./build.sh clean dist test
  2. Check that release files look ok - e.g. unpack the sources and run tests.
  3. Sign the release (see Step-By-Step Guide to Mirroring Releases for more information).

    No Format
    ./build.sh sign
    

    To sign a release, your key must be present in the dist/KEYS file. See the Apache guide to Signing Releases for more details. Also, if you've updated the dist/KEYS file, be sure to update the public Apache KEYS file as well:

    Code Block
    ssh people.apache.org
    cd /www/www.apache.org/dist/avro
    svn up

...

  1. Copy release files to the public staging area https://dist.apache.org/repos/dist/dev/avro/

    No Format
    svn co https://dist.apache.org/repos/dist/dev/avro/ avro-dev-dist
    mkdir avro-dev-dist/avro-X.Y.Z-rcR
    cp -pr avro/dist/* avro-dev-dist/avro-X.Y.Z-rcR
    cd avro-dev-dist
    svn add avro-X.Y.Z-rcR
    svn commit -m "Artifacts for Avro X.Y.Z RCR"
  2. Stage two versions of Before 1.9.x  stage the Hadoop 1 version of the Java artifacts to the Maven repository:

    No Format
    mvn clean -P dist,sign deploy -DskipTests=true -Dhadoop.version=1 -Dgpg.passphrase=XXX -Davro.version=X.Y.Z
    

    (From 1.9.x we do not support Hadoop 1 anymore. All the Java artifacts are created for Hadoop 2 by default.)

  3. Stage the default Hadoop 2 version of Java artifacts to the Maven repository:

    No Format
    mvn clean -P dist,sign deploy -DskipTests=true -Dgpg.passphrase=XXX -Davro.version=X.Y.Z
    
  4. Find the the Staging Repository, and close it.
  5. Call a release vote on dev at avro.apache.org.
    Include the URL of the staging repository.

...