Add parallel update path for prereleases. #206
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
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 allows us to make prerelease releases that are available from python.org and will automatically update through subsequent prereleases until the next real release. Prereleases are not added to the Store.
It's currently not clear whether an automatic update from a prerelease to a real release will later automatically update back to a prerelease - that's entirely in the hands of the OS, which decides whether it will replace auto-update settings for a package. Either way, since our intended release model is for updates as needed and only infrequent feature development, there's no reason to think we'll spend much time in prereleases.