-
Mark Mandel authored
This PR includes: - small fixes to the release process that came up during the last release - Adding links to the release process from the main README - Including a release calendar that people can see.
Mark Mandel authoredThis PR includes: - small fixes to the release process that came up during the last release - Adding links to the release process from the main README - Including a release calendar that people can see.
release_process.md 1.56 KiB
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 master.
- For the next week, the project is in "feature freeze" - i.e. only bug and documentation (.md and examples) fixes during this time.
- Any new PRs that are submitted during feature freeze, will be tagged with the label
merge-after-releaseto delineate that they should only be merged after the full release is complete.
- Any new PRs that are submitted during feature freeze, will be tagged with the label
- At the end of the RC week, the complete version release will occur.
Release Calendar
Release Process
- Create a Release Issue from the release issue template.
- Label the issue
kind/release, and attach it to the milestone that it matches. - Complete all items in the release issue checklist.
- Close the release issue.
Hot fix Process
- Hotfixes will occur as needed, to be determined by those will commit access on the repository.
- Create a Release Issue from the release issue template.
- Label the issue
release, and attach it to the next upcoming milestone. - Complete all items in the release issue checklist.
- Close the release issue.