[cargo-smart-release] Pre-release support

[jcornaz]

I see in the readme that support for pre-releases is planned. But after looking at the code, I saw some strange uses of the word "pre-release", and I am wondering what is meant by "pre-release" in the cargo-smart-release readme.

Is it "pre-release" in the semantic-versionning sense, like 1.0.0-alpha.1?
Or is it more initial development phase like 0.1.0?

I would be especially interested in support of the former (actual pre-releases, like 1.0.0-beta.1). :-)

[Byron]

Thanks for bringing this up! I wouldn't be surprised if the usage of pre-release is ambiguous in these texts, but believe they should consistently refer to pre-1.0 crates. Maybe there is an official term for that, so the usage of the word could be fixed and made less confusing with what semver prescribes.

Settling on the official meaning here, the code incrementing a version indeed cannot handle pre-releases yet. There is another relevant piece of code to determine if a version change is breaking which would probably also need adjustments.

[jcornaz]

Thanks for the answer. :)

Maybe there is an official term for that

The semver faq names it "initial development phase". It's not really a great name. But it's less loaded than "pre-release", which is more formally defined in the semver specs.

[Byron]

Thanks for the hint! I did my best to update the wording of every usage of 'pre-release' where appropriate, and it's definitely for the better. See 498072e for the change.

[jcornaz]

Looks great. Thanks for the clarification.

I think you missed this line which, btw also has a broken link. Probably you want the link to point to https://github.com/Byron/gitoxide/blob/main/STABILITY.md?

[Byron]

Great catch! I gave that one another shot now :D: 375cd12 .