On Mon, May 23, 2022 at 12:18 PM Ullrich Hafner <[email protected]> wrote: > > As mentioned several times before I think that using or allowing 2 different issue tracker systems for *any* Jenkins component (core and plugins) is a mess for users and developers.
Indeed, though at least the mess is mitigated for plugins through the use of appropriate links such as "Open issues (Github)" or "Open issues (Jira)" on the Plugin Site. This helps users to know where to go, though the problems with project management (tracking projects that span multiple plugins) and issue triage (being able to efficiently move an issue from the incorrect component to the correct component) remain. In contrast, the Issue Reporting <https://www.jenkins.io/participate/report-issue/> page clearly assumes the use of Jira, so it is natural for users to file tickets for core and core components in Jira since we do not direct them anywhere else in the documentation. That is why I am asking for us to (a) stop accepting new issues on GitHub for all core components and (b) move any existing core component issues from GitHub to Jira. This at least restores the working status quo for core and core components by using a consistent issue tracker for both that also matches the documentation and restores the project management and issue triage use cases mentioned above. I am defining "core component" as "any component whose developer list in RPU includes @core". -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjoM_Pr9DrZvmGcfkg9owzeTNJ1N2RBjXegX-JoYY3pDyw%40mail.gmail.com.
