On 22/12/15 11:38 AM, Ben Kelly wrote:
On Tue, Dec 22, 2015 at 11: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?
-1
This has been tried numerous times on fxos without success. While it might
get oranges down temporarily, its not putting a system in place to address
the problem over the long haul.
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
FWIW a summary of top orangefactor[1] oranges are posted regularly
to dev.tree-alerts. Configuring it to also post to
dev.platform is certainly possible if that's what people want. Though I
have a feeling that people will mostly ignore these emails anyway if we do.
-Andrew
[1] http://brasstacks.mozilla.com/orangefactor/
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
