-
-
Notifications
You must be signed in to change notification settings - Fork 18
Commit to semantic versioning #165
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
Conversation
We probably want some additional documentation for ppb-vector, but for now, the API reference is all there is.
Got a 👍 from Piper in Discord.
|
@pathunstrom Sorry, I accidentally opened the PR too early (i.e. before I had commited the relevant changes >_>') @astronouth7303 I got a 👍 from Piper on Discord, re: semver, but I would prefer to have your opinion before committing to it. |
pathunstrom
left a comment
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.
Just reconfirming, this still looks good to me.
|
Yes semver good Although I suspect 2.0 will be "yeah, it's API compatible, but now it's all native" |
|
bors r=astranouth5303,pathunstrom |
165: Commit to semantic versioning r=astranouth5303,pathunstrom a=nbraud Also snuck in 2 minor changes to `README.md`, as I didn't want to deal with conflicting PRs: - call the RTD docs “API reference”; - use complete sentences. Co-authored-by: Nicolas Braud-Santoni <nicolas@braud-santoni.eu>
|
@astronouth7303 Why would we call it 2.0, if it's the same thing but faster? |
Build succeeded
|
Also snuck in 2 minor changes to
README.md, as I didn't want to deal with conflicting PRs: