Skip to content

Latest commit

 

History

History
26 lines (17 loc) · 1.21 KB

RELEASE.md

File metadata and controls

26 lines (17 loc) · 1.21 KB

Zipkin Release Process

This repo uses semantic versions with a twist: we update minors on api-breaks until we hit 1.0. 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-0.18.1.

  3. Wait for Travis CI

    This part is controlled by travis/publish.sh. It creates a bunch of new commits, bumps the version, publishes artifacts, syncs to Maven Central, and publishes Javaocs to http://zipkin.io/zipkin into a versioned subdirectory. (Note: Javaocs are also published on all builds of master; due to versioning, it doesn't overwrite docs built for releases.)

  4. Publish docker-zipkin-java

    Refer to docker-zipkin-java/RELEASE.md.