-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use rocket 0.5-rc1, remove rocket-contrib #672
Conversation
mixnode/Cargo.toml
Outdated
bs58 = "0.4.0" | ||
clap = "2.33.0" | ||
bs58 = "0.4" | ||
clap = "2" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we be versioning with explicit patch versions in case things become incompatible at some point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Semver crates with versions greater then 1
should only break API at major versions changes, and those < 1
should only break at minor versions, so I'm being optimistic :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're assuming everyone is going to be following it properly : )
But I guess it should mostly be the case for the major crates
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm an optimist, makes it easier to stay up to date on crates. Maybe we should remain paranoid on 0.*
crates...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just re-read my comment and I think I confused you (and myself). Even though I said "patch" i meant minor version. oops. So x.y rather than entire x.y.z
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can skip minors on the 1+
, there are only a few of them, and they are developed by mature teams, so my optimistic proposal is we use major only for 1>
and minor for <1
. In the paranoid variant I suggest patch from <1
. I expect stable crates would not break APIs on minor versions, but we can be extra careful here as well and do minor.
Nightlies broken on a new clippy lint |
No description provided.