[Request] Follow Semantic Versioning Conventions
See original GitHub issueIt would be awesome if abp stuck to Semantic Versioning conventions
Summary:
Given a version number MAJOR.MINOR.PATCH, increment the:
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
We routinely nuget update -safe
relying on the fact nuget packages we use follow the above rules and do not break our code.
This is the official advice for nuget packages: Nuget Package Versioning
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Semantic Versioning 2.0.0 | Semantic Versioning
Semantic Versioning 2.0.0. Summary. Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes ...
Read more >How to follow Semantic Versioning and Keep a Changelog ...
Keep a Changelog is a wide-used convention that brings some guidelines about the maintenance of a CHANGELOG.md file in repositories managed over ...
Read more >Semantic Versioning. Demystifying SemVer and avoiding…
Semantic versioning indicates the type of changes since the last release of a library, as well as if these changes break backward compatibility....
Read more >README - semantic-release
Following formalized conventions for commit messages, semantic-release automatically determines the next semantic version number, generates a changelog and ...
Read more >Introduction to Semantic Versioning
Semantic versioning (also known as SemVer) is a versioning system that has been on the rise over the last few years.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Or just move to date or year based versioning like the rest of the world. Ive learned that most of the time the version numbers mean nothing with the two projects. ABP V 19.1 or ABP V 2019-01-14 seem to have better meaning to me personally, Im not like well is v4.1.3 the new Dec 2018 release or what not.
As I said this conversation is going nowhere.
FYI we actually pay for a license to use aspnetzero which if I’m not wrong helps pay for the development of ABP.
On Fri, Jan 18, 2019, 6:21 PM Aaron Chong <notifications@github.com wrote: