Fully aware I haven't always been consistent personally, but I have been trying to consistently refer to our versioning as:
-
Product v0 (because Product 0 or Product 0.0 looks weird, and the v feels more technical/representitive that it's pre-release)
-
Product 1.0 (because 1.0 is a known "first release") and later (Product 1.1, Product 2.0, Product 2.6, etc.)
-
Tag: bare semver with at least major.minor e.g. 0.0, 0.0.2, 1.0, 1.0.1. 1.1
I also think using uppercase-V "Product V0"/V1/V1.0 looks weird and is uncommon in versioning. Same with "Product V.1".
This is how I've been trying to refer to things in repos and w/the community, at least. We should write it down somewhere in the docs.
Fully aware I haven't always been consistent personally, but I have been trying to consistently refer to our versioning as:
Product v0 (because Product 0 or Product 0.0 looks weird, and the
vfeels more technical/representitive that it's pre-release)Product 1.0 (because 1.0 is a known "first release") and later (Product 1.1, Product 2.0, Product 2.6, etc.)
Tag: bare semver with at least major.minor e.g.
0.0,0.0.2,1.0,1.0.1.1.1I also think using uppercase-V "Product V0"/V1/V1.0 looks weird and is uncommon in versioning. Same with "Product V.1".
This is how I've been trying to refer to things in repos and w/the community, at least. We should write it down somewhere in the docs.