On 01/12/15 16:52, 'Jesse Glick' via Jenkins Developers wrote: > On Tue, Dec 1, 2015 at 5:32 AM, Baptiste Mathus <[email protected]> wrote: >> plugins forked under the Jenkinsci org, BUT still maintained elsewhere > > There are a number of such cases where the @jenkinsci fork is out of > date. There are even cases where both the original and fork repository > are configured to accept pull requests, which is quite confusing. > > Also in some cases the GitHub issue tracker is enabled (inside or > outside @jenkinsci), and there are some issues filed in JIRA too, > which is again confusing.
I guess being able to make plugin releases (exclusively?) via Jenkins-on-Jenkins would solve this problem? :) In any case, it would definitely be good if clicking on "Source code" on the wiki led to the place where the *most recent release* was made, rather than pointing to some abandoned fork. Whether that means source code needs to be exclusively hosted under @jenkinsci, I'm not 100% sure, but doing so would certainly have a lot of benefits. Regards, Chris -- 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/565E0F62.605%40orr.me.uk. For more options, visit https://groups.google.com/d/optout.
