On Thu, Jan 30, 2020 at 11:26 PM Michael Schwendt <mschwendt@xxxxxxxxx> wrote: > > On Thu, 30 Jan 2020 14:44:50 +0100, Kevin Kofler wrote: > > > Fabio Valentini wrote: > > > Until this functionality is merged into pagure's dist-git plugin, there is > > > a way, but it's a bit convoluted. > > And it's too obscure. Instead, I just retired the two EPEL branches. Did you at least check if the packages were used by something else? ... And as I said, a new self-service UI for setting bugzilla overrides for Fedora branches vs. EPEL branches is being worked on for src.fedoraproject.org. > > And we have to do that for every single package we maintain? That is not > > reasonable. It is Fedora policy that we cannot be forced to care about EPEL. > > The software needs to actually implement that policy. > > With pkgdb I could see who maintains which "branches" and which branches > exist. With this new web UI, I don't find where I could take a look at > who maintains which branch. For some packages I see socalled "members", a > "main admin", an "admin", people with "commit" access, but without any idea > who maintains which branches. That's because per-branch maintainership is no longer "supported", as mentioned on recent other threads. It seems the "support" in PkgDB was also a "lie", because BugZilla doesn't even support default assignees per-branch. > All this would not even interest me at all, but almost a week ago someone > from Red Hat Security decided it would be a good idea to assign to me > (without asking first) ancient EPEL tickets, which are almost five years (!) > old. Apparently, no proper tracking of those tickets has been done for a > very long time. It is entirely wrong and unexpected to assign those EPEL > tickets to me only because something under the hood knows only a default > assignee or such. For new tickets, I'd understand this. But for old tickets to get reassigned to you - I agree that that's weird. I wonder who the previous assignee was, and why it was decided to reassign now, after 5 years? Fabio > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
