Prepare for 0.1a.0 release #190
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
c24t
requested review from
a-feld,
carlosalberto,
lzchen,
Oberon00,
reyang and
toumorokoshi
as code owners
reyang
approved these changes
Sep 30, 2019
lzchen
approved these changes
Sep 30, 2019
|
The version number here follows the PEP 440 guidance for pre-releases. For future releases we'll follow the spec milestones, and may need to keep our release versions in sync with the spec. |
toumorokoshi
approved these changes
Sep 30, 2019
|
@c24t |
This was referenced Oct 29, 2019
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 PR updates the version number for all packages to
0.1a.0, and updates dependencies to match. This updates thev0.1a.xbranch only, we'll keep the0.1.dev0version on master.Like in OpenCensus,
v0.1a.xis a dedicated release branch for the0.1.*alpha releases. In principle we can cherry-pick bugfixes onto this branch from master, but we're unlikely to want to do this since this is an alpha release and advertised as unstable.For now, we need to manually create a GH release and manually push to PyPI. We should automate this before the next release.
See also #189, which updates the README to include info about this release.