On 6/11/20 8:32 AM, Slide wrote:
The big problem with GitHub issues is when a bug involves multiple components, or is filed against the wrong component. If you filed an issue in the wrong component, what would you expect the maintainers of that component to do? I don't think it should be on them to find the right component, so the issue just gets closer and possibly not seen by the correct people? I definitely prefer GitHub issues, but we need to address some issues like I describe above.
These are the big issues with moving away from a system-wide tracker to individual trackers. Jenkins is a system of interacting components and issues may involve multiple.
As Remoting maintainer I see this frequently. Someone may submit an issue against Remoting, but often it has to do with a plugin and just shows up in Remoting. Eventually Remoting is removed from the components list and the correct one is assigned. Then the maintainer of that one has notification. Sometimes it helps define the problem. Someone submits the issue against Remoting and a plugin that might show up in the stack trace or messages. I look at it and have no idea, but the maintainer of the other component quickly identifies it.
Sometimes something is submitted against core but we decide it needs to be fixed somewhere else. Or vice versa.
And then there are security issues. We manage security issues as a Jenkins system.
If we switch to tracking issues solely by individual component we're going to lose track of a lot of things. Well, a lot more than we already do.
Jeff -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/888f8585-767d-b195-8e77-307d3f03c82c%40cloudbees.com.
