Stage futures-preview crates #1048
Merged
Conversation
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
Closed
|
lgtm |
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.
This moves the current 0.2 crates into "*-preview" packages to denote that they're not releases that are expected to be stable long-term. Following this release, 0.2.0 and 0.2.1 of each crate will be yanked, leaving 0.1 as the current long-term release, with 0.3 as the next upcoming "preview" release. 0.2 will never see a long-term release.
Once released under "*-preview", 0.3 will receive regular updates, but will not be expected to be backwards-compatible, and will be nightly-only. Once futures-in-std have stabilized, 0.3 will move to the non-preview channel and no longer introduce breaking changes.
Apologies for all the confusion throughout this process-- hopefully this plan clarifies things. If you have any questions about the plan, feel free to comment here or message me on the rust-lang discord.
Fix #1039
cc @seanmonstar, @carllerche