After looking at it again (I was only looking at the CI job that was failing) I notice that the work is being done in a separate branch. I would still prefer that any work be done in someone's own fork and pull requests created for any desired updates.
On Mon, Aug 25, 2014 at 2:21 PM, Slide <[email protected]> wrote: > There have been a couple times recently where someone from Cloudbees has > made changes to email-ext without consulting with me as the maintainer of > email-ext. Just recently tfennelly made a change to the parent pom version > with no consultation. I consider this to be unacceptable. > > Any changes to plugins should go through the plugin maintainers (through > PR's is fine), regardless if it is a plugin that is heavily used in the > enterprise Clousebees offerings. > > I'm planning on reverting the changes made, as the policy for email-ext is > to track the LTS version of Jenkins, not the latest. > -- Website: http://earl-of-code.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 [email protected]. For more options, visit https://groups.google.com/d/optout.
