On Tuesday, September 15, 2015 at 2:04:54 PM UTC+2, Stephen Connolly wrote: > > > The security fixes are typically prepared in advance for this reason > and pushed to every branch at the same time to minimize exposure. If > we do not do the concurrent releases then LTS becomes vulnerable.
I understand that, though it is enough we dictate LTS users when to update (even if there is no other way, they are hardly happy about that). If those users can not rely there will be no breaking changes (even within one LTS line) it will hurt stability (because of the breakage we may caused) and security (as admins can postpone the upgrade because of the potential of breakage) IMO. What is the other side of the coin here? The fixes will be smaller and simpler for sure if we are allowed not to preserve BC in 100% of cases. Anything else? -- oliver -- 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/a2b2e18e-41d2-4c29-a1ce-03392a5b8509%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
