[RFC] code name support

[practicalrs]

Support the following

[package]
name = "mbdf"
version = "0.2.0"
edition = "2021"
code_name = "Bailey"

Rendered

[Turbo87]

There is nothing stopping people from already declaring a certain major version number as "Codename: Ace" or something like that. The only thing that they currently don't get is these codenames being visible in cargo and crates.io, but I'm not sure the additional work and complexity is worth the IMHO very small benefit of this feature. Authors are already able to use these codenames in the README (rendered on crates.io) and in their doc comments (rendered on docs.rs).

[Turbo87]

Windows 95 might also refer to v4.0.951 and v4.1.234 though. I guess it's more like a grouping of versions, not a singular version.

[practicalrs]

Yes, that is why I wrote "and for each major or minor release" - depends on the convention that you want to use.

[epage]

To add, there is the metadata field in the version number that can be used for this.

[weihanglo]

While not highly relevant, I have a feeling that we tend not to add more “metadata-like” fields to Cargo.toml. We've deprecated [badges] table and made package.authors optional. I'd like to know more on why we need a standardized field of it, otherwise package.metadata seems sufficient.

[ChrisDenton]

To add, there is the metadata field in the version number that can be used for this.

I wasn't aware of this but you can indeed do 1.0.0+nickname. I couldn't find it mentioned in the Cargo docs but the semver spec has this: https://semver.org/#spec-item-10

[practicalrs]

Ok, let's close it.

Thanks for all the comments.