The "Versions" field for editing a package implies its for specifying multiple different versions of the same package, and that a user can somehow pick a specific version to install / depend on or constrain the version using some semver-like system. But it's actually for version exceptions which provide different versions of the same package based on what Racket version a client is using. There are some packages who have confused it for the former, including the herbie package with "1.0" and "1.1" versions (which will never be used). Changing the field name to "Version exceptions" and maybe making it link to the appropriate docs about version exceptions might help.
jeapostrophe
commented
6 years ago
The "Versions" field for editing a package implies its for specifying multiple different versions of the same package, and that a user can somehow pick a specific version to install / depend on or constrain the version using some semver-like system. But it's actually for version exceptions which provide different versions of the same package based on what Racket version a client is using. There are some packages who have confused it for the former, including the herbie package with "1.0" and "1.1" versions (which will never be used). Changing the field name to "Version exceptions" and maybe making it link to the appropriate docs about version exceptions might help.