Closed Bug 856869 Opened 7 years ago Closed 7 years ago

New Product: Firefox Health Report

Categories

(bugzilla.mozilla.org :: Administration, task)

ARM
All
task
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: mconnor, Assigned: dkl)

Details

> The name of the product

Firefox Health Report

> The classification (group) you would like the product in

Client Software

> A longer description, usually including a web link for more info on the product

For all bugs involving collection, submission, analysis and user-facing features (about:healthreport) as part of the Firefox Health Report product

> The initial list of components, with their info

(We may add more in the future, but better to keep it simple for now.)

about:healthreport
For all bugs in the web-served user-facing report (code at https://github.com/mozilla/fhr-jelly)

Client: Desktop
For all FHR issues related to Firefox for Windows, Linux and OS X

THis next one is in conflict with what's in bug 855144, but I think it should be with FHR.

Client: Android
For all FHR issues related to Firefox for Android

Data API
For all bugs related to the aggregate data API supporting the user-facing report

Data Collection
For bugs related to receiving and storing FHR payloads

> The initial list of versions, with their info (see below)
> The initial list of target milestones, with their info (see below)

Please copy the Firefox Product

> The security group(s) bugs should be classified under when a user checks the security flag (if you don't know, we can help figure this out for you)

mozilla-services-security for now (pending the larger reorg/segmentation discussion)

> The number of votes needed to confirm a bug (UNCO --> NEW) (optional, disabled by default) 

Disabled.
Product created but not yet enabled for new bug entry.

Code change to support default security group:
Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2         
modified extensions/BMO/lib/Data.pm
Committed revision 8710. 

Once the change goes live we can enable the new product.

Moving to IT as they will need to run a script to sync the versions and milestones with Firefox.

-----

IT, please run the following script on from the BMO document root:

# perl contrib/reorg-tools/syncmsandversions.pl "Firefox" "Firefox Health Report"

When done, pass the bug back to us for completion.

dkl
Assignee: nobody → server-ops-devservices
Component: Administration → Server Operations: Developer Services
OS: Windows 8 → All
Product: bugzilla.mozilla.org → mozilla.org
QA Contact: shyam
Hardware: x86_64 → ARM
Version: Production → other
Not sure what happened here : no output at all - 

[shyam@bugzillaadm.private.scl3 bugzilla.mozilla.org]$ sudo ./contrib/reorg-tools/syncmsandversions.pl "Firefox" "Firefox Health Report"
[shyam@bugzillaadm.private.scl3 bugzilla.mozilla.org]$

Is that expected?
Assignee: server-ops-devservices → nobody
Component: Server Operations: Developer Services → Administration
Product: mozilla.org → bugzilla.mozilla.org
QA Contact: shyam
(In reply to Shyam Mani [:fox2mike] from comment #2)
> Is that expected?

yes, that script doesn't output anything when it succeeds.
Product open for business.
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Hmm, I was expecting the same flags/tracking flags as Firefox.  How do I make that happen?
(In reply to Mike Connor [:mconnor] from comment #5)
> Hmm, I was expecting the same flags/tracking flags as Firefox.  How do I
> make that happen?

you didn't ask for any flags (part of the 'component' requirements).

flags:
  - approval-mozilla-aurora : already there
  - approval-mozilla-beta : already there
  - approval-mozilla-release : added
  - approval-mozilla-esr17 : added
  - approval-mozilla-b2g18 : added
  - sec-approval : added
  - checkin : added

unfortunately tracking/status flags require a code change:

Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.2/
modified extensions/BMO/lib/Data.pm
Committed revision 8718.

these will be visible following this week's code push (late wednesday).
Sigh, this is what happens when I try to follow a template, thanks for the quick followup!
You need to log in before you can comment on or make changes to this bug.