On Thu, Jun 30, 2016 at 3:04 PM, Oleg Nenashev <[email protected]> wrote:
> If remoting 2.60 didn't get into the RC, I would vote against bumping the > version without re-spinning RC. If we don't want to re-spin the RC, it > should be perfectly fine to keep the version as is. > > All 2.60 fixes are actually [node/client]-side fixes, so Jenkins users can > get them by updating slave.jar files. > If you are using ssh slaves you have to not use the automated deployment/update of the slave.jar which is not easy if you have many slaves It is the main issue for people who are using JNPL slaves because they have to keep them up-to-date manually > > BR, Oleg > -- 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/CAFNCU--tb8Oh72H%2B1-qYBhudQf4iN9Ug1JsL2_nxyWt6gt647Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
