Bug assignees and general@js.bugs

[Josh Matthews]

With my hat as community steward on, I'm starting to use scripts that
return the list of bugs fixed during a certain period, and I see a
surprising number of ones with the assignee as gen...@js.bugs. This is
disappointing, since these scripts are also filtering by assignee to
remove entries that are assigned to MoCo employees. Can we be more
vigilant about assigning bugs to the person doing the work? That will
make my efforts more valuable and reduce the need for me to open up
lists of bugs individually to see if I need to include it or not.

Cheers,
Josh

[Bobby Holley]

Looping in RyanVM, since I imagine this might have something to do with his
scripts flagging nobody@ but not gen...@js.bugs.

> ______________________________**_________________
> dev-tech-js-engine mailing list
> dev-tech-js-engine@lists.**mozilla.org<dev-tech-...@lists.mozilla.org>
> https://lists.mozilla.org/**listinfo/dev-tech-js-engine<https://lists.mozilla.org/listinfo/dev-tech-js-engine>
>

[Bobby Holley]

Ok, we should fix that. gen...@js.bugs is the default assignee / nobody of
the js engine.


On Tue, Aug 27, 2013 at 10:13 AM, Ryan VanderMeulen <rya...@gmail.com>wrote:

> Our merge scripts set the assignee to the patch author when the assignee
> is nobody. AFAIK, mcMerge doesn't do anything if it's set to a generic

> gen...@js.bugs.
>
>
> On Tue, Aug 27, 2013 at 1:10 PM, Bobby Holley <bobby...@gmail.com>wrote:
>
>> Looping in RyanVM, since I imagine this might have something to do with
>> his scripts flagging nobody@ but not gen...@js.bugs.
>>
>>
>> On Tue, Aug 27, 2013 at 9:51 AM, Josh Matthews <jo...@joshmatthews.net>wrote:
>>

[Tom Schuster]

Actually do we still need that special case? I assume everyone could switch
to watching the JS component.

-Tom

On Tue, Aug 27, 2013 at 1:19 PM, Bobby Holley <bobby...@gmail.com> wrote:

> Ok, we should fix that. gen...@js.bugs is the default assignee / nobody
> of
> the js engine.
>
>
> On Tue, Aug 27, 2013 at 10:13 AM, Ryan VanderMeulen <rya...@gmail.com
> >wrote:
>
> > Our merge scripts set the assignee to the patch author when the assignee
> > is nobody. AFAIK, mcMerge doesn't do anything if it's set to a generic
> > gen...@js.bugs.
> >
> >
> > On Tue, Aug 27, 2013 at 1:10 PM, Bobby Holley <bobby...@gmail.com
> >wrote:
> >
> >> Looping in RyanVM, since I imagine this might have something to do with
> >> his scripts flagging nobody@ but not gen...@js.bugs.
> >>
> >>
> >> On Tue, Aug 27, 2013 at 9:51 AM, Josh Matthews <jo...@joshmatthews.net
> >wrote:
> >>

> >>> ______________________________**_________________
> >>> dev-tech-js-engine mailing list
> >>> dev-tech-js-engine@lists.**mozilla.org<
> dev-tech-...@lists.mozilla.org>
> >>> https://lists.mozilla.org/**listinfo/dev-tech-js-engine<
> https://lists.mozilla.org/listinfo/dev-tech-js-engine>
> >>>
> >>
> >>
> >

> _______________________________________________
> dev-tech-js-engine mailing list
> dev-tech-...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-tech-js-engine
>

[emo...@mozilla.com]

On Tuesday, 27 August 2013 18:19:05 UTC+1, Bobby Holley wrote:
> Ok, we should fix that. gen...@js.bugs is the default assignee / nobody of
> the js engine.

I've just patched mcMerge to look for email ending ".bugs" (Bugzilla's generic placeholders all end with that) rather than looking for 'nobody' specifically, (bug 909822).

Note also that until bug 764881, bzexport didn't set the assignee - and it's possible that some people haven't updated their local bzexport repo since they originally checked it out.

Best wishes,

Ed

[Ehsan Akhgari]

On 2013-08-27 1:21 PM, Tom Schuster wrote:
> Actually do we still need that special case? I assume everyone could switch
> to watching the JS component.

Yeah, we shouldn't need that special case any more.

> On Tue, Aug 27, 2013 at 1:19 PM, Bobby Holley <bobby...@gmail.com> wrote:
>
>> Ok, we should fix that. gen...@js.bugs is the default assignee / nobody
>> of
>> the js engine.
>>
>>

>> On Tue, Aug 27, 2013 at 10:13 AM, Ryan VanderMeulen <rya...@gmail.com
>>> wrote:
>>
>>> Our merge scripts set the assignee to the patch author when the assignee
>>> is nobody. AFAIK, mcMerge doesn't do anything if it's set to a generic
>>> gen...@js.bugs.
>>>
>>>
>>> On Tue, Aug 27, 2013 at 1:10 PM, Bobby Holley <bobby...@gmail.com
>>> wrote:
>>>
>>>> Looping in RyanVM, since I imagine this might have something to do with
>>>> his scripts flagging nobody@ but not gen...@js.bugs.
>>>>
>>>>
>>>> On Tue, Aug 27, 2013 at 9:51 AM, Josh Matthews <jo...@joshmatthews.net
>>> wrote:
>>>>

[Josh Matthews]

No further activity has occurred, since the mc-merge changes caused
havoc and were backed out. Who could sign off on removing the assignee
special case for the component?

Cheers,
Josh

[Chris Peterson]

On 9/11/13 10:10 AM, Josh Matthews wrote:
> No further activity has occurred, since the mc-merge changes caused
> havoc and were backed out. Who could sign off on removing the assignee
> special case for the component?

Just to clarify, if the gen...@js.bugs special case is removed, then
the default assignee will be nob...@mozilla.org? Will we need to
manually reassign existing gen...@js.bugs to nob...@mozilla.org?


chris

[Benjamin Smedberg]

On 9/14/2013 1:41 AM, Chris Peterson wrote:
> On 9/11/13 10:10 AM, Josh Matthews wrote:
>> No further activity has occurred, since the mc-merge changes caused
>> havoc and were backed out. Who could sign off on removing the assignee
>> special case for the component?
>
> Just to clarify, if the gen...@js.bugs special case is removed, then
> the default assignee will be nob...@mozilla.org?

Yes.

> Will we need to manually reassign existing gen...@js.bugs to
> nob...@mozilla.org?

We can do that with a mass change; no need to do it one at a time.

--BDS

[Josh Matthews]

One last time - can somebody give me the go-ahead on this? I don't like
interpreting silence as permission.

Cheers,
Josh