Documentation comments from a newbie crate publisher

[sttaft]

I have successfully published my first crate ("lwt" -- light-weight thread scheduler) for Alire (yay!). Along the way I will admit I found the documentation of the process a bit frustrating. Here is what I was missing:

• What is the expected process for approval of a new crate? (apparently, there are a couple of kind people who notice the attempt to publish, and review the result)
• What happens if you "fail" the first time? How do you fix a failure? Can you simply edit your sources and/or the ".toml" file and re-publish, or do you have to start doing GitHub things explicitly? (apparently it is the latter -- it would be nice if that were unnecessary, perhaps by simply adding a flag to "alr publish" to say this is to be a new commit for a pending publishing attempt)
• What is the process for producing a new version? Do you make your changes and then just edit the ".toml" file to change the version number? Do you just re-publish, or is there some separate command or flag for publishing a new version? (apparently you just re-publish, though again, the process for handling a failing review is unclear)
• When you publish a new version, where do you document the enhancements or bug fixes? The github log associated with the ".toml" file does not seem to be included anywhere in the index. Is there a "best practice" about where the enhancement/bug-fix log should go? Should it go into the description part of the ".toml" or should that include a link to more documentation? (It might be nice to see such a log before deciding whether to update to a new version)

That's all I can think of now, but my guess is that first-time crate publishers might have other comments about the process and any associated mysteries they encountered.

[sttaft]

Another item has to do with tests associated with the crate. Is there a best practice here? Somewhere I found a description of the [test] part of a ".toml" file, but it was not included in the main set of documentation provided on publishing a crate.

[mosteo]

I found a description of the [test] part of a ".toml" file

This is a new feature in the upcoming 3.0 release, so not yet usable in general, and missing from the website, which uses the latest stable branch as source.

As for the rest, I'm going to convert this into an issue so we have it closer in the radar.