See:
#topic LTS.next planning
http://meetings.jenkins-ci.org/jenkins/2014/jenkins.2014-01-22-19.01.log.html
I identified these 2:
- Announced weekly release might prove itself to be of low quality
19:33:28 <kohsuke> It feels like beefing up the QA effort into the main
line release is the pre-requisite for us to be able to mechanically pick
the LTS base version
- Low quality work can get into those releases because of the pressure it
poses on contributors/commiters
19:34:05 <ogondza> I am afraid that knowing what will be the next lts
before it is released can motivate people push changes to those releases in
a hurry degrading their quality
But as you said, we can hold dangerous changes until the LTS.next is
released. Perhaps this will allow us to merge more PRs we are not so sure
about right after the crucial release to give it extra long time until
picked up by the following LTS.next.
--
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/676a55b7-b94b-4987-b435-5ac6b39fb8f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
