momo-jun commented on code in PR #433: URL: https://github.com/apache/pulsar-site/pull/433#discussion_r1115172798
########## contribute/release-policy.md: ########## @@ -0,0 +1,94 @@ +--- +id: release-policy +title: Release policy +--- + +## Release semantics + +The Pulsar project follows a variant of [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. The difference is that a major version bump will not carry any special meaning in terms of "big features" included in the release or breaking API changes. Instead, it would simply signal a new long-term support (LTS) release. + +For example, + +* 2.10.0 is a feature release; +* 2.10.1 is a patch release; Review Comment: We need to align on the wording and consistently use it throughout the doc site. @codelipenghui and @BewareMyPower mentioned there was no `patch release` term for Pulsar, so we named it `minor` in contrast to `major` in the release process doc. If we decide to go with `feature/patch`, better eliminate `major/minor` to avoid confusing and guessing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
