On Thu, 2020-11-19 at 14:41 +0100, Kamil Paral wrote: > > People often add a hyperlink to the criterion in question (not using Adam's > anchors, just ToC links, but that's fine) to a Bugzilla comment. At least I > do it almost always (when I know which criterion to use, sometimes I > don't). But I'm not sure how it helps. We can't enforce it (we don't want > to prevent people from proposing blockers just because they don't know > which exact criterion applies). The BBA proposal form is used only > sometimes, many people propose it directly through Bugzilla, which is a > free-form text field. And even the criterion that gets cited originally is > often not considered the appropriate one. So if you want to vote, you still > need to read the whole discussion (not necessarily the technical bugzilla > discussion, but certainly the blocker discussion in our blocker-review > Pagure repo, and at least the comment in Bugzilla which nominated the bug). An ugly hack would just be to catch any time a comment on the bug links to a criteria page with a URL fragment, mirror that link as a comment on the issue with generic framing text, like this: === blockerbot commented a minute ago Release criterion mentioned in bug report by kparal: https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria#Remote_package_sources === If such a link is included in the bug report at the time blockerbot creates the issue, it could be incorporated into the initial issue description. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx
