In fact, I do not understand the motivation behind this. You care for
reviews so much that it takes several Jenkins veterans to incorporate
trivial javadoc change, though you are fine if other people merge changes
(that will eventually find its way into your product) without any review.
To me, it seems it would make more sense for CloudBees to focus on
improving overall review disciple in whole jenkinsci organization. I would
be much happier with @reviewbyjenkinscore, and I am fine considering all
bees Jenkins core contributors for reviewing purposes.
I do not object against your procedure as it is still will be an
improvement for Jenkins, though it seems odd.
--
oliver
--
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/op.x05ywl1usbfict%40localhost.localdomain.
For more options, visit https://groups.google.com/d/optout.
