Default App Versioning

[LorenzoVM]

Default apps should start at version 0.1.0 instead of 0.0.1?

0.0.1 infers that it is a bug release of version 0.0.0.

If many are as I, relatively new to coding and software development, it’s good to start with proper habits.

ref: https://semver.org/

[khalby786]

If you’re following semantic versioning, you can follow this thumb rule: MAJOR.MINOR.PATCH.

Also, since this is more of a tutorial, I’m moving this thread to #the-gallery!

[ihack2712]

@Semantic Versioning Specification (SemVer)

4. Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

@Semantic Versioning FAQ

How should I deal with revisions in the 0.y.z initial development phase?

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

Technically the semver specifications doesn’t require you to start at 0.1.0, but is is recommended in the FAQ. However the application should in its initial (development) phase only modify MINOR and PATCH versions.