{{ message }}
Repository navigation
docs: draft release schedule for discussion - #2047
Open
NiklasHerrmann21 wants to merge 1 commit into
Open
NiklasHerrmann21 wants to merge 1 commit into
NiklasHerrmann21 wants to merge 1 commit into
Conversation
…e cycles) Working document modeled after the SAP CAP release schedule, formalizing the de-facto release practice (active line on main, maintenance line on main-3.x) and collecting open questions for team discussion.
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
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.
What
Draft of a fixed release schedule for the library, modeled after the SAP CAP release schedule:
It formalizes the de-facto practice (active line on
main, maintenance line onmain-3.x, existing release process) and defines active / maintenance / end-of-life status with a proposed 12-month maintenance window (at most two majors maintained in parallel).Why a schedule
Consumers (and we) get a reliable planning basis: when to expect majors, what a maintenance line still receives, and when to migrate.
Status
Working document — the Open Questions section (major month, maintenance window, backport criteria, deprecation policy, EOL communication, …) is the agenda for the review. Comments welcome; this is expected to be iterated before it becomes a commitment.