Update branch procedure gpg link #300
Conversation
There was a problem hiding this comment.
I'm not 100% sure this is correct. We used to have documentation there, but in a cleanup it was dropped. https://web.archive.org/web/20210126123116/https://projects.theforeman.org/projects/foreman/wiki/GPG_Keys still has it.
These days we have scripts for it, so I wonder if we still need it. I think it would be better to include the still relevant information (like policies) somewhere in our README in this repo. Like expand https://github.com/theforeman/theforeman-rel-eng#generating-a-new-gpg-key-for-a-xy-release & https://github.com/theforeman/theforeman-rel-eng#generating-a-new-gpg-key-for-signing-the-debian-repository with the summary from the way back machine. Then drop the link here or modify it to point to the README.
Taking a step back: it's something I've thought about before. How do we keep the procedure light while still having reference documentation. If anyone has a good answer, I'd love to know.
|
Specifically on your point of " How do we keep the procedure light while still having reference documentation. If anyone has a good answer, I'd love to know."... At the moment I think we have about the best we can do from what I've seen. What to do, with embedded links to what it is and why we do it. It's always hard to find a good balance. |
|
This PR has been unintentionally superseded by #302 |
No description provided.