On 09/21/2014 07:45 PM, Nim wrote:
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?
All the old SVN repos are mirrored on GitHub:
https://github.com/jenkinsci/job-exporter-plugin/
There are 1150+ users of the existing plugin, so taking the effort to
maintain backwards compatibility, even if it just means automatically
converting config to your new way of doing things, is the strongly
preferred option.
Regards,
Chris
--
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.
For more options, visit https://groups.google.com/d/optout.
