Clarify release expectations: add tagging policy and align versioning language#703
Open
rohansood10 wants to merge 1 commit intodapr:masterfrom
Open
Clarify release expectations: add tagging policy and align versioning language#703rohansood10 wants to merge 1 commit intodapr:masterfrom
rohansood10 wants to merge 1 commit intodapr:masterfrom
Conversation
… language Address dapr/dapr#8188 by: - Adding an explicit tagging policy section covering core Dapr releases, component releases, and GitHub release annotations - Defining release types (stable, release candidate, security/bug fix) with clear tag format examples - Aligning versioning language between this document and the supported releases documentation - Clarifying the relationship between component maturity lifecycle and core release versioning - Fixing minor typos (cadence, corresponding) Signed-off-by: rohansood10 <rohansood10@users.noreply.github.com>
Author
|
Friendly ping — any chance to review this when you get a moment? Happy to make changes if needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Addresses dapr/dapr#8188 — Release Expectations: Clarify discrepancies and update to be easier for end users to understand.
Changes
Updates
release-process.mdto address the four items raised by the CNCF TOC:Align language between release process and support policy — Expanded the versioning section with a clear table matching the MAJOR/MINOR/PATCH definitions used in the supported releases documentation, and added explicit cross-references between the two documents.
Align maturity tagging between core Dapr and components — Added a dedicated section explaining that components follow their own maturity lifecycle (alpha → beta → stable) independent of the core Dapr release version, with a link to the component certification lifecycle docs.
Add a tagging policy — New "Tagging policy" section documenting the tag formats for stable releases, release candidates, and security/bug fix patches, for both core Dapr repos and components-contrib.
Clarify stable vs unstable vs security/bug releases — Each release type is now explicitly defined with tag format examples and guidance on production readiness. GitHub release annotation conventions (Latest vs Pre-release) are also documented.
Additional improvements
candence→cadence,correspondig→corresponding)Files changed
release-process.md— 1 file, ~71 insertions, ~35 deletionsRisk
Low — Documentation-only change. No code, tests, or runtime behavior affected.