While we're on the topic of how teams use the Priority Flag, could I ask
y'all do to something for me?
Could you add how your team maps the the priority flag, or link to a page
describing it?
https://wiki.mozilla.org/index.php?title=Bugmasters/Projects/Folk_Knowledge/Priority_Field&action=edit&re
gt; telling you things you don’t care about. Or, I could start arguing in the
> bug, that this should be higher priority, and fill up the comments with
> non-technical information.
>
> Getting close to a full page, I’ll stop now. I’m available for live
> conversations on the topic :)
On Thu, Mar 31, 2016 at 12:28 PM, Milan Sreckovic
wrote:
> Or, I could start arguing in the bug, that this should be higher priority,
> and fill up the comments with non-technical information.
This reminds me, we have filtering tools to mute abusive and unproductive
comments in bugs.
https:/
I've responded to a similar comment in the google doc, but I'll repeat it
here.
Priority sounds like a great choice, but given that everyone's using the
Priority field their own way, there's enough heterogeneity in how it's used
to make it difficult.
If I was to take that approach, I'm concerned
On Tue, Mar 29, 2016 at 5:09 PM, Eric Rescorla wrote:
> On a more substantive, less procedural note, this seems to be designed for
> a particular workflow in which there is an assumption that bugs are for
> immediate processing. However, in may cases we use bugs as placeholders or
> assemble big
c Rescorla wrote:
> I'm trying to figure out the scope of this proposal. Are you expecting it
> to apply merely to Firefox or to Gecko as well?
>
> -Ekr
>
>
> On Tue, Mar 29, 2016 at 1:07 PM, Emma Humphries wrote:
>
>> tl;dr
>>
>> In Quarter T
following the new process
-- Emma Humphries, Bugmaster
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
ty, have a look at this and update it!)
The things that would be most helpful are
* reproduction steps
* isolated example
Thanks,
-- Emma Humphries, Bugmaster
On Thu, Mar 10, 2016 at 10:23 AM, Devan Shah wrote:
> hello
>
> When I set a custom property such as element.listofSome
- Emma
On Mon, Feb 29, 2016 at 12:16 PM, Emma Humphries wrote:
>
> On Mon, Feb 29, 2016 at 12:02 PM, Josh Matthews
> wrote:
>
>> Am I right in assuming that this is a comment that's added to the bug
>> when a triage decision is made, rather than as a direct response
On Mon, Feb 29, 2016 at 12:02 PM, Josh Matthews
wrote:
> Am I right in assuming that this is a comment that's added to the bug when
> a triage decision is made, rather than as a direct response to filing the
> bug?
Yes, for now it's a comment (so we can trigger bugmail) and later it will
be a
Recently, Benjamin Smedberg gave an airmozilla talk in Mountain View [1]
about improving how we handle bugs filed against Firefox, and how we hope
it will make our product, the Web, and our lives better. Today, we’re
ready to show you the next steps of that project.
With the help of dedicated tr
On Sat, Feb 13, 2016 at 4:50 AM, David Rajchenbach-Teller <
dtel...@mozilla.com> wrote:
>
>
> One possible solution would be to:
> - add a component Firefox > Performance (and also Thunderbird >
> Performance, etc.) to Bugzilla, which would cover all untriaged
> performance issues (including web c
On Tue, Feb 2, 2016 at 9:04 AM, Richard Newman wrote:
> Here's my very lightweight counter-proposal:
>
> Once or twice a week, automatically mail out two lists (in one email) to
> the set of people Emma collected. The first are is UNCONFIRMED bugs. The
> second is NEW bugs, not filed by one of th
;t want to waste engineering's time, so we're piloting this with a
small number of groups so we can see if we're going in the right direction,
and stated what we expect to see happen with this work so we can decide if
we'll continue with it.
-- Emma Humphries
On Fri, Jan 29, 2016
Bug Program Next Steps
Over the last week, I’ve asked you to step up and identify developers who
will be responsible for bugs triaged into their component (in Firefox,
Core, Toolkit, Fennec iOS, and Fennec Android.)
Why This Matters
Bugs are a unit of quality we can use to see how we’re doing.
W
*Status of The Component Owners Sheet*
https://docs.google.com/spreadsheets/d/10i30CFUPJM7snz0xX3czFJeBh2tNwjwjtI409DQw3x0/
If you have questions, @emceeaich on irc.mozilla.org
If you think someone is a component owner enter 'name?' in owner column
If you think a component is defunct (no longer
ternoon after I sent
out the update.
And yes, that was a typo in the subject of Friday's email. It didn't
come from the alternate universe where the 26th is on a Tuesday.
%Complete
Core 67.13%
Toolkit 59.46%
Firefox 70.00%
Fennec iOS 45.45%
Fennec Android 100.00%
Overall 69.31%
Cheer
summaries
Firefox:Reading List
Cheers,
---
Emma Humphries
irc: emceeaich
bugmail: ehumphr...@mozilla.com
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Good point. I'll make the link accessible to all.
-- Emma
On Thu, Jan 21, 2016 at 2:44 PM, Dave Townsend wrote:
> Is there any reason not to make the link publicly accessible? Then
> no-one needs to request access.
>
> On Thu, Jan 21, 2016 at 2:37 PM, Emma Humphries wrote:
>
I understand, and if non-mozilla.com community members need access,
email me or request access from inside the sheet.
Thanks,
-- Emma
On Thu, Jan 21, 2016 at 2:31 PM, Josh Matthews wrote:
> I'll point out that the downside of using a google doc like this is that
> it's only accessible to Mozill
The short version: we believe that the number of outstanding bugs in a
component is the best metric we have of the overall health and quality
of that component. We will test this belief by dramatically improving
the efficiency of ingest and processing of new bugs, and would like
two to four compone
I've been reviewing Password Manager bugs the past few days, and the
https/http issue has been bugged:
https://bugzilla.mozilla.org/show_bug.cgi?id=667233 and has recent
activity. It has an owner, and a priority.
On Wed, Nov 25, 2015 at 10:06 AM, Thomas Schäfer
wrote:
> Am Mittwoch, 25. November
101 - 122 of 122 matches
Mail list logo
