This repository has been archived by the owner on Apr 18, 2018. It is now read-only.
doc: refine lts strawman #56
Closed
Conversation
This file contains 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
based on feedback, refine the LTS strawman.
|
|
||
| Once the `-rc.1` tag is cut at a particular point, the master stream goes into "Feature Freeze" until the release branch is cut. New features landed before the `-rc.1` tag make it into the LTS Release, those that do not must wait to land until after the Feature Freeze is lifted. | ||
| For instance, suppose the master branch rolls to version `2.0.0`. The LTS WG can decide in advance that there will be an LTS release in the `2.0.x` stream. At any point, the LTS WG can declare any version within that stream to be an "LTS Candidate" by cutting a `2.0-rc.1` tag. Sufficient time should then be given to allow the tag to be reviewed and tested. If things look good, the tagged version becomes the LTS Release. If, after testing, it becomes apparent that additional patches become necessary, the LTS Candidate can be shifted and a new `2.0-rc.2` at a specific patch level. |
There was a problem hiding this comment.
At any point, the LTS WG can declare any version within that stream to be an "LTS Candidate" by cutting a
2.0-rc.1tag.
It would be better to just choose it when a new minor rolls out. Far less confusing, makes less tension with master, etc.
There was a problem hiding this comment.
That'll likely be how it plays out (note the examples, each -rc. is cut when the minor rolls over, patches come in as necessary then either the LTS is cut or we roll to the next minor and try again.
|
This PR would be obsoleted and replaced by #59 |
Merged
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
based on feedback, refine the LTS strawman.