bump version for 2.1.0 dev (still on master) #3050
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
antiochp
force-pushed
the
2_1_0_dev_user_agent
branch
from
7274900 to
639425d
Compare
quentinlesceller
approved these changes
Sep 19, 2019
jaspervdm
approved these changes
Sep 19, 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.
Bumps the crate versions to reflect upcoming release
2.1.0.This is on
masterso I bumped the version to2.1.0-dev.1which I think makes more sense than the2.0.1-beta.1currently in place.Proposing we stick with
-devsuffix until we cut the beta release when we can bump the versioning again to2.1.0-beta.1on the 2.1.0 branch itself.I'd like to be able to visually inspect peer user agents in the TUI and have a rough idea of which are running against a recent build from master.
I toyed with the idea of including the build date or timestamp in the user agent when built from master. But there are some privacy and anonymity concerns involved there.