Managing a Release

The Apache Yetus community encourages all committers to help on driving releases. To that end, this section seeks to outline the tools and process you'll use when managing a release. Note that these are our community norms; they do not supersede foundation policy should the two disagree.


First, let's review what you'll need to complete all steps of the process.

Committer Access

While the Yetus project aims to get new contributors involved in as much of the project as possible, ASF policy requires that all Release Managers be committers on the project. As a practical matter, release candidates are staged in a project-specific svn repository that only project committers have write access to.

Hardware You Own and Physically Control

ASF release policy requires that release manager verification and signing of artifacts take place on hardware you have as much control over as possible. This is because your private signing keys will be involved and those should only be accessible on such hardware, to minimize the exposure to third parties. For more details, see the ASF release policy's relevant text.

Cryptographic Signing Tools and Keys

Everything distributed by an ASF project must be signed before distribution (ref ASF release policy on releases and supplemental artifacts). The short version of the rationale is that downstream users should be able to verify that the artifacts they make use of were ones blessed by the project PMC. For a longer explanation, see the ASF release signing document's motivation section.

In practice, the requirement for artifact signing is handled via OpenPGP signatures. For all practical purposes, this means you'll need to use Gnu Privacy Guard (aka GnuPG or GPG). It also means you'll need to have a public/private key pair you control that is published in your name. Thankfully, the ASF provides an excellent overview to using GPG in the ASF OpenPGP guide. In particular, if you don't already have a published key be sure to follow the instructions in the section How To Generate A Strong Key.

Version Control System Tools

In addition to the git tools you normally use to interact with the Yetus project, managing a release also requires a properly configured Apache Subversion installation. This additional tool is because both the staging area for release candidates and the final distribution mechanism for PMC approved releases rely on Subversion.

The Subversion project provides a nice set of pointers to installing on various OSes, in most cases via package managers, on their page Apache Subversion Binary Packages. Alternatively, you could start with a source release and manually build the necessary tools by starting at Apache Subversion - Download Source Code.

Project Specific Build Tools

To create our convenience binary artifact and the Apache Maven plug-ins, you'll need to build both our project docs and all of the individual components. If you usually only work on one part of the project, say Yetus Precommit, this might require some additional programming languages and tools.

All of these tools should be in the Docker container that is launched by using the ./ script. If you wish to build outside of the container (not recommended), you will need:


When you first start managing a given release, you'll have to take care of the following tasks. Except for creating the release staging branch, these can be done in any order.

Verify the Year

Before attempting to do a release, verify that the documentation, website, etc, has the current year in the copyright notices. Given that fixing that requires a patch, this should be done in advance of other release work!

Ensure Your Public Key is in KEYS

Like many ASF projects, we provide a single file that downstream folks can use to verify our release artifacts. It's located in the project's distribution area You can read about this file in the ASF guide to release signing section. If your public key is not already included in the KEYS file, you will need to add it. You can either follow the instructions in the previously mentioned guide or those at the top of the actual KEYS file. In any case, you will need to use Subversion to update the KEYS file in the project's distribution area. Note that this area is writable only by the project PMC. If you are not yet on the PMC, your last step should be providing a patch rather than committing.

Example commands:

$ svn co yetus-dist-release
$ cd yetus-dist-release
$ (gpg --list-sigs <your key name> && gpg --armor --export <your key name>) >> KEYS
$ svn diff
$ svn commit -m "Added myself to KEYS."

Work in JIRA

Like the rest of our project activity, we'll use an issue in JIRA to track managing the release. You should create this issue and assign it to yourself. As you make your way through the process of creating and running votes on release candidates, this issue will give you a centralized place to collect pointers to your work.

  1. Browse to the ASF JIRA instance's "create issue" page:!default.jspa
  2. Select "Yetus" for the Project and "Task" for the issue type. Click "Next".
  3. On the next screen, use a subject line like "Release VERSION", with an appropriate version number. Fill in the following fields and click "Create".
    • The component should be "website and documentation"
    • Affects Version and Fix Version should both be the version you are releasing
    • Assignee should be you
    • Add a description similar to "Generate release candidates as needed to create a VERSION release." with an appropriate version number.
  4. Next, create a shortened link to the JIRA version's release notes. This link should use the ASF link shortener, To find the appropriate release notes page:
  5. Browse to the ASF URL shortener:
  6. Paste the URL into the "URI" field
  7. Set the optional key field to 'yetus-_version_-jira'
    For example, on the 0.7.0 release, you would use for the URI field and 'yetus-0.7.0-jira' for the key.
  8. Finally, you should create a JIRA version that matches the release following the one you are managing. This action is so that folks can continue to work on things that won't make it into the in-progress release while we evaluate candidates.
    1. Browse to the ASF JIRA project management page for versions:
    2. Fill in a version one minor version up from the release you're managing. E.g., when managing the 0.7.0 release, fill in 0.3.0.
    3. Set a start date of today.
    4. Click "Add"

Work in Git

Once you have an issue to track things, you can create the git branch for staging our release. This separate branch will allow you to polish the release while regular work continues on the master branch. You will need to update master for the next SNAPSHOT version and the branch for the release.

Example commands, presuming the release under management is 0.7.0 and the JIRA issue is YETUS-XXX:

$ # Ensure master is up to date
$ mvn clean
$ git fetch origin
$ git status
# On branch master
# Your branch is behind 'origin/master' by 6 commits, and can be fast-forwarded.
nothing to commit (working directory clean)
$ git rebase origin/master
First, rewinding head to replay your work on top of it...
Fast-forwarded master to origin/master.
$ git status
# On branch master
nothing to commit (working directory clean)
$ # create a branch and push without changes
$ git checkout -b YETUS-XXX
Switched to a new branch 'YETUS-XXX'
$ git push origin YETUS-XXX
$ # find files we need to update for release
$ grep -rl "0.7.0-SNAPSHOT" * 2>/dev/null

At this point, you should edit the files mentioned above. They must have the version we expect upon a successful release. Search for instances of VERSION-SNAPSHOT and replace with VERSION; e.g., 0.7.0-SNAPSHOT should become 0.7.0:

$ perl -pi -e 's,0.7.0-SNAPSHOT,0.7.0,g' $(find . -type f)

After you are done, create a branch-specific patch and then prepare to update the master branch.

$ git add -p
$ git commit -m "YETUS-XXX. Stage version 0.7.0."
$ git format-patch --stdout origin/YETUS-XXX > path/to/patches/YETUS-XXX-YETUS-XXX.1.patch
$ git checkout master
$ grep -rl "0.7.0-SNAPSHOT" * 2>/dev/null

Now update these files, but this time you should update them for the next minor version's SNAPSHOT. e.g., 0.7.0-SNAPSHOT should become 0.8.0-SNAPSHOT:

$ perl -pi -e 's,0.7.0-SNAPSHOT,0.8.0-SNAPSHOT,g' $(find . -type f)

After you are done, create a patch.

$ git add -p
$ git commit -m "YETUS-XXX. bump master version to 0.8.0-SNAPSHOT"
$ git format-patch --stdout origin/master > path/to/patches/YETUS-XXX.1.patch

Both of these patch files should be uploaded to your release issue for review. Push them to the repository once the patches get approval.

Release Candidate(s)

Depending on how candidate evaluation goes, you may end up performing these steps multiple times. Before you start, you'll need to decide when you want each candidate's vote thread to end. ASF policy requires a minimum voting period of 72 hours (ref ASF Voting Policy), so you should ensure enough padding to complete the candidate generation process in time. Ideally, you would plan to post the vote thread on a Friday morning (US time) with a closing date on Monday morning (US time).

  1. Update JIRA version release date. Browse to the JIRA project version management page, mark the version as 'Release', and set the release date. Our generated release notes will use this date.
  2. Update your ${HOME}/.m2/settings.xml file to include the Maven snapshot information as indicated on
  3. Build release artifacts. You should use our convenience script to create the tarballs and markdown documents for a release. Run the following from the release staging branch and inspect the results:

    $ mvn --batch-mode clean deploy -Papache-release
    $ mvn --batch-mode site site:stage
    $ ls -lah yetus-dist/target/artifacts/*
  4. Check out the staging area for release candidates and make a directory for this candidate, somewhere outside of your working directory. Copy the artifacts from the previous step into place. For example, when working on RC1 for the 0.7.0 release

    $ svn co `` yetus-dist-dev
    $ cd yetus-dist-dev
    $ mkdir 0.7.0-RC1
    $ cd 0.7.0-RC1
    $ cp path/to/yetus/target/ path/to/yetus/target/ path/to/yetus/target/*.tar.gz .
  5. While still in the staging area, sign the artifacts and create the needed checksum files:

    $ for artifact in *; do
       echo ${artifact}
       gpg --use-agent --armor --output "${artifact}".asc --detach-sig "${artifact}"
       gpg --print-mds "${artifact}" >"${artifact}".mds
       shasum -a 512 "${artifact}" >"${artifact}".sha512
  6. Push the release candidate to staging distribution. This will make the artifacts visible for the vote.

    $ cd ..
    $ svn add 0.7.0-RC1
    $ svn commit -m "stage Apache Yetus 0.7.0-RC1"
    Afterward, the artifacts should be visible via the web under the same URL used when checking out. In the case of 0.7.0-RC1: <>
  7. Examine staged maven build. Go to the ASF repository and log in with your asf LDAP credentials. Look for the staging repository with a name that includes "yetus". Clicking on it will give you a link to an "Open" repository. You can examine the structure in the Nexus API while you're logged in. If it looks essentially correct, "Close" the repository. Refreshing and clicking on the repository will give you a link in the Summary tab that other folks can use to interact with the repository.
  8. Create a short link that should point to some online timezone conversion utility that will point to when the vote will end. ASF votes often use's Event Time Announcer:
  9. Call a vote on the release candidate. At this point, you have everything you need to call a vote. Your vote thread must contain "[VOTE]" in the subject line, a link to the candidate staging area you created, a source repository commit hash, and voting rules. It should also contain hashes for the artifacts. Here is an example draft for 0.7.0-RC1, update it as appropriate for your release:

     Subject: [VOTE] Apache Yetus 0.7.0-RC1
     Artifacts are available:

     As of this vote the relevant sha512 hashes are:
     SHA512 ( = 6dbb09360b3116d12aed275d223f43b50a95e80aab1981d5bb61886ceb4b3b57475c976e9465f3fb28daaf62b8cae113b8ee87eae35a212c861fbc434632073b
     SHA512 ( = 72a12eb96f32d35a7660967caf2ce5261bd7829ddc56962c97c7b1e71cebfa026c055258a9db1b475581ca0a3ae13d9f9651724573cacaaad9972a89ff809875
     SHA512 (yetus-0.7.0-bin.tar.gz) = 28f8c94fb2e22a70674be6070f63badf98e1b022ee25c171fff9629d82ca899fc7eb509ffee2a5c50f2bec10cbb20632fb9fddcab5ebcf5c2511a3ae7edbc56b
     SHA512 (yetus-0.7.0-src.tar.gz) = 316cf36c97b301233a9b163c8b8d7ec47bdd3d042b1821820b8ac917e5668e610ec8c35fd438e45a64e05215b183ce1ad7321065883fb84ccac8b4744a7fb73e
     Source repository commit: 1e8f4588906a51317207092bd97b35687f2e3fa3
     Maven staging repository:
     Our KEYS file is at:
     All artifacts are signed with my key (DEADBEEF)
     JIRA version:
     Please take a few minutes to verify the release[1] and vote on releasing it:
     [ ] +1 Release this package as Apache Yetus 0.7.0
     [ ] +0 no opinion
     [ ] -1 Do not release this package because...
     The vote will be subject to Majority Approval[2] and will close at 8:00 PM
     UTC on Monday, Xxx XXth, 2018[3].
     [3]: to find this in your local timezone see:
  10. Close the vote after the deadline. Once the deadline in the vote thread passes, tally the vote and post a suitable response that changes the subject line to start with "[RESULT]". If the vote failed, ensure there are issues in JIRA for any problems brought up. When they are closed, repeat the steps for creating a release candidate. If the vote passed, proceed to the Cleanup section


You are free to make whatever checks of our release candidate artifacts suit your use, but before voting, there are certain checks you must perform according to ASF policy. This section will walk you through the required checks and give some guidelines on additional checks you may find useful. Besides the fact that downloading the release artifacts must happen first, generally, you can perform these in any order that suits you.

Download release artifacts

You will need to download the release candidate files, include the artifacts and accompanying signatures and checksum files. The directory containing them should be in the [VOTE] thread. You can use wget or a similar tool to recursively grab all the files rather than download them one at a time. If you are not familiar with wget, it will create a nested set of directories based on the structure of the hosting site for release candidates.

For example, if we use the URL from our exemplar VOTE email, the process would look like this:

$ wget --recursive --no-parent --quiet ''
$ find -type f

Lastly, if you haven't verified a release before, you'll need to download and import the public keys for the project's release managers. The public keys are located in the KEYS file that should have been mentioned in the [VOTE] thread announcement. The specific output of the following commands will vary depending on how many release managers there have been and which keys, if any, you have previously imported.

$ curl --output KEYS.yetus --silent ''
$ gpg --import KEYS.yetus
gpg: key 0D80DB7C: "Sean Busbey (CODE SIGNING KEY) <>" not changed
gpg: Total number processed: 1
gpg:              unchanged: 1

ASF required checks

ASF policies require that binding votes on releases be cast only after verifying proper licensing and provenance. For specific details, you should read the ASF Release Policy's section entitled What Must Every ASF Release Contain? as well as the informational page What We Sign. The following is a non-normative set of guidelines.

  1. You MUST make sure each of the signatures matches. As noted in the informational page What We Sign, if you don't have the signer's key in your web of trust the output of the verify command will point this out. You should refer to it for guidance. For example, using gpg and taking a fictional source artifact:

    $ cd
    $ gpg --verify apache-yetus-0.7.0-src.tar.gz.asc apache-yetus-0.7.0-src.tar.gz
    gpg: Signature made Fri Dec 11 11:50:56 2015 CST using RSA key ID 0D80DB7C
    gpg: Good signature from "Sean Busbey (CODE SIGNING KEY) <>"
  2. You MUST make sure the provided hashes match the provided artifact.

    $ gpg --print-mds apache-yetus-0.7.0-src.tar.gz >apache-yetus-0.7.0-src.tar.gz.my_mds
    $ diff apache-yetus-0.7.0-src.tar.gz.mds apache-yetus-0.7.0-src.tar.gz.my_mds
    $ shasum -a 512 apache-yetus-0.7.0-src.tar.gz >apache-yetus-0.7.0-src.tar.gz.my_sha512
    $ diff apache-yetus-0.7.0-src.tar.gz.sha512 apache-yetus-0.7.0-src.tar.gz.my_sha512
  3. You MUST make sure artifacts abide by the ASF Licensing Policy. You should read through the ASF Licensing Policy, especially if your vote will be binding. As a quick guide:
  4. You SHOULD make sure the source release artifact corresponds to the referenced commit hash in the [VOTE] thread. (This ASF policy is currently in DRAFT status.) The release tag is how we'll provide long-term provenance information for our downstream users. Since the release's source code artifact will be the canonical representation of the release we vote on, it is essential that it matches the contents of the version control system's tag. Given our example above, you can check this with recursive diff.

    $ mkdir apache-yetus-0.7.0-src_unpack
    $ tar -C apache-yetus-0.7.0-src_unpack -xzf apache-yetus-0.7.0-src.tar.gz
    $ git clone --single-branch --depth=1 --branch YETUS-585 '' apache-yetus-0.7.0-RC1-tag
    $ diff -r apache-yetus-0.7.0-RC1-tag apache-yetus-0.7.0-src_unpack/yetus-project-0.7.0
    $ echo $?
  5. You MUST make sure any non-source artifacts can be derived from the source artifact. Since the source artifact is the canonical representation of our release, any other artifacts we distribute must be just for the convenience of our downstream users. As such, one must be able to derive them from the source artifact. Currently, you can generate all of the artifacts we distribute for convenience using the same commands used to create the release artifacts.

    $ mkdir apache-yetus-0.7.0-src_unpack
    $ tar -C apache-yetus-0.7.0-src_unpack -xzf apache-yetus-0.7.0-src.tar.gz
    $ cd apache-yetus-0.7.0-src_unpack/yetus-project-0.7.0
    $ mvn clean install

This will create a yetus-dist/target/ directory that contains the tarball binary distribution files.

If you've gone through all of the ASF required checks, you'll already have made use of both the shelldocs and releasedocmaker components and confirmed that the compilable components successfully compile.

  1. Test Precommit. The smart-apply-patch and test-patch scripts don't get flexed as a part of the above candidate verification. If you have a downstream project you regularly use, it should suffice to attempt local verification of a contribution. If that project happens to be an ASF project with an example personality, this should be as simple as finding an issue in patch-available status.

        $ cd path/to/my/repo/for/hbase
        $ /some/path/to/the/unpacked/candidate/bin/test-patch --project=hbase HBASE-1772
        -1 overall
        | Vote |       Subsystem |  Runtime   | Comment
        |   0  |         reexec  |  0m 0s     | Docker mode activated.
        |  +1  |      hbaseanti  |  0m 0s     | Patch does not have any anti-patterns.
        |  +1  |        @\author  |  0m 0s     | The patch does not contain any @\author
        |      |                 |            | tags.
        |  +1  |     test4tests  |  0m 0s     | The patch appears to include 2 new or
        |      |                 |            | modified test files.
        |  +1  |     mvninstall  |  4m 41s    | master passed
        |  +1  |        compile  |  1m 4s     | master passed with JDK v1.8.0_72
        |  +1  |        compile  |  0m 57s    | master passed with JDK v1.7.0_95
        |  +1  |     checkstyle  |  0m 36s    | master passed
        |  +1  |     mvneclipse  |  0m 35s    | master passed
        |  -1  |       findbugs  |  1m 6s     | hbase-client in master has 19 extant
        |      |                 |            | Findbugs warnings.
        |  -1  |       findbugs  |  2m 8s     | hbase-server in master has 84 extant
        |      |                 |            | Findbugs warnings.
        |  -1  |        javadoc  |  0m 23s    | hbase-client in master failed with JDK
        |      |                 |            | v1.8.0_72.
        |  -1  |        javadoc  |  0m 34s    | hbase-server in master failed with JDK
        |      |                 |            | v1.8.0_72.
        |  +1  |        javadoc  |  0m 57s    | master passed with JDK v1.7.0_95
        |  +1  |     mvninstall  |  1m 3s     | the patch passed
        |  +1  |        compile  |  0m 59s    | the patch passed with JDK v1.8.0_72
        |  +1  |          javac  |  0m 59s    | the patch passed
        |  +1  |        compile  |  0m 59s    | the patch passed with JDK v1.7.0_95
        |  +1  |          javac  |  0m 59s    | the patch passed
        |  +1  |     checkstyle  |  0m 32s    | the patch passed
        |  +1  |     mvneclipse  |  0m 28s    | the patch passed
        |  +1  |     whitespace  |  0m 0s     | Patch has no whitespace issues.
        |  +1  |    hadoopcheck  |  4m 28s    | Patch does not cause any errors with
        |      |                 |            | Hadoop 2.4.1 2.5.2 2.6.0.
        |  +1  |       findbugs  |  3m 37s    | the patch passed
        |  -1  |        javadoc  |  0m 24s    | hbase-client in the patch failed with
        |      |                 |            | JDK v1.8.0_72.
        |  -1  |        javadoc  |  0m 36s    | hbase-server in the patch failed with
        |      |                 |            | JDK v1.8.0_72.
        |  +1  |        javadoc  |  1m 2s     | the patch passed with JDK v1.7.0_95
        |  +1  |           unit  |  1m 23s    | hbase-client in the patch passed with
        |      |                 |            | JDK v1.8.0_72.
        |  -1  |           unit  |  67m 12s   | hbase-server in the patch failed with
        |      |                 |            | JDK v1.8.0_72.
        |  +1  |           unit  |  1m 28s    | hbase-client in the patch passed with
        |      |                 |            | JDK v1.7.0_95.
        |  -1  |           unit  |  66m 16s   | hbase-server in the patch failed with
        |      |                 |            | JDK v1.7.0_95.
        |  +1  |     asflicense  |  0m 30s    | Patch does not generate ASF License
        |      |                 |            | warnings.
        |      |                 |  177m 13s  |
                                    Reason | Tests
         JDK v1.8.0_72 Failed junit tests  |  hadoop.hbase.client.TestMultiParallel
         JDK v1.7.0_95 Failed junit tests  |  hadoop.hbase.client.TestMultiParallel
        || Subsystem || Report/Notes ||
        | Docker | Client=1.9.1 Server=1.9.1 Image:yetus/hbase:date2016-02-11 |
        | JIRA Patch URL | |
        | JIRA Issue | HBASE-15198 |
        | Optional Tests |  asflicense  javac  javadoc  unit  findbugs  hadoopcheck  hbaseanti  checkstyle  compile  |
        | uname | Linux 67e02eb9aeea 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux |
        | Build tool | maven |
        | Personality | /testptch/patchprocess/precommit/personality/ |
        | git revision | master / 81a6fff |
        | findbugs | v2.0.1 |
        | findbugs | /testptch/patchprocess/branch-findbugs-hbase-client-warnings.html |
        | findbugs | /testptch/patchprocess/branch-findbugs-hbase-server-warnings.html |
        | javadoc | /testptch/patchprocess/branch-javadoc-hbase-client-jdk1.8.0_72.txt |
        | javadoc | /testptch/patchprocess/branch-javadoc-hbase-server-jdk1.8.0_72.txt |
        | javadoc | /testptch/patchprocess/patch-javadoc-hbase-client-jdk1.8.0_72.txt |
        | javadoc | /testptch/patchprocess/patch-javadoc-hbase-server-jdk1.8.0_72.txt |
        | unit | /testptch/patchprocess/patch-unit-hbase-server-jdk1.8.0_72.txt |
        | unit | /testptch/patchprocess/patch-unit-hbase-server-jdk1.7.0_95.txt |
        | unit test logs |  /testptch/patchprocess/patch-unit-hbase-server-jdk1.8.0_72.txt /testptch/patchprocess/patch-unit-hbase-server-jdk1.7.0_95.txt |
        | modules | C: hbase-client hbase-server U: . |
        | Powered by | Apache Yetus 0.7.0 |
  2. Test Audience Annotations. If you have a downstream project that relies on the audience annotations project, you should be able to install the jars locally and test with the updated version.

     $ mkdir apache-yetus-0.7.0-src_unpack
     $ tar -C apache-yetus-0.7.0-src_unpack -xzf apache-yetus-0.7.0-src.tar.gz
     $ cd apache-yetus-0.7.0-src_unpack/yetus-0.7.0
     $ mvn --batch-mode install
     [INFO] ------------------------------------------------------------------------
     [INFO] ------------------------------------------------------------------------
     [INFO] Total time: 3.539 s
     [INFO] Finished at: 2016-02-13T02:12:39-06:00
     [INFO] Final Memory: 14M/160M
     [INFO] ------------------------------------------------------------------------
     $ cd path/to/your/project
     $ vim pom.xml # edit version to be e.g. 0.7.0
     $ mvn verify
     [INFO] ------------------------------------------------------------------------
     [INFO] ------------------------------------------------------------------------
     [INFO] Total time: 7.539 m
     [INFO] Finished at: 2016-02-13T02:13:39-06:00
     [INFO] Final Memory: 14M/160M
     [INFO] ------------------------------------------------------------------------


Once a release candidate obtains majority approval from the PMC, there are several final maintenance tasks you must perform to close out the release.

  1. Create shortcut links to the vote thread (e.g., and the result (e.g., that point to the archives on Be aware that it may take several hours for the archive to get the posts that need to be referenced.
  2. Produce a signed release tag. You should create a signed tag and push it to the asf repo. The tag's message should include ASF-shortened links to the vote and results. It should be named 'rel/version' so that it will be immutable due to ASF infra's git configuration. Presuming we're working on the 0.7.0 release and the RC1 example above has passed:

     $ git config --global user.signingkey <your-key-id> # if you've never configured
     $ git tag --sign rel/0.7.0 1e8f4588906a51317207092bd97b35687f2e3fa3  Example commit message:
     YETUS-XXX. tag Apache Yetus 0.7.0 release.
     vote thread:
     results:  Then push:
     $ git push origin rel/0.7.0
  3. Add the release to the ASF reporter tool. To make our project reports for the ASF Board easier, you should include the release in the Apache Committee Report Helper website. Be sure to use the date release artifacts first were pushed to the distribution area, which should be the same release date as in JIRA. Note that this website is only available to PMC members. If you are not yet in the PMC, please ask them to add the release information. Additionally, it will not let you set a future date.
  4. Move release artifacts to the distribution area. The release officially happens once the artifacts are pushed to the ASF distribution servers. From this server, the artifacts will automatically be copied to the long-term archive as well as the various mirrors that will be used by downstream users. These must be exactly the artifacts from the RC that passed. Please note that currently, only Yetus PMC members have write access to this space. If you are not yet on the PMC, please ask the PMC to post the artifacts.

     $ svn co yetus-dist-release
     $ cd yetus-dist-release
     $ mkdir 0.7.0
     $ cp path/to/yetus-dist-dev/0.7.0-RC1/* 0.7.0
     $ svn add 0.7.0
     $ svn commit -m "Publish Apache Yetus 0.7.0"  It may take up to 24 hours for the artifacts to make their way to the various mirrors. You should not announce the release until after this period.
  5. Remove candidates from the staging area. Once you have moved the artifacts into the distribution area, they no longer need to be in the staging area and should be cleaned up as a courtesy to future release managers.

     $ svn co yetus-dist-dev
     $ cd yetus-dist-dev
     $ svn rm 0.7.0-RC*
     D         0.7.0-RC1/apache-yetus-0.7.0-src.tar.gz.sha512
     D         0.7.0-RC1/apache-yetus-0.7.0-bin.tar.gz.asc
     D         0.7.0-RC1/
     D         0.7.0-RC1/
     D         0.7.0-RC1/
     D         0.7.0-RC1/apache-yetus-0.7.0-src.tar.gz
     D         0.7.0-RC1/
     D         0.7.0-RC1/apache-yetus-0.7.0-bin.tar.gz.mds
     D         0.7.0-RC1/apache-yetus-0.7.0-bin.tar.gz.sha512
     D         0.7.0-RC1/apache-yetus-0.7.0-src.tar.gz.asc
     D         0.7.0-RC1/
     D         0.7.0-RC1/
     D         0.7.0-RC1/
     D         0.7.0-RC1/
     D         0.7.0-RC1/apache-yetus-0.7.0-bin.tar.gz
     D         0.7.0-RC1/apache-yetus-0.7.0-src.tar.gz.mds
     D         0.7.0-RC1
     $ svn commit -m "cleaning up release candidates from Apache Yetus 0.7.0 release process."
     Deleting       0.7.0-RC1
     Committed revision 1772.
  6. Resolve release issue; it should be marked as "fixed."
  7. Go to the ASF repository and click 'Release' to put the RC Maven artifacts into the release repository.
  8. Mark JIRA version as released. Browse to the project version management page for the YETUS JIRA tracker. Mouse over the version you are managing, click on the gear in the far right and select Release.
  9. Delete staging branch. Now that there is an immutable tag for the release, all commits leading up to that release will be maintained by git. Should we need a future maintenance release after this version, we can reestablish the branch based off of the release tag.
    $ git push origin :YETUS-XXX
  10. Update the Mac OS X Homebrew Formula:

    $ vim Formula/yetus.rb
    $ # change URL point to the new version
    $ # update the sha256. e.g., shasum -a 256 bin.gz
    $ # test the formula:
    $ brew install --build-from-source Formula/yetus.rb
     # or if you already have it installed:
    $ brew upgrade --build-from-source Formula/yetus.rb
  11. Update the documentation in the git master branch for the new release. Remove the oldest release and add the latest.

    $ cd asf-site-src
    $ # Add the release to the releases data file
    $ vim data/versions.yml
    $ vim data/htaccess.yml
    $ vim pom.xml
    $ # add the two stanzas
    $ git add -p
    $ git add asf-site-src/pom.xml
    $ git commit
    • Example commit message:
    YETUS-XXX. add release 0.7.0.
    - list in releases
    - remove 0.4.0, add 0.7.0 to pom.xml
  12. You should then post this patch for review. Once you've gotten feedback, it's fine to push the patch to the ASF source repo immediately so long as the updated website is not published.
  13. Publish website updates. After the 24 hour window needed for the release artifacts to make their way to the variety of mirrors, you should render the website and publish it using the instructions found in Maintaining the Yetus Website.
  14. Verify that and download the newly released version.
  15. Remove old releases from the distribution area. The ASF distribution area should only contain the most recent release for actively developed branches If your release is a maintenance release, delete the prior release. If your release marks the end of maintenance for an earlier minor or major release line, you should delete those versions from the distribution area.
  16. Draft an announcement email. The announcement email should briefly describe our project and provide links to our artifacts and documentation. For example,
    Subject: [ANNOUNCE] Apache Yetus 0.7.0 release

     Apache Yetus 0.7.0 Released!
     The Apache Software Foundation and the Apache Yetus Project are pleased to
     announce the release of version 0.7.0 of Apache Yetus.
     Apache Yetus is a collection of libraries and tools that enable contribution
     and release processes for software projects.  It provides a robust system
     for automatically checking new contributions against a variety of community
     accepted requirements, the means to document a well defined supported
     interface for downstream projects, and tools to help release managers
     generate release documentation based on the information provided by
     community issue trackers and source repositories.
     This version marks the latest minor release representing the community's
     work over the last X months.
     To download, please choose a mirror by visiting:
     The relevant checksums files are available at:
     Project member signature keys can be found at
     PGP signatures are available at:
     The list of changes included in this release and release notes can be browsed at:
     Documentation for this release is at:
     On behalf of the Apache Yetus team, thanks to everyone who helped with this
     Questions, comments, and bug reports are always welcome on
     Meg Smith
     Apache Yetus PMC  If you'd like feedback on the draft, feel free to post it for review on your release issue.
  17. Send announcement emails. After the 24 hour window needed for the release artifacts to make their way to the variety of mirrors, you should send the announcement email. The email should come from your email address and at a minimum should go to the list. For details see the ASF Release Policy section How Should Releases Be Announced?. Additionally, you may want to send the announcement to the development lists of downstream projects we know are using Yetus components.
  18. Send tweet. Once the message to has made it to the public archive, you should draft a tweet with a link to the announcement. You should use the ASF link shortener and a descriptive name. For example, the 0.7.0 release could use

     Apache Yetus 0.7.0 has been released:
  This tweet should come from the official [@ApacheYetus]( account. Currently, only PMC members have access to it. If you are not yet on the PMC, please ask for the PMC to post the tweet once your email is available in the archives.