This repository was archived by the owner on Sep 17, 2025. It is now read-only.
Prepare for 0.2.0 release#460
Closed
c24t wants to merge 1 commit intocensus-instrumentation:masterfrom
Closed
Conversation
bogdandrutu
approved these changes
Jan 19, 2019
bogdandrutu
approved these changes
Jan 19, 2019
Member
Author
|
Pushed to the |
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.
After merging this change into master I'll create a separate
v0.2.xrelease branch on the remote, tag the head commit asv0.2.0, and release to PyPI. The release branch will diverge from master as we cherry-pick bugfixes onto it, using the release strategy from #412.Since the library is still changing quickly I think it makes sense to cut more minor version releases with the expectation that the behavior and API may change between versions. We won't maintain multiple minor versions at once; all new changes including bugfixes will happen on master or the
v.2.xbranch.Merging this into master also means that the library will report the same version (
0.2.0) when it's built from source as when it's installed from PyPI. We may want to change the version number on master to avoid this, e.g. to includedev.Fixes #403 and #391.