I think this is a great idea. Although it won't fix the problem long-term, what it will do is get engineers and especially engineering managers thinking about the problem, and hopefully understanding it better so they can incorporate it into future priorities.
There are two fundamental problems that lead to the current state: weak or no ownership of many tests or suites, so that fixing these oranges is always somebody else's problem, and a focus on "hard" deliverables which often leave little or no time to deal with unplanned problems like an increase in intermittents. If we dedicate a cycle to quality and tests, we should use that opportunity to figure out what a more viable strategy is longer-term for making sure these don't get out of hand again, which might include having teams adopt test, suites, and the intermittent orange counts associated with them, and being accountable for them in goals and deliverables. Jonathan On Tue, Dec 22, 2015 at 8:16 AM, Douglas Turner <do...@mozilla.com> wrote: > Mike -- totally supportive of this. I would *love* to see a release cycle > completely dedicated to quality. We branch again on January 26. We could > use that cycle to focus on nothing but quality (fixing tests, bug triaging, > no feature development at all). > > Thoughts? > > On Tue, Dec 22, 2015 at 7:41 AM Mike Conley <mcon...@mozilla.com> wrote: > > > I would support scheduled time[1] to do maintenance[2] and help improve > our > > developer tooling and documentation. I'm less sure how to integrate such > a > > thing in practice. > > > > [1]: A day, a week, heck maybe even a release cycle > > [2]: Where maintenance is fixing oranges, closing out papercuts, > > refactoring, etc. > > > > On 21 December 2015 at 17:35, <jmath...@mozilla.com> wrote: > > > > > On Monday, December 21, 2015 at 1:16:13 PM UTC-6, Kartikaya Gupta > wrote: > > > > So, I propose that we create an orangefactor threshold above which > the > > > > tree should just be closed until people start fixing intermittent > > > > oranges. Thoughts? > > > > > > > > kats > > > > > > How about regularly scheduled test fix days where everyone drops what > > they > > > are doing and spends a day fixing tests? mc could be closed to > everything > > > except critical work and test fixes. Managers would be able to opt > > > individuals out of this as needed but generally everyone would be > > expected > > > to take part. > > > > > > Jim > > > _______________________________________________ > > > dev-platform mailing list > > > dev-platform@lists.mozilla.org > > > https://lists.mozilla.org/listinfo/dev-platform > > > > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
