Re: 2.426 as Nov 15, 2023 LTS baseline?

Tim Jacomb, can you confirm that 2.426 is approved as the next LTS baseline? Thanks, Mark Waite -- 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 jenkinsci-

Re: Backporting for LTS 2.414.3 has started

I would like to propose backporting a documentation change [0], ensuring the installation pages match the instructions on jenkins.io . Additionally, a remoting PR has been labeled as “backporting-candidate”. [0] https://github.com/jenkinsci/packaging/pull/435 [1] https://gith

Re: Splitting a plugin into a legacy and supported part

On Fri, Oct 13, 2023 at 2:38 AM Ullrich Hafner wrote: > there might be still some users that use the old and deprecated steps > Like, Pipeline steps? So you cannot confidently delete this code without potentially breaking user workflows? > Move the old code to a new plugin with new plugin id.

Re: Splitting a plugin into a legacy and supported part

On Fri, Oct 13, 2023 at 8:38 AM Ullrich Hafner wrote: > Or is there even anotheroption that I do not see? > Depending on the scope of the problem, deprecation and finally removal of the obsolete stuff you want to remove. Use usage-in-plugins to identify callers and consider providing PR