search

paritytech / prdoc

prdoc files are YAML files following a defined schema and helping with code change documentation.
MIT License
11 stars 1 forks source link

Renamed and merged crates #40

Closed mutantcornholio closed 1 month ago

mutantcornholio commented 1 month ago

@chevdor still owns the package on crates.io, and refuses to allow parity to publish it

And maybe instead of two crates, we only need one?

WDYT?

Fixes #36

ggwpez commented 1 month ago

Release engineering can also publish it: https://crates.io/crates/prdoc

mutantcornholio commented 1 month ago

However, we can't use Parity's user to publish it.
As far as I understood it, I'd have to ask @Morganamilo or @EgorPopelyaev for their crates.io token to keep publishing it. Just as well as Will can revoke the access at any time (which seems probable, as he refuses to cooperate), and we can't do anything about it.

ggwpez commented 1 month ago

I spoke to Will and confirmed that it is okay to remove Rel-Eng as publisher and that Parity should fork.
Then please go ahead with renaming the crate and setting up the publish pipeline again with the new name: parity-prdoc.
Maybe we also rename the repo here, not sure.

PS: We could keep the binary name backwards compatible, so that it installs two binaries: prdoc and parity-prdoc. Then it would not break workflows.

mutantcornholio commented 1 month ago

PS: We could keep the binary name backwards compatible, so that it installs two binaries: prdoc and parity-prdoc. Then it would not break workflows.

Why not just keep producing a single prdoc binary?
Two identical binaries seems a bit weird and excessive.

Maybe we also rename the repo here, not sure.

I think maybe just mention it in README and that's all? paritytech/prdoc still has "parity" in the name.