DevHeads.net

Stalled Review Request - Close it and create new?

Recently I began to create a review request for netatalk, when I noticed there already was an open review request:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1520024" title="https://bugzilla.redhat.com/show_bug.cgi?id=1520024">https://bugzilla.redhat.com/show_bug.cgi?id=1520024</a>

May 7th was the last activity by anyone other than myself. On 11/28 I offered assistance to help move the review along, but I have not received an answer.

In the interested of getting this review completed, am I in my right to close this request and create a new one, or is there better course of action?

Comments

Re: Stalled Review Request - Close it and create new?

By Jason L Tibbitts III at 12/04/2018 - 17:19

AB> In the interested of getting this review completed, am I in my right
AB> to close this request and create a new one, or is there better
AB> course of action?

If you have a package ready to go, then certainly just close the old
review ticket. If someone is upset by that then they can simply help
you review the package you're submitting or offer to co-maintain it with
you.

Also do note that netatalk has been orphaned since 2016, so in addition
to the package review, you will need to file a releng ticket to get the
package unblocked so that you can build it again. See:
<a href="https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package" title="https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package">https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainer...</a>

- J<

Re: Stalled Review Request - Close it and create new?

By Dan =?utf-8?B?x... at 12/04/2018 - 17:16

Afaik the recommendation (at least for maintainers not responding to
bugreports) is to wait at least two weeks (in case someone is on
vacation), so I'd maybe wait at least until the end of the week before
taking further action.

"Andrew Bauer" < ... at outlook dot com> writes: