> On 27. Jul 2017, at 07:19, Andreas Mandel <[email protected]> wrote: > > Thanks for the feedback. Does this mean, according to plan, you release LTS > versions even with blocker issues? Or do you judge the severity of the issue > different?
Yes. The train model means we leave the station no matter what. Otherwise we just get bogged down in discussions what constitutes a blocker issue while holding off releases to include well-soaked bug fixes. > but time is unfortunately quite limited. If I'm right with my guess of 2.53 as the first affected release, the problem was around for almost 3 months between introduction of the issue and the original report, which was created only after 2.60.1 was released. As we rely on users reporting and voting on issues they encounter for things like deciding on an LTS baseline, it's no surprise this got in. I asked a month ago in a comment for people who encounter this issue to narrow down in which release the problem was introduced. Despite having 20 watchers now, nobody seems to have taken the time to do that yet. Does that look consistent with an urgent blocker issue to you? -- 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/6C6FDB86-4015-4DDA-8376-B7A1F5C28B52%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
