> On 27. Nov 2020, at 18:26, James Nord <[email protected]> wrote:
>
> Could we maybe keep the discussion here to just a 3.x bump as we are more
> likely to reach a consensus?
As a technical/compatibility indicator, 3.0 makes little sense because it's
late. None of the related documentation would even say "from Jenkins 3.0" (if
it did, it would be wrong). Plus there's no commitment to semver in the future,
making this not even useful from an admin POV as an indicator that we're going
to apply semver in the future. It might even be actively bad to create an
expectation that incompatible changes bump the major version the next time we
integrate a big change. People who read the documentation before updating will
see huge warning signs either way, and can make an informed decision. People
who don't will experience the same pain either way.
As a marketing/"there's big new stuff" indicator, I don't think there's enough
big new stuff here from a regular user POV. Ideally XStream and Spring work
without a ton of problems (and do we really want to highlight how bad things
were until now?), and tables to div is nice but not on the scale I would expect
as a user to justify the major version bump. All these changes are mostly
internal, with some nice but overall modest visual updates to the configuration
forms. Not to mention we'd need a solid plan for announcements, documentation,
etc. -- a lot of that nature was done for Jenkins 2.
To me, this idea comes at least a month late, probably two, and going for it
unprepared will just cause problems, while not actually accomplishing much.
--
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/DF8247AA-3945-4720-8E73-D050C16383A9%40beckweb.net.
