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.
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
Updates to README #453
Updates to README #453
Changes from 14 commits
6481f73
1dc5802
3d5d527
12d7a45
119a74d
0bc6aee
f899ece
fe087af
c27659b
7127898
01809c3
0c7abf4
242ce8d
0bafb55
d094f3e
66c268f
2db9d83
949cc52
4d27323
4a687c9
6751273
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 would mayhaps move these to CHANGELOG.md and mayhaps mark breaking public API changes some way e.g.
Breaking Changes:
thereThere 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 kinda of agree that it feels cluttered here, but CHANGELOG.md has a list of all the versions. So to keep it consistent, the API-breaking changes would have to go just in the x.0.0 headers. But that makes it hard to skim. Did you have something in mind?
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.
Ctrl-F "Breaking Changes" ? 😅
Ideally they probably mayhaps be in Release notes in GitHub and then link to release notes - which in turn get generated from CHANGELOG.md automatically upon release - that could be linked instead ?
Could also link by to CHANGELOG.md with
#
anchor points ?There isn't too many with 2.x anymore and the ones at 2.x are unmaintained anyways me thinks ?
https://crates.io/crates/curve25519-dalek/reverse_dependencies
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 split the difference a bit here. I left the 4.x breaking changes in the README so people can see it at a glance. The rest is now in the CHANGELOG under "Breaking changes"
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 removed the line here about removing exemptions in the future. It wasn't saying much and we don't need to make those promises now imo.