Hi, Following this procedure. https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers I am requesting some progress on #1457856 in particular.
https://bugzilla.redhat.com/show_bug.cgi?id=1457856 link to bug.
Thank you very much for starting this process Steve! I would be happy to contribute to the maintenance, however possible. I have put in requests to the current maintainer over the last few months but haven't been able to get a response. Thanks again!
[I appear to be missing Fedora notifications, but I don't think I'm the only one who can't make that work.] I'm unclear what happens with joint maintainer requests these days, but I can't see anything in pagure, if that's the right place. What do you want to do with maintenance? I don't think it should just be pushed out as-is, and I haven't had a chance to go through the current version for at least the issues I found previously. Why is a new version so important? I'd assume it would be mostly relevant for EPEL, not Fedora, and it probably wouldn't satisfy the EPEL update policy.
Thanks for the response. In pagure you request access just via email or bugzilla currently. To grant brian or me (stevetraylen) access it's https://fedoraproject.org/wiki/Infrastructure/WhatHappenedToPkgdb#How_do_I_give_a_user_commit_access_to_a_dist-git_repo.3F Steve.
(In reply to Dave Love from comment #3) > I don't think it should just be pushed out as-is, and I haven't had a chance > to go through the current version for at least the issues I found previously. > > Why is a new version so important? I'd assume it would be mostly relevant > for EPEL, not Fedora, and it probably wouldn't satisfy the EPEL update > policy. Let's discuss these questions in ticket #1457856 where the update to 2.3.2 is requested.
Thanks for the response closing this ticket.