Hiyas,
for a few days I have given permission to perform buildroot overrides. There was now a request for a buildroot override in all branches including EPEL. Therefore I wonder whether I should do these, too, or just ask to create a new ticket for EPEL?
Regards Till
On Thu, 25 Feb 2010 23:57:48 +0100 Till Maas opensource@till.name wrote:
Hiyas,
for a few days I have given permission to perform buildroot overrides. There was now a request for a buildroot override in all branches including EPEL. Therefore I wonder whether I should do these, too, or just ask to create a new ticket for EPEL?
I would say it would be fine for you to do them as long as you know what you're doing. ;)
Ie, the tags are named slightly differently in epel.
We have:
dist-5E-epel-testing-candidate -> newly built dist-5E-epel-testing -> in testing dist-5E-epel -> in stable dist-5E-epel-override -> temp override for builds.
We also usually keep the ticket open after making the request so the submitter can tell us when they don't need it anymore, and we can untag the override. :)
If you would like to start doing them I have no objections.
kevin
On Fri, Feb 26, 2010 at 10:14:06AM -0700, Kevin Fenzi wrote:
We also usually keep the ticket open after making the request so the submitter can tell us when they don't need it anymore, and we can untag the override. :)
This is how it usually happens for Fedora, too. The workflow is not completely documented, except for how to check whether a request is sane: https://fedoraproject.org/wiki/Buildroot_override_SOP
A big / problematic difference is, that in EPEL the owner / state of the tickets are not changed if someone processes then. Therefore it seems not possible to query trac for unhandled trac requests. For Fedora there is a nice RSS feed for all unhandled koji issues. But there seems to be no way to get one for all tickets that do not have any comments.
If you would like to start doing them I have no objections.
So in case there will be another ticket for both Fedora and EPEL, does there need to be a seperate ticket in the EPEL component to track it or can I just track it in the Fedora ticket?
Regards Till
On Friday 26 February 2010 11:47:42 am Till Maas wrote:
On Fri, Feb 26, 2010 at 10:14:06AM -0700, Kevin Fenzi wrote:
We also usually keep the ticket open after making the request so the submitter can tell us when they don't need it anymore, and we can untag the override. :)
This is how it usually happens for Fedora, too. The workflow is not completely documented, except for how to check whether a request is sane: https://fedoraproject.org/wiki/Buildroot_override_SOP
A big / problematic difference is, that in EPEL the owner / state of the tickets are not changed if someone processes then. Therefore it seems not possible to query trac for unhandled trac requests. For Fedora there is a nice RSS feed for all unhandled koji issues. But there seems to be no way to get one for all tickets that do not have any comments.
If you would like to start doing them I have no objections.
So in case there will be another ticket for both Fedora and EPEL, does there need to be a seperate ticket in the EPEL component to track it or can I just track it in the Fedora ticket?
Regards Till
One big difference we have is that we use a koji group to grant permissions and you don't need to force the tagging operations. I have added you to the epel- override group.
Dennis
On Fri, 26 Feb 2010 18:47:42 +0100 Till Maas opensource@till.name wrote:
On Fri, Feb 26, 2010 at 10:14:06AM -0700, Kevin Fenzi wrote:
A big / problematic difference is, that in EPEL the owner / state of the tickets are not changed if someone processes then. Therefore it seems not possible to query trac for unhandled trac requests. For Fedora there is a nice RSS feed for all unhandled koji issues. But there seems to be no way to get one for all tickets that do not have any comments.
I suppose we could start reassigning them too... the downside there is that if the person who did the tag is busy/gone, further requests or issues in the ticket may be unnoticed by active taggers that could be handling it.
If you would like to start doing them I have no objections.
So in case there will be another ticket for both Fedora and EPEL, does there need to be a seperate ticket in the EPEL component to track it or can I just track it in the Fedora ticket?
I would think just one ticket would be fine. The fewer tickets the better IMHO.
kevin
epel-devel@lists.fedoraproject.org