In https://github.com/jenkinsci/winp/pull/71 I have proposed a path forward that, while certainly not ideal for consumers outside of the Jenkins project, matches the path of least resistance that we have already taken with file-leak-detector, mock-javamail, maven-jellydoc-plugin, maven-stapler-plugin, and other repositories adopted from Kohsuke. This path is achievable by me in the short term and unblocks the Jenkins project to deliver fixes for e.g. JENKINS-69647. If and when someone volunteers to improve the winp build, test, and release process even further as described in that PR, their contribution(s) would be most welcome.
-- 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/CAFwNDjrKTF3OCeZDcb85_RQUFnv-6-kJvjaazJEyv%2BC8Q9MZaQ%40mail.gmail.com.
