Skip to content

Managing a Release

Jump to bottom Edit New page
Sean Busbey edited this page Oct 11, 2019 · 35 revisions

⚠️ This page is a guide for folks working directly on the YCSB project. It is unlikely to be of use if you are a downstream user of YCSB. That said, we love it when downstream users decide to pitch in on the project. Let us know if part of this could be clearer.

This document is meant to provide guidance for collaborator who have taken on the responsibility of generating a release.

In order, we're going to cover

Assumptions

This document has several assumptions built into it. We'll attempt to cover them briefly to reduce stumbling blocks.

  • Release managers have 'collaborator' status on the YCSB repo
  • Git commands all start at the root of a local working copy of the YCSB repo
  • The remote YCSB repo is named 'origin' in your local working copy
  • The in-progress release you are managing is referred to as version; you should always replace this with an actual version string i.e. 0.3.0. In bash examples, this version will be referred to with the placeholder $VERSION
  • Your release version was determined prior to this process inline with our versioning policy
  • Your local development environment is correct
    • We presume Linux for release builds
    • We require JDK 8 for release builds
    • We require Maven 3.2+ for release builds

Set Release Gates

Before starting the release process, you should have a set of goals for the release to meet. At a minimum you should maintain some minimum verified code quality:

  • the generated binary artifacts should run on both Linux and Windows (presuming a valid environment)
  • at least three of the datastore bindings should be verified as working
  • someone needs to run mvn org.apache.rat:apache-rat-plugin:check to verify licensing

Additionally, you should review issues/PRs that have been closed since the last release. If any of them include major restructuring or new functionality you should consider requiring that they are tested before a release can happen. Drawing the line between required testing and simply labeling a feature as experimental is a judgement call. Changes to how we measure throughput or latency, especially by default, should certainly require testing. An additional export format for measurements has relatively little risk for downstream users if it is labeled experimental.

Create Release Issue

Once you know what you'd like covered in the release, create a new issue with the title "Release version version". The conversation on this issue will serve as the central hub of activity related to the release: you'll post links here to release candidates as they're created and testers will post their results.

It's important to stay responsive on this thread. If an issue is discovered that you believe needs to be in the final release, provide a link to it and note that it is a blocker. If you think an issue can be sufficiently mitigated try to get consensus on having it listed as a known issue instead.

On the initial issue description, you should include your expected release gating criteria and a brief timeline. Essentially, let folks know when you will create the release staging branch and when you'd like to see all of the testing completed.

Create Release Staging Branch

Releases are driven out of a dedicated branch so that unrelated development can continue in the master branch. The release staging branch marks feature freeze for the release; no additional improvements or enhancements should go into the branch. One important exception to this rule is the addition of a README.md for datastore bindings. While documentation changes would not normally be considered an improvement, this particular document causes our build to generate a convenience binary specific to that datastore. You should accept (and encourage!) these changes in a release branch, especially if they are paired with test results.

Creating a release staging branch involves a couple of git commands and updating version numbers. The next version number will generally be the next minor release number (for more info see our versioning policy).

  #!/bin/bash
  #
  # Script to create a new staging branch.  This assumes that the master
  # branch is checked out and the working directory is clean.
  #
  # To confirm changes before checking them in, replace the -A option
  # to "git add" below with -p.
  #

  # Update the following two variables before running this script.
  # (Hint: VERSION is the version you are currently working to release)
  VERSION=0.3.0
  NEXT_VERSION=0.4.0

  # Create the new branch.
  git branch ${VERSION}-staging

  # Update the version string to the next version number.
  FROM=${VERSION}-SNAPSHOT
  TO=${NEXT_VERSION}-SNAPSHOT

  FILES="`grep -rl -- ${VERSION}-SNAPSHOT *`"

  echo "$FILES" | xargs sed -i "s/$FROM/$TO/"
  git add -A
  git commit -m "[version] update master to $TO."

  git push origin ${VERSION}-staging master

If any changes are merged into master before you attempt to push the update version numbers you'll receive an error like this:

  $ git push origin _version_-staging master
To git@github.com:brianfrankcooper/YCSB.git
 ! [rejected]        master -> master (non-fast-forward)
error: failed to push some refs to 'git@github.com:brianfrankcooper/YCSB.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Merge the remote changes (e.g. 'git pull')
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

To fix this, you should fetch new changes and rebase your master branch before pushing.

  $ git fetch origin
remote: Counting objects: 126, done.
remote: Compressing objects: 100% (39/39), done.
remote: Total 126 (delta 33), reused 19 (delta 19), pack-reused 42
Receiving objects: 100% (126/126), 20.27 KiB, done.
Resolving deltas: 100% (33/33), completed with 5 local objects.
From github.com:brianfrankcooper/YCSB
   35720bb..2c83327  master     -> origin/master
  $ git rebase origin/master
First, rewinding head to replay your work on top of it...
Applying: [version] update master to ${NEXT_VERSION}-SNAPSHOT.
  $ git push origin master

Note that these additional changes will not be present in your release staging branch. If you wish to include them, delete the branch and start over.

Once you create the release staging branch it will be up to you to ensure any changes you want included in the release are cherry-picked back to this branch. We'll cover the mechanics of that later in Collect Test Feedback.

Generate a Release Candidate

Testing in the release conversation should always be done on a release candidate so that everyone is operating on the same version of the code. An accessible release candidate reduces the burden on the volunteers we ask to do our release vetting. At the same time, we don't want downstream users relying on these candidates since they have not, by definition, been tested yet. To achieve a balance between these two opposing goals we make use of GitHub's pre-release markings. Additionally, we don't create any convenience binaries for release candidates.

Before tagging a release candidate, you will need to update the version in the repo. In this example, we'll use the placeholder ${RC_NUMBER} for the current release candidate, i.e. RC_NUMBER="RC1" for the first release candidate.

  #!/bin/bash
  #
  # Script to help generate a new release candidate.  This assumes that
  # the master branch is checked out and the working directory is clean.
  #
  # To confirm changes before checking them in, replace the -A option
  # to "git add" below with -p.
  #

  # Update the following two variables before running this script.
  VERSION=0.3.0
  RC_NUM=2

  RC_NUMBER=RC${RC_NUM}
  NEXT_RC_NUMBER=RC$((${RC_NUM} + 1))
  RC_VERSION=${VERSION}-${RC_NUMBER}

  git checkout ${VERSION}-staging

  # Modify version string from SNAPSHOT to RC.
  test $RC_NUM = 1 && FROM=${VERSION}-SNAPSHOT || FROM=${RC_VERSION}-SNAPSHOT
  TO=$RC_VERSION

  FILES="`grep -rl -- -SNAPSHOT *`"

  echo "$FILES" | xargs sed -i "s/$FROM/$TO/"
  git add -A
  git commit -m "[release] mark ${VERSION} ${RC_NUMBER}"

  # Now create a tag that we can reference on GitHub.
  git tag $RC_VERSION

  # Modify version string from RC to the next RC snapshot.  Now fixes
  # that come in during testing can be picked back here for files that
  # need updating.
  FROM=$RC_VERSION
  TO=${VERSION}-${NEXT_RC_NUMBER}-SNAPSHOT
  echo "$FILES" | xargs sed -i "s/$FROM/$TO/"
  git add -A
  git commit -m "[release] update version for ${NEXT_RC_NUMBER}"

  # Finally push all of this up to GitHub.
  git push origin ${VERSION}-staging $RC_VERSION

Now the YCSB repo should have all of your changes available on GitHub.

  1. Visit the "Draft new release" page
  2. In the "Tag version" field, enter the tag you created above, ${VERSION}-${RC_NUMBER}
  3. Ensure the @ Target branch is the staging branch from above, ${VERSION}-staging
  4. Fill in a title of "version Release Candidate rc-number", e.g. "0.3.0 Release Candidate 1"
  5. Fill in the description. Give folks a pointer to the release issue. Be sure to include a warning that this is an RC and not for downstream use. If this is the first RC, it will help your later release notes if you can describe what's different since the last release. If this is a follow on RC, you should include what has changed since the last RC.
  6. Be sure to check the "this is a pre-release" box.

Here's an example template for a Release Candidate description

UPPERCASE WARNING: THIS IS A RELEASE CANDIDATE AND IS NOT INTENDED FOR DOWNSTREAM USE.

This source is a candidate for release version. Please see #release issue for testing instructions and where to leave your feedback.

Compared to the previous release, this candidate includes

  • some list
  • of changes

When you've published a particular release candidate, you should add a brief note to the release issue pointing to it and asking folks who are testing to use it from then on.

Collect Testing Feedback

As folks work to verify a release candidate, they'll open PRs for problems they encounter and hopefully those PRs will result in fixes on the master branch. As the Release Manager, you'll need to ensure that any of these fixes needed for the release make it into the staging branch. You accomplish this by using the git cherry-pick command to apply individual patches from the master branch on the release staging branch.

As a simple example, consider the fix for #319 in the 0.2.0 release line. This was a problem with the scan operation in the Tarantool datastore binding that was discovered between RC2 and RC3.

You can use something similar to git log --pretty=format:"%h %s (%cr)" --graph to get a view of commits and merges.

Here's the fix landing in master:

*   ecadf1f - (HEAD, master) Merge pull request #323 from bigbes/master (3 weeks ago)
|\
| * 25e0ec8 - Issue #319: [tarantool] Error on scan operation and replace problems (3 weeks ago)
|/
*   45631e8 - Merge pull request #304 from gkamat/issue-278 (3 weeks ago)

And here's how master compared to the 0.2.0-staging branch at the time:

* f2e333b - (0.2.0-staging) [hbase] Update to commit 80b74a94359179a60032289e5a115dec1bf6ee8b. Pass original exception back when issues discovered during initialization. (3 weeks ago)
* 1e437eb - [hbase] Verify that the table exists during DB binding initialization (3 weeks ago)
* 31b86d4 - [mongodb] update parameter for connection url to match previous behavior and docs. (3 weeks ago)
* f3aac41 - [release] update version for RC3 (4 weeks ago)
* dde1fb8 - (0.2.0-RC2) [release] mark 0.2.0 RC2 (4 weeks ago)
* 643f007 - [scripts] Include only the binding-specific jars and conf directory in the classpath, rather than all of them. (4 weeks ago)
* dc794ca - [scripts] Add only the conf directory for the relevant binding to the classpath, rather than all of them. (4 weeks ago)
* fb9c41a - [release] update version for RC2 (4 weeks ago)
* 7bc13d8 - (0.2.0-RC1) [release] mark 0.2.0 RC1 (4 weeks ago)
| *   ecadf1f - (HEAD, master) Merge pull request #323 from bigbes/master (3 weeks ago)
| |\
| | * 25e0ec8 - Issue #319: [tarantool] Error on scan operation and replace problems (3 weeks ago)
| |/
| *   45631e8 - Merge pull request #304 from gkamat/issue-278 (3 weeks ago)
| |\
| | * 1c3db41 - [hbase] Update to commit 80b74a94359179a60032289e5a115dec1bf6ee8b. Pass original exception back when issues discovered during initialization. (4 weeks ago)
| | *   6d85b13 - Merge remote-tracking branch 'upstream/master' into issue-278 (4 weeks ago)
| | |\
| | * \   2517e26 - Merge remote-tracking branch 'upstream/master' into issue-278 (4 weeks ago)
| | |\ \
| |_|/ /
|/| | |
| | * |   36194ed - Merge branch 'issue-278' of https://github.com/gkamat/YCSB into issue-278 (4 weeks ago)
| | |\ \
| | | * | d59ce9b - [hbase] Verify that the table exists during DB binding initialization and bail out if not found.  If this is not checked here, the workload will continue running and generating errors
| | * | | 80b74a9 - [hbase] Verify that the table exists during DB binding initialization and bail out if not found.  If this is not checked here, the workload will continue running and generating errors
| | |/ /
| * | |   9bc02d2 - Merge pull request #301 from saggarsunil/master (3 weeks ago)
| |\ \ \
| | * \ \   ba66be6 - Merge branch 'master' of https://github.com/saggarsunil/YCSB (4 weeks ago)
| | |\ \ \
| | | * \ \   c4e3943 - Merge branch 'master' of https://github.com/saggarsunil/YCSB (4 weeks ago)
| | | |\ \ \
| | * | \ \ \   ea22a7b - Merge branch 'master' of https://github.com/saggarsunil/YCSB (4 weeks ago)
| | |\ \ \ \ \
| | | |/ / / /
| | |/| / / /
| | | |/ / /
| | | * | | 42b39f5 - Changes: 1. mongodb configuration parameter bug (mongodb.url) 2. README file change 3. Some cleanup. Default DB is 'ycsb' (4 weeks ago)
| | * | | | 4cfd40f - [mongodb] update parameter for connection url to match previous behavior and docs. Changes: 1. mongodb configuration parameter bug (mongodb.url) 2. README file change 3. Some cleanup
| | |/ / /
| * | | |   7dcbb32 - Merge pull request #305 from gkamat/issue_302 (4 weeks ago)
| |\ \ \ \
| | |_|_|/
| |/| | |
| | * | | 2559ce6 - [scripts] Include only the binding-specific jars and conf directory in the classpath, rather than all of them. (4 weeks ago)
| | * | |   be6c4d9 - Merge branch 'master' of https://github.com/brianfrankcooper/YCSB into issue_302 (4 weeks ago)
| | |\ \ \
| | * | | | ced4306 - [scripts] Add only the conf directory for the relevant binding to the classpath, rather than all of them. (4 weeks ago)
| | | |_|/
| | |/| |
| * | | | 9c80044 - [version] update master to 0.3.0-SNAPSHOT. (4 weeks ago)
|/ / / /
* | | |   700b71c - Merge pull request #307 from busbey/issue-297 (4 weeks ago)

To get this same fix in our release staging branch, we can ignore the merge and just use cherry-pick on the fix itself (You may need to first issue a git fetch to grab in the recent history.)

  $ git cherry-pick 25e0ec8
[0.2.0-staging 7de528c] Issue #319: [tarantool] Error on scan operation and replace problems
 Author: bigbes <bigbes@gmail.com>
 1 file changed, 7 insertions(+), 5 deletions(-)

Now you can see the comparison of the branches after:

* 44330fb - (HEAD, 0.2.0-staging) Issue #319: [tarantool] Error on scan operation and replace problems (47 seconds ago)
* f2e333b - [hbase] Update to commit 80b74a94359179a60032289e5a115dec1bf6ee8b. Pass original exception back when issues discovered during initialization. (3 weeks ago)
* 1e437eb - [hbase] Verify that the table exists during DB binding initialization (3 weeks ago)
* 31b86d4 - [mongodb] update parameter for connection url to match previous behavior and docs. (3 weeks ago)
* f3aac41 - [release] update version for RC3 (4 weeks ago)
* dde1fb8 - (0.2.0-RC2) [release] mark 0.2.0 RC2 (4 weeks ago)
* 643f007 - [scripts] Include only the binding-specific jars and conf directory in the classpath, rather than all of them. (4 weeks ago)
* dc794ca - [scripts] Add only the conf directory for the relevant binding to the classpath, rather than all of them. (4 weeks ago)
* fb9c41a - [release] update version for RC2 (4 weeks ago)
* 7bc13d8 - (0.2.0-RC1) [release] mark 0.2.0 RC1 (4 weeks ago)
| *   ecadf1f - (master) Merge pull request #323 from bigbes/master (3 weeks ago)
| |\
| | * 25e0ec8 - Issue #319: [tarantool] Error on scan operation and replace problems (3 weeks ago)
| |/
| *   45631e8 - Merge pull request #304 from gkamat/issue-278 (3 weeks ago)
| |\
| | * 1c3db41 - [hbase] Update to commit 80b74a94359179a60032289e5a115dec1bf6ee8b. Pass original exception back when issues discovered during initialization. (4 weeks ago)
| | *   6d85b13 - Merge remote-tracking branch 'upstream/master' into issue-278 (4 weeks ago)
| | |\
| | * \   2517e26 - Merge remote-tracking branch 'upstream/master' into issue-278 (4 weeks ago)
| | |\ \
| |_|/ /
|/| | |
| | * |   36194ed - Merge branch 'issue-278' of https://github.com/gkamat/YCSB into issue-278 (4 weeks ago)
| | |\ \
| | | * | d59ce9b - [hbase] Verify that the table exists during DB binding initialization and bail out if not found.  If this is not checked here, the workload will continue running and generating errors
| | * | | 80b74a9 - [hbase] Verify that the table exists during DB binding initialization and bail out if not found.  If this is not checked here, the workload will continue running and generating errors
| | |/ /
| * | |   9bc02d2 - Merge pull request #301 from saggarsunil/master (3 weeks ago)
| |\ \ \
| | * \ \   ba66be6 - Merge branch 'master' of https://github.com/saggarsunil/YCSB (4 weeks ago)
| | |\ \ \
| | | * \ \   c4e3943 - Merge branch 'master' of https://github.com/saggarsunil/YCSB (4 weeks ago)
| | | |\ \ \
| | * | \ \ \   ea22a7b - Merge branch 'master' of https://github.com/saggarsunil/YCSB (4 weeks ago)
| | |\ \ \ \ \
| | | |/ / / /
| | |/| / / /
| | | |/ / /
| | | * | | 42b39f5 - Changes: 1. mongodb configuration parameter bug (mongodb.url) 2. README file change 3. Some cleanup. Default DB is 'ycsb' (4 weeks ago)
| | * | | | 4cfd40f - [mongodb] update parameter for connection url to match previous behavior and docs. Changes: 1. mongodb configuration parameter bug (mongodb.url) 2. README file change 3. Some cleanup
| | |/ / /
| * | | |   7dcbb32 - Merge pull request #305 from gkamat/issue_302 (4 weeks ago)
| |\ \ \ \
| | |_|_|/
| |/| | |
| | * | | 2559ce6 - [scripts] Include only the binding-specific jars and conf directory in the classpath, rather than all of them. (4 weeks ago)
| | * | |   be6c4d9 - Merge branch 'master' of https://github.com/brianfrankcooper/YCSB into issue_302 (4 weeks ago)
| | |\ \ \
| | * | | | ced4306 - [scripts] Add only the conf directory for the relevant binding to the classpath, rather than all of them. (4 weeks ago)
| | | |_|/
| | |/| |
| * | | | 9c80044 - [version] update master to 0.3.0-SNAPSHOT. (4 weeks ago)
|/ / / /
* | | |   700b71c - Merge pull request #307 from busbey/issue-297 (4 weeks ago)

Since the release staging branch doesn't maintain the git history for the original fix, it's important to make sure the commit message is good. If the above fix hadn't included an issue number, for example, then we can edit the commit message while cherry-picking to improve it.

  $ git cherry-pick --edit 25e0ec8

For example, in the commint for #319 we'd prefer to have the issue number after the first line.

[tarantool] Error on scan operation and replace problems

fixes #319

In some cases, you'll need to cherry pick multiple commits. The main caveat in that case is to make sure you pick them in the same order they were originally applied (bottom up if you're looking at the git log). You can use something like git cherry-pick A^..B where A is older than B, which will include the range of commits from A to B inclusive.

If the fix you need came from a feature branch with multiple merges, or if any of those merges involved substantive changes you'll need to use some more advanced git features. Ask for help on the release issue and someone will help out. (and hopefully update this document!)

For more information on git cherry-pick, check out the cherry-pick section of Think Like a Git.

Before pushing your cherry picked changes to GitHub, ensure the build still passes and minimally that the basic binding works.

$ mvn clean package
...SNIP...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:14 min
[INFO] Finished at: Mon Jul 06 00:34:07 CDT 2015
[INFO] Final Memory: 81M/756M
[INFO] ------------------------------------------------------------------------
$ bin/ycsb load basic -P workloads/workloada -p recordcount=4
...SNIP...

You should see four INSERT statements, followed by some stats prefixed with [OVERALL], [CLEANUP], and [INSERT]. There should be no errors.

Stage Release Notes

Before ultimately publishing the release you will need to write up a short document that lets downstream users know what they ought to watch out for when upgrading. This is an important chance to minimize the headache (and our future support!) by warning them of incompatibilities or known problems.

Things to make sure you include:

  • Incompatible changes, especially if a datastore binding was removed, we changed how the tool is run, or comparative analysis with prior versions is invalid.
  • Known limitations of the current datastore bindings with particular datastore versions, particular workloads, or on particular operating systems.
  • Datastore bindings. Call out new ones, but be sure to list every datastore binding that is present in the binary distribution. Those that were tested in the release thread should be called out at such, and should have links to their project pages. Those that weren't tested should still be listed, but the lack of testing should be noted and no links made.

Things to leave out:

  • Changes that are only internal to the project, e.g. build tooling that doesn't impact the final binary artifacts

The easiest way to write up the release note is to start with the one for the prior version:

Release notes are ultimately posted in Markdown. To create a draft, you can use GitHub Gists or any other pastebin. It's best if you can mark them "private" or "secret"—essentially anything that makes the draft only visible to those with the link. This should help cut down on searchers accidentally ending up at the draft prior to the final release.

Once you have a draft, post it to the release thread and wait for someone to give it a 👍.

Publish Release

Once you have consensus that the release is ready and an appropriate set of release notes, it's time to publish the release. This process will involve one last round of version updates, building the convenience artifacts, and using GitHub's release publishing feature.

Finalize Version

Our staging branch should still be set to the version for a potential new release candidate. Once you've decided candidates are no longer needed, you'll need to update to a finalized version.

In the example below, RC3 is the latest release candidate, while the staging directory is set up for the RC4 snapshot. Our goal here is to go from 0.3.0-RC4-SNAPSHOT to 0.3.0.

  #!/bin/bash
  #
  # Script to help finalize the release number.  This assumes that
  # the staging branch is checked out and the working directory is clean.
  #
  # To confirm changes before checking them in, replace the -A option
  # to "git add" below with -p.
  #

  # Update the following two variables before running this script.
  VERSION=0.3.0
  RC_NUM=4

  RC_NUMBER=RC${RC_NUM}
  RC_VERSION=${VERSION}-${RC_NUMBER}

  git checkout ${VERSION}-staging

  # Modify version string from RC SNAPSHOT to final.
  FROM=${RC_VERSION}-SNAPSHOT
  TO=$VERSION

  FILES="`grep -rl -- -SNAPSHOT *`"

  echo "$FILES" | xargs sed -i "s/$FROM/$TO/"
  git add -A
  git commit -m "[release] mark ${VERSION}"

  # Finally push all of this up to GitHub.
  git push origin ${VERSION}-staging

You should ensure you can properly build the convenience artifacts before tagging the branch and pushing it to GitHub.

Build Convenience Artifacts

First, make sure you have the local tools we'll use. Your maven will need to be 3.2+ and you JVM must be Java 8.

Use the mvn --version command to check your build tool versions. In the example below, we can see the maven version is 3.5.2 and Java is Oracle's JDK 1.8.0_161.

$ mvn -version
Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 2017-10-18T02:58:13-05:00)
Maven home: /usr/local/Cellar/maven/3.5.2/libexec
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.13.6", arch: "x86_64", family: "mac"

Additionally, you'll need to generate various digests of the convenience artifacts. The easiest way to handle this is to use gpg. You should ensure it includes support for SHA512.

Use the gpg --version command and look for the line that starts with "Hash":

$ gpg --version
gpg (GnuPG) 1.4.18
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
        CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

First, build the project using the Java 8 sdk you verified above.

$ mvn clean package
...SNIP...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:14 min
[INFO] Finished at: Mon Jul 06 00:34:07 CDT 2015
[INFO] Final Memory: 81M/756M
[INFO] ------------------------------------------------------------------------

Gather up all of the convenience artifacts that you'll eventually publish. This should include those for all tested datastore bindings applicable to this release. This will include the ones tested in the current release thread as well as those tested earlier that you believe are still valid for this release. Note that not all of the bindings tested may have artifacts.

# The "distribution" tarball is for the core YCSB module.  The others 
# comprise the set of tested bindings applicable for version 0.1l.0.
$ TARBALLS="
  distribution
  accumulo
  aerospike
  arangodb
  asynchbase
  couchbase2
  dynamodb
  elasticsearch
  geode
  googlebigtable
  googledatastore
  hbase098
  hbase10
  jdbc
  kudu
  memcached
  mongodb
  rados
  riak
  s3
  solr
  tarantool
"

$ for i in $TARBALLS; do \
      cp $i/target/*.tar.gz /some/path/to/a/ycsb-release-dist/ \
  done

$ ls -lh /some/path/to/a/ycsb-release-dist
total 366672
-rw-r--r--  1 busbey  staff   144M Aug  6 01:37 ycsb-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff    29M Aug  6 01:34 ycsb-hbase-binding-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff   4.2M Aug  6 01:34 ycsb-mongodb-binding-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff   2.0M Aug  6 01:34 ycsb-tarantool-binding-0.3.0.tar.gz
[...]

Finally, you will need to generate a file with digest hashes for each of these artifacts.

$ cd /some/path/to/a/ycsb-release-dist
$ for tarball in *.tar.gz; do gpg --print-mds "${tarball}" > "${tarball}.mds"; done
$ ls -lh
total 366704
-rw-r--r--  1 busbey  staff   144M Aug  6 01:37 ycsb-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff   930B Aug  6 01:49 ycsb-0.3.0.tar.gz.mds
-rw-r--r--  1 busbey  staff    29M Aug  6 01:34 ycsb-hbase-binding-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff   1.2K Aug  6 01:49 ycsb-hbase-binding-0.3.0.tar.gz.mds
-rw-r--r--  1 busbey  staff   4.2M Aug  6 01:34 ycsb-mongodb-binding-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff   1.3K Aug  6 01:49 ycsb-mongodb-binding-0.3.0.tar.gz.mds
-rw-r--r--  1 busbey  staff   2.0M Aug  6 01:34 ycsb-tarantool-binding-0.3.0.tar.gz
-rw-r--r--  1 busbey  staff   1.5K Aug  6 01:49 ycsb-tarantool-binding-0.3.0.tar.gz.mds
[...]

Each of the files ending in .mds should contain a variety of message digests.

e.g. for the primary binary distribution:

ycsb-0.3.0.tar.gz:    MD5 = 46 07 C6 D6 99 4B 62 19  47 93 F2 18 58 49 18 A6
ycsb-0.3.0.tar.gz:   SHA1 = E070 20B6 2707 3162 AED9  432E 25EB B7C7 4E2E 11D2
ycsb-0.3.0.tar.gz: RMD160 = B6B4 54B0 014E 4088 90A4  0ED2 828A 5298 43C6 E625
ycsb-0.3.0.tar.gz: SHA224 = 61195921 C96F33B8 07C8ACBA B42AC6BE 9684971B
                            84C7ABB2 8541FEEC
ycsb-0.3.0.tar.gz: SHA256 = E7CA1E5A BE9FA405 546734CB 6F9D9BCB 1AE575D7
                            E5D42503 08BC37E3 DEED3CE2
ycsb-0.3.0.tar.gz: SHA384 = 6BF50128 C1F62049 0729FB88 96DBEDA1 9A4F5B8E
                            34DD25A4 1916261A 39B62908 EFA10753 EA56120E
                            27C6A173 870BD1CF
ycsb-0.3.0.tar.gz: SHA512 = 406826AA 1048E88E C9B17427 C31C2A6D 73FBE550
                            740B4393 B829FAFE E2614905 D2FD9ACD C1BC097B
                            5F6CA7C3 3624EFC7 4F381C00 BC6A3465 445E1680
                            9C6E1EF8

Draft Release

Now that you have workable convenience artifacts, go ahead and push the tag to GitHub.

  #!/bin/bash
  #
  # Presumes you are on the staging branch.

  # Update the following two variables before running this script.
  VERSION=0.3.0

  # Now create a tag that we can reference on GitHub.
  git tag $VERSION

  # Finally push the tag up to GitHub.
  git push origin $VERSION

Once the tag exists and all of your convenience artifacts are ready, you can publish the release:

  1. Visit the "Draft new release" page
  2. In the "Tag version" field, enter the tag you created above, ${VERSION}
  3. Ensure the @ Target branch is the staging branch from above, ${VERSION}-staging
  4. Fill in a title of "YCSB version", e.g. "YCSB 0.3.0"
  5. Fill in the description with the release notes you drafted above.
  6. Attach all of the convenience artifacts and digest files created above.
  7. Be sure the "this is a pre-release" box is not checked.

Announce Release

You should let interested communities know that a new version is available. In particular, we try to make sure any of the communities with datastore bindings in the release know.

You should adapt the template below to highlight significant datastore binding changes and major features. Include a summary line for those datastore bindings that were not tested in the release. If a supported datastore binding did not change the range of versions supported, omit from the general template. Be sure to still list it as supported in the email to that datastore's community.

It's usually helpful to tailor the template to the particular community, by putting their datastore at the top of the list, if it is in the supported category. If theirs is in the 'experimental' camp, you can mention their datastore, for instance:

"~5 additional datastore bindings in experimental status (including Couchbase)"

Subject: [ANNOUNCE] YCSB version Release

On behalf of the development community, I am pleased to announce the release of YCSB version.

Highlights:

  • DataStore A 2.2 support
  • DataStore B 1.3 support
  • DataStore C 0.8.1 support
  • ~5 additional datastore bindings in experimental status
  • Some other feature

Full release notes, including links to source and convenience binaries:

https://github.com/brianfrankcooper/YCSB/releases/tag/_version_

This release covers changes from the last X months.

Here's a list of communities we have previously announced our releases in (typically, you will need to sign up for an account to post to these boards):

Clean up

Once the release is out, there are a few final steps to take care of.

  • Remove staging branch in git $ git push origin :_version_-staging
  • Close your release issue, include a message that points to the published release
  • Create a PR to update the top-level README.md to reference downloading the new version
  • Update the top-level wiki page to reference downloading the new version
  • Update getting started to reference downloading the new version
  • Add your release issue to the examples for future release managers
  • If any new bindings were added, update the [list of message boards](#Announce Release)

Examples

Below are prior release issues, so you can get a better idea of timing and the kinds of status updates that have been useful before.

  • Version 0.2.0 - RM Sean Busbey - #266
  • Version 0.3.0 - RM Govind Kamat - #358
  • Version 0.3.1 - RM Sean Busbey - #391
  • Version 0.4.0 - RM Rob Moore - #409
  • Version 0.5.0 - RM Connor McCoy - #456
  • Version 0.6.0 - RM Eugene Blikh - #542
  • Version 0.7.0 - RM Kevin Risden - #624
  • Version 0.8.0 - RM Chrisjan Matser - #678
  • Version 0.9.0 - RM Stanley Feng - #740
  • Version 0.10.0 - RM Sean Busbey - #772
  • Version 0.11.0 - RM Govind Kamat - #827
  • Version 0.12.0 - RM Kevin Risden - #827
  • Version 0.13.0 (non-production) - RM Chris Larsen, then Sean Busbey - #981
  • Version 0.14.0 - RM Sean Busbey - #1117
  • Version 0.15.0 - RM Sean Busbey - #1204
  • Version 0.16.0 (non-production) - RM Sean Busbey - #1265
  • Version 0.17.0 - RM Sean Busbey - #1355
Add a custom footer
Add a custom sidebar
Clone this wiki locally