Skip to content

Latest commit

 

History

History
27 lines (16 loc) · 1.14 KB

RELEASE.md

File metadata and controls

27 lines (16 loc) · 1.14 KB

Zipkin Release Process

  1. Verify that the build you're releasing is green

    There is currently no automated testing during the release process. As the person pushing a release tag, you'll need to manually check that the test run on Travis is green for the commit you're tagging. (Building tooling for this would be awesome.)

  2. Push a git tag

    For release candidates, this should be something like 1.2.2-rc1. For final releases, it's just 1.2.2.

  3. Wait for Travis CI

    This part is controlled by travis/publish.sh. It creates a bunch of new commits, bumps the version if this was a final (non-RC) release, publishes SNAPSHOT and non-SNAPSHOT artifacts (SNAPSHOT artifacts are published for each build on master). A high-level overview of how the release happens for RC and final releases:

    Release example

    A detailed view at the process:

    Release details

  4. Publish docker-zipkin

    Refer to docker-zipkin/RELEASE.md.