In order to make the collaboration on tests stored in the tests namespace easy it would be good to have ability to track test-related issues (test bugs, ideas for improving the test coverage). Currently, Pagure has the "issues" feature disabled for the whole dist-git, that means for all namespaces.
dist-git
While for rpms namespace this makes sense (component bugs should be filed to Bugzilla), for the tests namespace it would be best to store issues close to the test source code, that is directly in the Pagure. So the proposal is to enable issue for the tests namespace.
rpms
tests
One of the options would be to allow repo admins to enable issues when needed.
Yes please!
@pingou, what do you think about allowing issues on a per-project basis. That is keeping issues functionality off by default for dist git as a whole but allow admins to enable issues for their individual projects if they need.
what do you think about allowing issues on a per-project basis
This isn't supported in pagure and this would require a discussion outside of this scope I think
Where would you suggest to discuss this, @pingou?
We should open a RFE ticket on pagure itself :)
I am not sure I understand, @pingou. In the admin settings there already is an option to enable or disable the issues feature of pagure. So if, for the whole dist-git, this option is set to disabled and the global restriction removed we would get what we need: By default all repos would have issues disabled and individual admins would be able to turn on the issue tracking if desired. What RFE for pagure did you mean?
In the admin settings there already is an option to enable or disable the issues feature of pagure.
This impacts the entire pagure set-up and it has been made clear that Fedora does not want to have issues reported against RPMs on src.fp.o (and does not want to offer the option to change this).
The RFE needed is to allow pagure to have issue trackers on only some namespace (ie: we would turn on issue trackers only for a set of namespaces).
Pagure issue for reference: https://pagure.io/pagure/issue/4244
@pingou The Pagure issue was released in Pagure 5.3, and src.fedoraproject.org is now running Pagure 5.7
Is there anything else needs to be done to enable the issues tracker for tests/*?
Just a configuration change. Let's put this in an infra ticket, it will require a freeze break request or wait for post-freeze :)
Filed https://pagure.io/fedora-infrastructure/issue/8195
Done \o/
@psss I guess this can be closed, right? :)
Metadata Update from @bgoncalv: - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.