https://bugzilla.redhat.com/show_bug.cgi?id=1975859 --- Comment #6 from Ben Beasley <code@xxxxxxxxxxxxxxxxxx> --- > But, is it really necessary if the original review request cannot be accepted because it does not package the latest version? Also, is a situation like this (duplicate review request) documented anywhere? I think it’s not-quite-explicitly covered by the policy: > The idea is to move the ticket to a state where other interested parties can submit the package or take over the review. If the stalled package process completes and their bug is closed: > If the bug is resubmitted by someone else, it is also reasonable to change the resolution on the closed bug to DUPLICATE and mark it as a duplicate of the new bug so that reviewers of the new ticket can easily find the work that was done on the old one. If the original submitter responded within the allowed time and updated their submission to the latest version, they could proceed, and your bug would be the duplicate. I’ve been in your position recently; in that case, the other submitter did come back and encourage me to proceed with my version instead. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
