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. BR, Oleg 2016-06-30 14:43 GMT+02:00 Mark Waite <[email protected]>: > It appears that the 2.7.1 RC which I've been testing includes > remoting-2.59, rather than remoting-2.60. Oliver, can you confirm that is > intentional? > > Mark Waite > > On Wednesday, June 22, 2016 at 3:45:28 PM UTC-6, Oleg Nenashev wrote: >> >> Hi, >> >> Sorry for being a slowpoke. >> @Oliver @KK If you have not started the RC release yet, maybe makes sense >> to pick remoting-2.60. It contains several important fixes (see changelog >> <https://github.com/jenkinsci/remoting/blob/master/CHANGELOG.md#260>), >> which has been soaked for about 1 week. IMHO it would be useful to pick >> this version. >> >> I'm planning to maintain an LTS & Backporting branch in remoting for >> 2.7.1 baseline, so bumpong of the release would be useful in order to avoid >> full backporting for the next release. >> >> BR, Oleg >> >> вторник, 21 июня 2016 г., 19:09:00 UTC+2 пользователь Oleg Nenashev >> написал: >>> >>> Thanks a lot for your efforts! >>> The RC branch looks good to me >>> >>> 2016-06-21 19:02 GMT+02:00 ogondza <[email protected]>: >>> >>>> I consider backporting to be close. All was backported except for >>>> JENKINS-35641 and JENKINS-34923 where I would like it to have some extra >>>> soaking time. Note that I will not be able to attend the Governance meeting >>>> (travelling) so I will proceed with the rc at the closest time I am >>>> available unless I hear some objection, either here or in meeting logs, or >>>> the ATH will fail seriously. >>>> >>>> -- >>>> oliver >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/4f621098-ed39-462d-a245-52f882650d89%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/4f621098-ed39-462d-a245-52f882650d89%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/ieXnaHVqX3k/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/da62c57c-dbc8-4d8d-879a-275ec246a88e%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/da62c57c-dbc8-4d8d-879a-275ec246a88e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPfivLA4NFV8UG6x9fN3dEw9zQ4i0%3DKU1%2B6sXDD%2BMEdS7qx2Ww%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
