On Tue, Feb 3, 2026 at 12:02 PM Jan Faracik <[email protected]> wrote:
> Moving to 3.0 would indicate to me a new major release > Which IMO is something we want to avoid, as it implies dropping at least some level of compatibility with 2.x, which I hope is not being proposed. (Any weekly release inevitably runs the risk of regressing compatibility, the more so when major changes are being made. But we should expect developers to proactively test for this and only break compatibility for specific plugins/scenarios when there is no reasonable alternative that allows the code base to move forward, and then only with plenty of preparation and warning.) We should not have adopted the 2.x convention either. The idea at the time had been to advertise Jenkins Pipeline and some vaguely expressed new way of using Jenkins, but in fact Pipeline was compatible with many 1.x versions. In reality the main functional changes in 2.0 compared to the last 1.x version was a setup wizard which may be nice (if you are not using CasC) and a revised GUI for New Item. No fundamental changes in the capabilities of the application or its everyday usage. There are all sorts of ways to promote improvements to Jenkins. I do not think the version number should be used for this purpose. -- CONFIDENTIALITY NOTICE:_ This email and any attachments contain confidential and proprietary information of CloudBees intended only for the named recipient(s). Unauthorized use or distribution is prohibited. If you received this in error, please notify the sender and delete this email._ -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0TgH3L4%3DTpfPZF8yFvjZdkGQyWK1ryY2v%3DNr0n4%3DoLkg%40mail.gmail.com.
