Not a big deal, I've wondered why all branches are tracked on jenkins.ci.cloudbees, I would think only master would be tracked. Don't worry about deleting the branch. If you have specific things you would like added, pull requests are great.
On Tue, Aug 26, 2014 at 3:22 AM, Tom Fennelly <[email protected]> wrote: > Okay... really sorry about that... I did make those changes on a branch > but I should have done it on a fork. I actually did create a fork after > seeing there was a build tracking branches. Let me know if I should delete > the branch I created - I won't touch anything until you let me know what > you want. Sorry again !! > > > On Monday, August 25, 2014 10:21:27 PM UTC+1, slide 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. >> > -- > 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. > -- 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.
