This repository was archived by the owner on Sep 17, 2025. It is now read-only.
Update version, add changelog#463
Merged
c24t merged 2 commits intocensus-instrumentation:masterfrom Jan 22, 2019
Merged
Conversation
songy23
approved these changes
Jan 22, 2019
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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 copies the changelog from #460 and adds an "unreleased" section. Significant changes on master should modify this section, and it should be copied verbatim into a new version-specific section of the changelog on each release. The changelog already exists on both release branches, this PR just adds it to master.
This PR also changes the version number to
0.3.dev0to indicate that this is the development version of the unreleasedv0.3.0version of the library.Another option is to name this version
v0.2.dev0and increment the version number on master with each patch-level update to thev0.2.xbranch. This has the benefit of keeping the version numbers consistent across branches, but is potentially confusing since the version on master may include changes that won't be included in a release until the next minor- or major-version update.Keeping the master version number one minor version ahead of the latest release is also consistent with the guidance in PEP 440 for development releases since development releases are ordered behind regular releases.
We should never upload code from master to PyPI without creating a release branch and updating the version number, so "dev" version numbers should only apply to distributions of the library built from source. Since packaging tools like
pipuse this version number syntax, this change also makes it possible to specify the unreleased version of the library as a dependency, as e.g.opencensus>0.2.