Reopen master for breaking changes #21610
Merged
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
|
Could be 0.7.0-Dev, which is less "shouty". |
|
that would also be easier to accidentally mistype, and write incorrect comparison conditions |
|
#21475 is the only thing left on the milestone. That needs to happen by final release but it's a doc change so isn't absolutely needed for rc1. Merging this and branching now. |
Closed
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.
Based on some recent discussion, currently we're thinking we will call master 0.7.0-DEV (capitalized this time, so it sorts before 0.7.0-alpha) so we can add new deprecations in this next release cycle, and stick with our existing policy of removing those new deprecations in the next release which will be 1.0.
0.7 will be intended mostly as a transitional porting helper, the plan is for 1.0 to be released almost immediately after 0.7 with the only code difference being removal of deprecations. There was an idea of maybe putting deprecations in a package and going straight to 1.0-DEV right now, but that's not practical with syntax deprecations.
This should be squash merged once the PR's that are open and ready and will be going into 0.6 are merged. We can create the release-0.6 branch from the commit immediately preceding when this gets merged, and put out RC1 as soon as it goes through a PkgEval run for regression testing against beta.