> On 21. May 2018, at 10:06, ogondza <[email protected]> wrote: > > The backporting window is closing this Wednesday. There ware no candidates > nominated (likely due to recent baseline choice) BUT there is the outstanding > problem of JENKINS-51253[0]. > > There does not seem to be a consensus on whether/how to fix it[1] so I am > wondering which version of remoting we prefer to use for 2.121 LTS. I lean > towards using pre-JENKINS-45287[2] remoting - before the regression was > introduced. But there are alternatives of shipping current master or > expediting the fix. > > Thoughts? > > [0] https://issues.jenkins-ci.org/browse/JENKINS-51253 > [1] https://github.com/jenkinsci/packaging/pull/107 > [2] https://issues.jenkins-ci.org/browse/JENKINS-45287
I assume s/remoting/packaging/g here, otherwise I'm really confused. The current packaging (or at least the bits that don't declare a Java dependency) has been used in weekly releases for a long time successfully, and probably for the 2.89.x line and older as well. We document the intended behavior on the repo index page (see PR discussion). It's just an oversight that resulted in the outdated packaging being used for 2.107.1 and 2.107.2. IMO we could mention this in the upgrade guide, complete with explanation similar to the package repo index pages, and done. No reason to diverge LTS packaging from weekly packaging deliberately. -- 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/891E05A0-1BEA-469E-BC14-6C66955EDE53%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
