On 22 April 2015 at 12:36, Jesse Glick <[email protected]> wrote: > On Wed, Apr 22, 2015 at 5:48 AM, Stephen Connolly > <[email protected]> wrote: > > Where was the discussion on this? I couldn't find it anywhere in > > jenkins.2015-01-07-19.01.log.html or jenkins.2015-01-21-19.01.log.html > > Not sure why you are looking at logs in January!
I was trying to find where 1.596 was selected as the LTS line... 1.596 was released in January and On Feb 4th we just have 19:42:19 <kohsuke> #topic LTS RC status19:42:30 <kohsuke> #action Kohsuke to put LTS schedules in the calendar19:42:39 <ogondza> kohsuke: we are ready19:42:46 <hgilmore> Thank you19:42:49 <kohsuke> ogondza: yay19:42:58 <kohsuke> all right, that was easy On Feb 18th, we have: 20:02:14 <kohsuke> #topic LTS status check20:02:30 <ogondza> kohsuke: we are ready20:02:47 <kohsuke> ogondza: yay, nice and sweet On Mar 4th we have: 19:00:32 <kohsuke_> #topic LTS RC status check19:00:50 <ogondza> kohsuke_: ready for RC19:01:08 <kohsuke_> I failed once again to push 1.596.1 in time, so my hats off to you ogondza19:01:26 <ogondza> no problem So by March 4th 1.596 was chosen as the LTS line. The only reference I could see to 1.596 being selected was the mail on 27th of Jan from ogondza which would mean that I should expect to see in the logs during January the discussion of which LTS line to pick... but no sign or sight > According to > > https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line > > the next baseline is picked around the time 1.596.3 is released. > > The RC was posted on Apr 05, meaning the release should have been on > Apr 19/20. Clearly that did not happen; maybe Kohsuke just forgot? > > Picking a baseline generally happens during a project meeting, which > is not for another week, though I suppose it could be done on the dev > list as well. > > > /me hoping for 1.607+ or 1.610 ideally > > /me hoping for 1.607+ definitely, or 1.609+ ideally, and if not 1.610+ > then I certainly have some `lts-candidate`s I will push for. > > I have complained about this to Kohsuke privately but perhaps others > are affected too: it would be really helpful if the upcoming LTS > baseline were decided (*) well in advance, so that people writing APIs > would know when those changes would actually be available for use from > plugins with LTS dependencies (as is usually preferred). As it stands, > for workflow-plugin I have the master branch on 1.596.x, a branch > using APIs from 1.599+ intended for the next LTS, a branch on top of > that branch (!) using 1.609+ which may or may not be in the next LTS, > and an unrelated branch using 1.607+ which will probably be in the > next LTS but I am not sure. I cannot collapse these branches without > running the risk that the LTS will be earlier than 1.609 and I will > have to revert some of my changes and put them back in a branch. It > would be a lot less work, and merge conflicts, if I knew in advance > what I was going to get in May, and could plan accordingly. Indeed my > core changes could be planned with a schedule in mind, and reviewers > could ask for a particularly dangerous-looking PR to be put on hold if > a new baseline were imminent. > > Put another way, the current policy is fine if you think of Jenkins > core releases as more or less equivalent, but some more stable than > others according to a couple dozen user ratings, so we might as well > pick a reasonably recent sunny one so fewer regression fixes need to > be backported. It does not work when you think of core as a platform > with APIs that plugin authors are awaiting the delivery of. I realize > that most plugins use rather old core dependencies and are not much > affected, so perhaps mine is a minority complaint. > > > (*) Since we seem to have replaced the RC system with a policy of > doing multiple 1.xxx releases in a week if warranted, the decision > would be better stated in terms of a date, rather than a version > number. > > -- > 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/CANfRfr2paJyCam8YCcSn8TZ-vZzdmghLMLBOpcHYjYbbKtr%2Brg%40mail.gmail.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%2BnPnMzFJ9MoCmmD%3DgV-6VEUGjD14o-ua7dFy9FoxgYZ%2B%3DT8wQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
