I think it's a good idea. In the same spirit than 1.x -> 2.x (We justify the bump by the risk to impact a large number of plugins)
On Thu, Nov 26, 2020 at 9:29 AM Ivan Fernandez Calvo < [email protected]> wrote: > +1000 to considered those changes as a major change > > El miércoles, 25 de noviembre de 2020 a las 17:37:21 UTC+1, James Nord > escribió: > >> Hi all, >> >> with the recent weeklies we have a couple of changes (Acegi >> upgrade/table-to-div) that break compatibility in plugins. >> >> Whilst many open source plugins have been updated and made compatible >> with the old and new version by the people making the changes (and >> compatability layers have been added as far as possible), there can be >> closed source ones that we have no sight of that can be broken. >> >> Given this is an API compatibility breakage, I am wondering why don't we >> bump the version number to Jenkins 3.x to signify the breaking API? >> >> Regards >> >> /James >> > -- > 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/3929b9b0-d36b-4eb7-bc46-81fc01e7c21en%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/3929b9b0-d36b-4eb7-bc46-81fc01e7c21en%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- Arnaud Héritier Twitter/Skype : aheritier -- 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/CAFNCU-8n8qzP0NZrAazGkg-U7Anf2Mrz1ZCgbUoqiJjz4LeWCA%40mail.gmail.com.
