Skip to content

Latest commit

 

History

History
47 lines (40 loc) · 1.46 KB

RELEASE.md

File metadata and controls

47 lines (40 loc) · 1.46 KB
Raw

Release

Here's how OAuth2 Proxy releases are created.

Schedule

Our aim is to release once a quarter, but bug fixes will be prioritised and might be released earlier.

The Process

Note this uses v4.1.0 as an example release number.

  1. Create a draft Github release
  • Use format v4.1.0 for both the tag and title
  1. Update CHANGELOG.md
  • Write the release highlights
  • Copy in headings ready for the next release
  1. Create release commit
git checkout -b release-v4.1.0
  1. Create pull request getting other maintainers to review
  2. Copy the release notes in to the draft Github release, adding a link to CHANGELOG.md
  3. Update you local master branch
git checkout master
git pull
  1. Create & push the tag
git tag v4.1.0
git push --tags
  1. Make the release artefacts
make release
  1. Upload all the files (not the folders) from the /release folder to Github release as binary artefacts. There should be both the tarballs (tar.gz) and the checksum files (sha256sum.txt).
  2. Publish release in Github
  3. Make and push docker images to Quay
make docker-all
make docker-push-all

Note: Ensure the docker tags don't include -dirty. This means you have uncommitted changes.

  1. Verify everything looks good at quay and github