Thus spake Ulli Hafner: > Wouldn't it make more sense to commit your changes to the existing plugin and > take over the ownership? Then users need not to replace plugins and migrate > their jobs.
The old plugin is in an SVN repo somewhere, and I've already broken backwards compatibility. A new plugin seems like a better option IMO? - Nim -- 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.
