Query: Number of people reviewed patches & contributed to test cases

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
10 years ago
3 years ago

People

(Reporter: Natnaree Chummanon, Assigned: reed)

Tracking

Details

(Reporter)

Description

10 years ago
I want to know:

1. Number of people who reviewed patches in Bugzilla (during the past 6 months before FF3 launch).
- This includes reviews of only products that are categorized as "Client Software" and "Components" (https://bugzilla.mozilla.org/enter_bug.cgi?full=1)

2. Number of "Test Cases" reported in the last 6 months.
(Assignee)

Updated

10 years ago
Group: infra
Assignee: server-ops → reed
(Assignee)

Comment 1

10 years ago
(In reply to comment #0)
> 1. Number of people who reviewed patches in Bugzilla (during the past 6 months
> before FF3 launch).
> - This includes reviews of only products that are categorized as "Client
> Software" and "Components" (https://bugzilla.mozilla.org/enter_bug.cgi?full=1)

265

select distinct flags.setter_id 
from attachments join flagtypes on flags.type_id=flagtypes.id 
join bugs on flags.bug_id = bugs.bug_id 
join products on bugs.product_id=products.id 
join classifications on products.classification_id=classifications.id
where flags.modification_date > '2007-12-17' and flags.modification_date < '2008-06-17' 
and (flags.status = '+' or flags.status = '-') 
and (flagtypes.name = 'review' or flagtypes.name = 'superreview') 
and (classifications.name = 'Client Software' OR classifications.name = 'Components');

> 2. Number of "Test Cases" reported in the last 6 months.

6939

select count(attach_id) as num_attachments
from attachments join longdescs on attachments.bug_id = longdescs.bug_id
and creation_ts = bug_when
where (attachments.description LIKE '%test%' or longdescs.thetext LIKE '%test%')
and creation_ts > '2007-12-17' and creation_ts < '2008-06-17';
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.