Unless there are no changes, we create releases for google-cloud-cpp every 4 weeks, or if there is a major announcement or change to the status of one of the libraries (like reaching the "Alpha" or "Beta" milestone).

The intended audience of this document are developers in the google-cloud-cpp project that need to create a new release. The audience is expected to be familiar with the project itself, git, GitHub, semantic versioning.

Assuming you are working on your own fork of the google-cloud-cpp project, and upstream points to the googleapis/google-cloud-cpp remote, these commands should be useful in identifying important changes for inclusion in the release notes.

Before beginning the release process, verify all CI builds are passing on master.

Update CHANGELOG.md based on the release notes for Bigtable, Storage, Spanner, and the common libraries:

# Summarize the output of this into CHANGELOG.md under the "Bigtable" header
git log --no-merges --format="format:* %s" \
    $(git describe --tags --abbrev=0 upstream/master)..HEAD \
    upstream/master -- google/cloud/bigtable

# Summarize the output of this into CHANGELOG.md under the "Storage" header
git log --no-merges --format="format:* %s" \
    $(git describe --tags --abbrev=0 upstream/master)..HEAD \
    upstream/master -- google/cloud/storage

# Summarize the output of this into CHANGELOG.md under the "Spanner" header
git log --no-merges --format="format:* %s" \
    $(git describe --tags --abbrev=0 upstream/master)..HEAD \
    upstream/master -- google/cloud/spanner

# Summarize the output of this into CHANGELOG.md under the "Common libraries" header
git log --no-merges --format="format:* %s" \
    $(git describe --tags --abbrev=0 upstream/master)..HEAD \
    upstream/master -- google/cloud \
   ':(exclude)google/cloud/firestore/' \
   ':(exclude)google/cloud/bigquery/' \
   ':(exclude)google/cloud/bigtable/' \
   ':(exclude)google/cloud/pubsub/' \
   ':(exclude)google/cloud/spanner/' \
   ':(exclude)google/cloud/storage/'

Any chore/ci/test-tagged PRs in the above lists should probably be discarded as they are uninteresting to our users.

It is not recommended that you create the release branch before this PR is merged, but in some circumstances it might be needed, for example, if a large change that could destabilize the release is about to be merged, or if we want to create the release at an specific point in the revision history.

We next need to create the release tag, the release branch, and create the release in the GitHub UI. These steps are handled automatically for us by the ./release/release.sh script.

No PR is needed for this step.

First run the following command -- which will NOT make any changes to any repos -- and verify that the output and version numbers look correct.

$ ./release/release.sh googleapis/google-cloud-cpp

If the output from the previous command looks OK, rerun the command with the -f flag, which will make the changes and push them to the remote repo.

$ ./release/release.sh -f googleapis/google-cloud-cpp

NOTE: This script can be run from any directory. It operates only on the specified repo.

Review the new release in the GitHub web UI (the link to the pre-release will be output from the release.sh script that was run in the previous step). If everything looks OK, uncheck the pre-release checkbox and publish.

Manually run a Kokoro job cloud-devrel/client-libraries/cpp/google-cloud-cpp/publish-refdocs in the Cloud C++ internal testing dashboard and specify the branch name (e.g. v0.11.x) in the Committish field. This job will generate and upload the doxygen documentation to the staging bucket for googleapis.dev hosting. The uploaded documentation will generally be live in an hour at the following URLs:

• https://googleapis.dev/cpp/google-cloud-bigtable/latest/
• https://googleapis.dev/cpp/google-cloud-storage/latest/
• https://googleapis.dev/cpp/google-cloud-spanner/latest/
• https://googleapis.dev/cpp/google-cloud-common/latest/

Working in your fork of google-cloud-cpp: bump the version numbers to the next version (i.e., one version past the release you just did above), and send the PR for review against master You need to:

• Update the version numbers in the top-level CMakeLists.txt file.
• Run the cmake configuration step, this will update the different version_info.h files.
• Update the version number and SHA256 checksums in the google/cloud/*/quickstart/WORKSPACE files to point to the just-released version.

We use the GitHub Branch Settings to protect the release branches against accidental mistakes. From time to time changes in the release branch naming conventions may require you to change these settings. Please note that we use more strict settings for release branches than for master, in particular:

• We require at least one review, but stale reviews are dismissed.

• The Require status checks to pass before merging option is set. This prevents merges into the release branches that break the build.

  • The Require branches to be up to date before merging sub-option is set. This prevents two merges that do not conflict, but nevertheless break if both are pushed, to actually merge.
  • The Kokoro Ubuntu, Kokoro Windows, cla/google, and continuous-integration/travis-ci checks are required to pass.

• The Include administrators checkbox is turned on, we want to stop ourselves from making mistakes.

• Turn on the Restrict who can push to matching branches. Only Google team members should be pushing to release branches.

Nudge coryan@ to send a PR to vcpkg. The PRs are not difficult, but contributing to this repository requires SVP approval.

In your development fork:

• Switch to the existing release branch, e.g. git checkout v1.17.x.
• Create a new branch off the release branch.
• Create or cherry-pick commits with the desired changes.
• Update CHANELOG.md to reflect the changes made.
• Bump the minor version number in the top-level CMakeLists.txt and run the cmake configuration step to update the different version_info.h files.
• After merging the PR(s) with all the above changes, use the Release gui on github to create a pre-release along with a new tag for the release.
• After review, publish the release.
• Manually run a Kokoro job cloud-devrel/client-libraries/cpp/google-cloud-cpp/publish-refdocs in the Cloud C++ internal testing dashboard and specify the branch name (e.g. v1.17.x) in the Committish field.
• Nudge coryan@ to send a PR to vcpkg.