The fix is a rather serious memory leak for anyone with long running active slaves. I would argue that it is low risk to include it on the basis of the testing I performed on this code and an analysis of the actual change.
If it misses the boat, fair enough, but we should try and get it on the boat IMHO On 28 April 2016 at 09:15, Oliver Gondža <[email protected]> wrote: > I doubt this is .2 material. Stephen, are you ok with .3? > > On 04/28/2016 10:09 AM, Oleg Nenashev wrote: > >> I'll ping him again about it >> >> On Apr 28, 2016 10:07, "Stephen Connolly" >> <[email protected] >> <mailto:[email protected]>> wrote: >> >> I think we need a 2.58 release from KK to include the memory leak fix >> > > -- > 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/e3be7523-8ccd-2b4a-8906-e582688c93a3%40gmail.com > . > > 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/CA%2BnPnMw%2B8mHfuD0SOy7dr7Xb_c5q97JuH6s5UQd1YJOXJ%3D0adA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
