[Request] Follow Semantic Versioning Conventions

It 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

[bbakermmc]

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.

[whithajess]

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 <[e-mail] wrote:

I would say that generally it’s pretty inconsiderate to the ~15000ish users that will be upgrading to make them “pay special attention” to a release that is no different to any of the MINOR releases before them

No, it would be inconsiderate for ABP to introduce non-bugfix breaking changes in a minor or patch release. But the major version change introduces new features, provided free of charge to the users.

On the other hand, it is inconsiderate for you to demand that an open source project changes the way it releases versions to fix your

whether its a revert or bugfix that I would sill mark this a Major

Then you’re not following SemVer either.

when it breaks something they were using unexpectedly.

Do you mean exploiting undocumented behaviour? That is at the user’s own risk.

And that all of it could be avoided by just following the actual conventions more closely.

Again, the versions that you have taken issue with appear to be in accordance with SemVer.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/aspnetboilerplate/aspnetboilerplate/issues/4194#issuecomment-455431077, or mute the thread https://github.com/notifications/unsubscribe-auth/AB-SHQIJUojOumt2aGKFvrbWRrTbZDK6ks5vEVnJgaJpZM4aG6Pn .