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
