There will be confusion for version like 1.3.0-20170208 before 1.3.0 signed off to release, although it’s a 1.3.0 RC build( release candidate )
But removing the X.Y.Z from the version string is not a best solution. Rational as attachment slides.
Slides also found in Confluence: RackHD-Nightly-build-Versioning.pptx
Summary( more detail in slides)
- X.Y.Z in nightly build is meaningful and helpful to user
- It is Industrial common practice : example
- For confusion during “rc” period. Solution is -- defer “version bumping” until final release tagging
Atlas vagrant boxes will not follow this naming convention for nightly builds. They will follow the convention v0.MM.DD.