Skip to content

Latest commit

 

History

History
32 lines (28 loc) · 1.52 KB

release.md

File metadata and controls

32 lines (28 loc) · 1.52 KB
Raw

Release process

To release a new version, you need to be a member of gcp-variant-transforms-test project and have write access to the GitHub repo.

The process is as follows:

  1. Navigate to Container Builder build history and verify that the latest integration tests have passed.
  2. Choose the appropriate version number by following the semantics in https://semver.org/. See the Summary section for a quick overview.
  3. Update the version number in setup.py by submitting a change.
  4. Wait until the integration tests are done. It will take about 2 hours. Ensure that there are no failures. In case of failures, rollback the version change in setup.py and continue from Step #1 once the errors are fixed.
  5. Navigate to the releases tab and click on Draft a new release.
    1. Set the Tag version to vX.X.X where X.X.X is the release version specified previously.
    2. Set the Target to the commit that changed the version number.
    3. Set the Release title to "Release vX.X.X".
    4. Enter a description of the main features and/or bug fixes going into the release.
    5. Click on Publish release.
    6. This will kick off a trigger to copy the verified image to the main project.
  6. Congratulations! The release process is now complete!