I'll triage the top orange tomorrow and try to find some owners for things.
After the new year I'll set something weekly up to stay on top of things. On Dec 22, 2015 2:58 PM, "Jason Duell" <[email protected]> wrote: > > > On Tue, Dec 22, 2015 at 11:38 AM, Ben Kelly <[email protected]> wrote: > >> >> I'd rather see us do: >> >> 1) Raise the visibility of oranges. Post the most frequent intermittents >> without an owner to dev-platform every N days. >> 2) Make its someone's job to find owners for top oranges. I believe >> RyanVM >> used to do that, but not sure if its still happening now that he has >> changed roles. >> >> Ben >> >> > I'm with bkelly on this one. Maybe with some additional initial messaging > ("War on Orange raised in priority!") too. I don't think we want to pivot > all work in platform for this. > > Jason > > > >> >> > >> > On Tue, Dec 22, 2015 at 7:41 AM Mike Conley <[email protected]> >> 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, <[email protected]> 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 >> > > > [email protected] >> > > > https://lists.mozilla.org/listinfo/dev-platform >> > > > >> > > _______________________________________________ >> > > dev-platform mailing list >> > > [email protected] >> > > https://lists.mozilla.org/listinfo/dev-platform >> > > >> > _______________________________________________ >> > dev-platform mailing list >> > [email protected] >> > https://lists.mozilla.org/listinfo/dev-platform >> > >> _______________________________________________ >> dev-platform mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-platform >> > > > > -- > > Jason > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
