Hi. I don't have a strong opinion although I tend to think more like Ulrich. Maybe the UI revamp would be a good inflection point, in addition to these breaking changes..
Anyway, I would like, when the time comes, to introduce semantic versioning <https://semver.org/#why-use-semantic-versioning>, adding a third number to the version and using them according to this way of versioning. In the future we can extend it to plugins and add some features in core to support / check / leverage this. Thanks! On Thu, Nov 26, 2020 at 12:56 PM Ullrich Hafner <[email protected]> wrote: > Aren’t we are a little bit late for it, since these changes are already > part of 2.x? Additionally, wouldn’t it be helpful if we have some > groundbreaking user visible changes in 3.x as well (as we had in 2.x)? > > Am 26.11.2020 um 09:47 schrieb Arnaud Héritier <[email protected]>: > > 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 > <https://groups.google.com/d/msgid/jenkinsci-dev/CAFNCU-8n8qzP0NZrAazGkg-U7Anf2Mrz1ZCgbUoqiJjz4LeWCA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > -- > 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/7E4AA979-7FBB-4712-BCE6-B24C28840F50%40gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/7E4AA979-7FBB-4712-BCE6-B24C28840F50%40gmail.com?utm_medium=email&utm_source=footer> > . > -- 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/CADN1OJ25c1K%2BrRbX9zf3oKBdrbsU3sSBYOiGLVA4pgW18QKrNw%40mail.gmail.com.
