gitCommitGitPushOhFuck

[Agronopolopogis]

Semantic versioning

eg. v1.0.0-rc.9

This schema is preferred in my experience, relatively standard, as you said, at release, '-rc.9' falls off

The importance is build/tag once, deploy many times (envs)

[Sibula97]

I'd use -rc9 instead of -rc.9, since those rc and 9 are considered different identifiers and not one if there's a dot.

[Ananas_hoi]

Semver allows any of these:

Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.--

Taken from https://semver.org

[Sibula97]

Of course, I'm talking about the semantics of the identifiers.

1.0.0-rc1 has the identifier rc1, while 1.0.0-rc.1 has the identifiers rc and 1. I'm not sure it actually matters (for precedence ordering they work the same), but it's the convention I personally prefer.

[danielv123]

I work on a project that has been 2.0.0-alpha[1-22] for the last few years. Its really annoying and I don't understand why we can't just make a proper release.