Nice, and thanks for the information. I was recommended to add jenkinsci code-reviewers but perhaps this is not necessary for the low scale plugins I am working on as things have been working fine up until now.
PS - I accepted the invitation now to join jenkinsci (email got lost) On Thursday, 5 January 2017 18:01:36 UTC+2, Daniel Beck wrote: > > > > On 10.08.2016, at 08:42, James Dumay <jdu...@cloudbees.com <javascript:>> > wrote: > > > > All of the blueocean-plugin PRs mention the reviewers team... so If you > are looking to get involved in Blue Ocean reviewing is a great place to > start! > > FTR I asked that this practice be stopped a few weeks ago, as it increased > the notification traffic a lot, and the BO developers generally seem to > have no problem finding reviewers for their changes. > > Now @jenkinsci/code-reviewers should be back to be fairly low traffic and > limited to PRs where someone really thinks reviews are needed: > > > https://github.com/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+team%3Ajenkinsci%2Fcode-reviewers > > > -- 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/09926995-796e-4a27-a160-0554a2af9665%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
