So I completely dropped the ball on this one, and my apologies. I'm going to produce the bits tonight, but given that there are still some more issues like JENKINS-15652, what if we backport some more fixes, skip 1.509.2, and call that 1.509.3 (or call that the new 1.509.2)?
I'll produce 1.509.2 RC with the current bits but while I wait to hear from others, I'll do some backporting toward 1.509.3 RC. 2013/5/19 Vojtech Juranek <[email protected]> > > > I can think of several bugs off the top of my head which will be prime > > candidates for 1.509.3 once fixed in trunk. So long as vjuranek is > willing > > to produce new LTS versions I see no harm in sticking to the “train” > model. > > yes, this is intended (to produce another minor LTS). IIRC we chose 1.509 > as a > base line for LTS with awareness that it contains bugs and we will produce > minor versions more often to included as much fixes as possible. Therefore > I > also wanted to do an exception and backport fixes regardless they are > already > in mail release line or not, but Kohsuke had different opinion [1] (and as > I > hadn't any strong opinion on this, I agreed to backport only soaked fixes) > > [1] > http://meetings.jenkins-ci.org/jenkins/2013/jenkins.2013-05-15-18.00.log.html > -- Kohsuke Kawaguchi -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
