4 ms·
Semantic Versioning 2.0.0
- soroso 11y agoWhere's the changelog? What has changed?
- killercup 11y agoNow if only Semantic Versioning had a Changelog…
- raziel2p 11y agoAccording to github[1], version 2 has been out for two years. Kinda misleading submission title. 1: https://github.com/mojombo/semver/releases https://github.com/mojombo/semver/releases
- mikmoila 11y agoHow about interface implementation versioning Ae la OSGI http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pd...
- nickpresta 11y agoI find well written changelogs far more useful than relying on encoding meaning in a version string. I really like http://keepachangelog.com http://keepachangelog.com as a guideline for writing changelogs.
- kelnage 11y agoIs there any harm in doing both? I agree that good changelogs are incredibly helpful - but I can also see how consistent version numbering can be useful too. If nothing else, it can allow easier automated dependency management vs. parsing the contents on a changelogs.
- nickpresta 11y agoI'm of the opinion that if you're relying on semver for automated depenency management (like npm), you're doing it horribly wrong. Pin your dependencies to specific versions, read changelogs and make informed decisions. Don't rely on someone bumping patch versions correctly to keep your software stable. I tend to agree with Jeremy Ashkenas on this issue: https://gist.github.com/jashkenas/cbd2b088e20279ae2c8e https://gist.github.com/jashkenas/cbd2b088e20279ae2c8e
- RickHull 11y agoThis doesn't help with dependency management. Changelogs, no matter how well written, cannot replace semver in e.g. Ruby / Rubygems / Bundler version constraints: https://robots.thoughtbot.com/a-healthy-bundle https://robots.thoughtbot.com/a-healthy-bundle