Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SECURITY] Add Security Policy and Supported Versions page to website #10829

Merged
merged 7 commits into from
Feb 10, 2022
Prev Previous commit
Next Next commit
Add note about upgrade compatibility
  • Loading branch information
michaeljmarshall committed Feb 10, 2022
commit 2df790106a316335085460e5e455638eb52e58e4
3 changes: 3 additions & 0 deletions site2/docs/security-versioning-policy.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,9 @@ For instructions on how to subscribe, please see https://pulsar.apache.org/conta
The Pulsar project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). Existing releases can expect
patches for bugs and security vulnerabilities. New features will target minor releases.

When upgrading an existing cluster, it is important to upgrade components linearly through each minor version. For
example, when upgrading from 2.8.x to 2.10.x, it is important to upgrade to 2.9.x before going to 2.10.x.

## Supported Versions

Feature release branches will be maintained with security fix and bug fix releases for a period of at least 12 months
Expand Down