> On 14.11.2016, at 08:06, Johann Ollivier Lapeyre > <[email protected]> wrote: > > i'm really thinking we should have only one zaproxy-plugin and one community > to take care of it.
Goran has implemented a major, incompatible refactoring (as in, all existing plugin data in users' Jenkins instances cannot be loaded anymore). I suggested that rather than create an incompatible version 2.0 which comes with configuration data loss, it should be a new plugin, allowing users to migrate incrementally, and optionally declare the existing plugin deprecated and stop distributing it (or perhaps add a message to it, telling users to install the other plugin and migrate their jobs). -- 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/3A3F97F0-0DDF-483C-9E7B-8283B5B84DEE%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
