-
Notifications
You must be signed in to change notification settings - Fork 695
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
Release notes? #993
Comments
Yeah, AFAIK we don't have any changelog right now (and creating them for existing tags is somewhat hard). For better visibility, I've created GitHub Releases for existing tags: https://github.com/semver/semver/releases |
Ok. I mean, I was hoping for more of a summary of what changed between 1.x.x and 2.0.0 for example, rather than simply a list of commits. I feel like it could be good for this repo to set a good example, considering this repo's topic is strongly related to releases :) |
Note that if you copied the tags into branches, then it would be straight forward to use the github 'Compare' to compare the two versions. |
Note that the notes on GitHub Releases are auto-generated! I hope someone could write down some more things but I couldn't find any discussion or something else other than commits... |
@hughperkins I just posted some history notes on the 2.0.0 spec (#976 (comment)). WIP: going back further and into more detail. |
@hughperkins The full history, since mojombo handed everything off to haacked, can be found here: https://github.com/semver/semver/commits/master/semver.md Changes tend to accumulated over here on semver/semver and then get dumped in batches into the official document(s) posted over on semver/semver.org. |
Nothing to preview |
I see there are multiple versions of semver, 1.0.0, 2.0.0, etc. I dont see any releases on this github repo, or release notes. Where can I find those? If they don't already exist, I feel it might be useful to create those? (and if they do, then maybe make them easier to find?)
The text was updated successfully, but these errors were encountered: