Nue uses Pragmatic Versioning until it reaches v1.0

[tipiirai]

Just a general note that Nue is using pragmatic versioning so that the version numbers follows this pattern:

MILESTONE.MAJOR.MINOR[.PATCH]

where

• PATCH is a super minimal fix, like a typo somewhere. This is optional: for example the README can change without changes on the version
• MINOR changes when there is any kind of contribution that impacts functionality
• MAJOR when there is a significant new feature or a breaking change
• MILESTONE changes when a significant goal is reached, such as 1.0 when Nue will be production ready

[goblinfactory]

Hi @tipiirai

Since we're on/ you are ... still on version 0, may I suggest that after version 1 is released that any breaking changes will require approval by certain key people, who can avoid or veto the change instead recommending a way to feature switch the new behaviour in so that it's not breaking until the next major release?

Perhaps instead of a feature switch, we should encourage adding a check for the usage and throw or log a friendly error message so that the library user can know that Foo() has been renamed to Bar() etc.

While it's very simple to adopt pragmatic versioning at the start of a project, if the project gains momentum at an exponential scale as I suspect it will, then you may want to consider switching to semver after version 1 comes out so that engineers can safely upgrade to latest version automatically and use the latest features as things evolve and move fast without fear of breaking things.

Especially since we're going to change the world!

[tipiirai]

Hey @goblinfactory — this indeed sounds like a solid approach. Let's switch to semver after 1.0