Skip to content

Latest commit

 

History

History
23 lines (14 loc) · 1.11 KB

RELEASE.md

File metadata and controls

23 lines (14 loc) · 1.11 KB
Raw

Zipkin Api Release Process

This repo uses semantic versions. Please keep this in mind when choosing version numbers.

  1. Alert others you are releasing

    There should be no commits made to master while the release is in progress (about 10 minutes). Before you start a release, alert others on gitter so that they don't accidentally merge anything. If they do, and the build fails because of that, you'll have to recreate the release tag described below.

  2. Push a git tag

    The tag should be of the format release-N.M.L, for example release-3.7.1.

  3. Wait for CircleCI

    This part is controlled by build-support/publish-stable.sh. It creates a bunch of new commits, bumps the version, publishes artifacts, and syncs to Maven Central. https://circleci.com/gh/openzipkin/zipkin-api

Credentials

Credentials of various kind are needed for the release process to work. If you notice something failing due to unauthorized, re-save them as environment variables.