Jenkins Test Harness is not a core component, it is a separate deliverable with its own release lifecycle Same for other developer tools AFAICT
On Wed, Apr 27, 2022 at 11:43 PM Basil Crow <m...@basilcrow.com> wrote: > Strong -1 from me. Using GitHub issues for core components but not > core itself makes it impossible to do project management in a single > view (Jira epic or GitHub project) that covers both core and core > components. Additionally, there is no way to define causal > relationships or dependencies between GitHub issues, which is also > essential for project management. Please roll back whatever change now > prevents me from creating new Jira issues for core components. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/9sZipk1PHns/unsubscribe. > To unsubscribe from this group and all its topics, 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/CAFwNDjpy_QzJ0v4RqUJkDw2migG_RoaX856rJienKLgD%2BxVs%3DQ%40mail.gmail.com > . > -- 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/CAPfivLBm%3DkiYaz%2Bo%3DcHedERt1OGR9fLq14iaBNmzDNaC4LwX-g%40mail.gmail.com.
