I think I have three issues that should go in despite not meeting the standard criteria. In two cases the change is small, low risk and I have analysed the change for impact.
The third is a remoting change I am currently working to get merged... I'd like if it can be included butay be able to have it wait for .3 On Monday, June 8, 2015, oliver gondža <[email protected]> wrote: > Hi, > > Backporting for next LTS release started. > > Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 > Fixed: > https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%201.609.2-fixed > > -- > 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/op.xzxhvbqxsbfict%40arch. > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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%2BnPnMykMO9tVkK1bje4ffMmkfu12zf4qa2G_LBFjdA-tw6gKA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
