Skip to content

Latest commit

 

History

History
38 lines (28 loc) · 1.76 KB

release_process.md

File metadata and controls

38 lines (28 loc) · 1.76 KB
Raw

Agones Release Management

Release Cadence

  • Versioned releases will occur every 6 weeks
  • Releases occur on a Tuesday.
  • 5 week development cycle, at the end of a which a Release Candidate (RC) will be released with the contents of main.
  • For the next week, the project is in "feature freeze". Only the following pull requests will be accepted during this time:
    • Bug fixes.
    • Build tools enhancements that won't alter build artifacts (i.e. Makefile refactoring is acceptable, Go version upgrading is not).
    • Documentation and example improvements or fixes.
  • Any new PRs that are submitted during feature freeze, will be tagged with the label feature-freeze-do-not-merge to delineate that they should only be merged after the full release is complete.
  • At the end of the RC week, the complete version release will occur.

Release Calendar

Release Process

  1. Create a Release Issue from the release issue template.
  2. Label the issue kind/release, and attach it to the milestone that it matches.
  3. Complete all items in the release issue checklist.
  4. Close the release issue.

Hot fix Process

  1. Hotfixes will occur as needed, to be determined by those will commit access on the repository.
  2. Create a Release Issue from the release issue template.
  3. Label the issue release, and attach it to the next upcoming milestone.
  4. Complete all items in the release issue checklist.
  5. Close the release issue.