diff options
| -rw-r--r-- | docs/dev/policy/release_and_support_schedule.md.md | 32 |
1 files changed, 18 insertions, 14 deletions
diff --git a/docs/dev/policy/release_and_support_schedule.md.md b/docs/dev/policy/release_and_support_schedule.md.md index 3ef3457569..9feb9c0f1d 100644 --- a/docs/dev/policy/release_and_support_schedule.md.md +++ b/docs/dev/policy/release_and_support_schedule.md.md @@ -6,12 +6,12 @@ Chef Infra releases follow a `MAJOR.MINOR.PATCH` versioning scheme based on [Sem Given a version number `MAJOR.MINOR.PATCH`: - * **MAJOR** version releases (e.g. 1.x -> 2.x) will include breaking or backwards-incompatible changes. + * **MAJOR** version releases (e.g. 15.x -> 16.x) will include breaking or backwards-incompatible changes. * _Example: When changing the load order of any cookbook segments_ - * **MINOR** version releases (e.g. 1.1 -> 1.2) will include new features, bug fixes, and will be backwards-compatible to the best of the maintainers' abilities. + * **MINOR** version releases (e.g. 15.1 -> 15.2) will include new features, bug fixes, and will be backwards-compatible to the best of the maintainers' abilities. * _Example: When adding support to the mount provider for special filesystem types that were previously unsupported._ * _Example: Major version bump of a software dependency._ - * **PATCH** version releases (e.g. 1.1.1 -> 1.1.2) will include backwards-compatible bug fixes. + * **PATCH** version releases (e.g. 15.1.1 -> 15.1.2) will include backwards-compatible bug fixes. * _Example: Minor version bump of a software dependency._ When incrementing a version, the following conditions will apply: @@ -20,22 +20,17 @@ When incrementing a version, the following conditions will apply: * _Note: New features that did not exist in version 1.1.0 may be released in 2.0.0 without any intermediary releases._ * When **MINOR** increases, **PATCH** will be reset to zero (e.g. 11.3.x -> 11.4.0) -When contextually appropriate, a version may be referred to by only the **MAJOR** or **MAJOR.MINOR** versions. For example: - - * a breaking change: "This behavior will change in Chef 16" would refer to the first release in the `16.MINOR.PATCH` series. - * a future feature release:: "We expect to release Chef Workstation 2.2 this month" would refer to the `2.2.PATCH` build that was selected as the stable release. - ### Auto-bumping PATCH versions -Chef projects are managed by our Expeditor release tooling application. This application is executed each time a pull request is merged and incrementwss the patch version of the software before running the change through our internal CI/CD pipeline. As not all builds will make it successfully through the CI/CD pipeline, the versions available for public consumption might have gaps (e.g. 1.2.1, 1.2.10, 1.2.11, 1.2.12, 1.2.20), but all verisons have been built and tested. +Chef projects are managed by our Expeditor release tooling application. This application is executed each time a GitHubb Pull Request is merged and incrementwss the patch version of the software before running the change through our internal CI/CD pipeline. As not all builds will make it successfully through the CI/CD pipeline, the versions available for public consumption might have gaps (e.g. 1.2.1, 1.2.10, 1.2.11, 1.2.12, 1.2.20), but all verisons have been built and tested. ## Support Schedule -Chef currently supports the current major version release as well as the previous major version release. These releases each fall into one of three distinct lifecycle stages: +Chef currently supports the current **major version** release as well as the previous **major version** release. These releases each fall into one of three distinct lifecycle stages: - - Generally Available - - Deprecated - - End of Life (EOL) + - **Generally Available (GA)** + - **Deprecated** + - **End of Life (EOL)** ### Generally Available (GA) @@ -61,7 +56,16 @@ This stage indicates a previously deprecated release version, which is no longer ## Release Schedule -The current Generally Availble (stable) release of Chef Infra is released on a regular cadence with a new **minor release shipping every month** during the 2nd week of the month. A new **major release ships every April**, at which time the previous GA release will become deprecated with further releases only for critical bugs or security issues. +### Generally Available Release Schedule + + - **Minor releases**: 2nd week of each month + - **Major releases**: Once a year in April + +### Deprecated Release Schedule + + - Adhoc released for critical bugs and security vulnerabilities only + +## Release Announcements Each release will be announced to the "chef-release" [Chef Mailing List](https://discourse.chef.io) category, notifying users of the new stable release. |