chart.mozilla.org doesn't display 2.5 nominations/blockers for Firefox OS

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Bugzilla Anthropology Metrics
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: jlorenzo, Unassigned)

Tracking

(Blocks: 1 bug)

Production
x86_64
Linux
Dependency tree / graph

Details

(Reporter)

Description

3 years ago
Even though we have some 3.0? nominations, no corresponding filter is displayed and you can't force 3.0 in the URL[1].

It seems like we need to update the queries like here[2].

As QA starts to find regressions on the 3.0 branch, it seems high priority to have visibility on these nominations. Kyle, do you think we can get a fix rapidly?

[1] http://charts.mozilla.org/fxos/nominations.html#project=1.3T,1.4,2.0,2.1,2.2,3.0
[2] https://github.com/mozilla/charts/blob/df254743cba75260e0132e5abe0cffc5f8fbf847/fxos/nominations.html#L255
Flags: needinfo?(klahnakoski)
(Reporter)

Comment 1

3 years ago
NI Bhavana to get Release Management aware of this issue. It's just a call out, no input required.
Flags: needinfo?(bbajaj)
Thanks Johan. Kyle, can we please get 3.0? noms added to this chart when you get a chance?
Flags: needinfo?(bbajaj)
np, I will get back to you when I have pushed the change.
Flags: needinfo?(klahnakoski)
Sorry for the delay.  Please send me a project "start_date" and some meaningful "targetDate".  This meta data is required to provide context to charts.
Flags: needinfo?(bbajaj)
Also, what versions of the platform are going into 3.0?
(Reporter)

Comment 7

3 years ago
The result doesn't seem right for the "client" component: 146 noms are listed there but all of them have blocking-b2g set to "---". Apart from that, everything else looks coherent.
Flags: needinfo?(klahnakoski)
This is an example where I need to know about the Firefox versions that will go into 3.0.  I assume fx37 and fx38, but maybe there are more.  The reason the "client" has some many nominations is because they have blocking-loop: Fx38?
Flags: needinfo?(klahnakoski)
(In reply to Kyle Lahnakoski [:ekyle] from comment #4)
> Sorry for the delay.  Please send me a project "start_date" and some
> meaningful "targetDate".  This meta data is required to provide context to
> charts.

sry about the late response here, but we are yet to determine the exact gecko/timeline. For now can we pick whatever is on m-c(Firefox 39) as the target ? the hypothetical start/end dates are : jan 12 2015 and June 30 2015 (when fx39 ships). I'll redo those on my end and pass it on once i have a confirmation on 3.0 in next few weeks.
Flags: needinfo?(bbajaj)
(Reporter)

Comment 10

3 years ago
I think we can fix this bug now that we know the calendar for the next FFOS version (2.5). Josh, Wilfred, do you know the dates needed in comment 4?
Flags: needinfo?(wmathanaraj)
Flags: needinfo?(jocheng)
Summary: chart.mozilla.org doesn't display 3.0 nominations/blockers for Firefox OS → chart.mozilla.org doesn't display 2.5 nominations/blockers for Firefox OS
Yes, please confirm the dates: (jan 12 2015 and June 30 2015)?  and confirm the Firefox versions that are included in FxOS 2.5.   Also, for clarity:  Are we talking about 2.5 or 3.0?  or both?

I will make the changes and comment back here when on allizom, and will ask you all to review before pushing to prod.

Comment 12

3 years ago
(In reply to Kyle Lahnakoski [:ekyle] from comment #11)
> Yes, please confirm the dates: (jan 12 2015 and June 30 2015)?  and confirm
> the Firefox versions that are included in FxOS 2.5.   Also, for clarity: 
> Are we talking about 2.5 or 3.0?  or both?
> 
> I will make the changes and comment back here when on allizom, and will ask
> you all to review before pushing to prod.

Hi Kyle,
Planned to branch out from: Firefox 43

Current planned date:
    Dev Start: 2015-06-29 (Dev start)
    FLR: TBD
    FL: TBD (branch here for m-c and gaia)
    FC: 2015-11-02 (branch here for gecko b2g_43)
    CC: 2016-01-04 

The previous 3.0 release is now 2.5. (Although we plan to have 3.0 in 2016 1H)
All current blocking-b2g and feature-b2g flags are renamed from 3.0?/+ to 2.5?/+.

Ref: https://wiki.mozilla.org/Firefox_OS/Releases/2.5
Flags: needinfo?(jocheng)
I have pushed the proposed changes to allizom [1]

* I assumed that "Planned to branch out from: Firefox 43" means 2.5 will NOT contain 2.5
* I assumed 2.3 and 2.4 do not exist

Please review and get back to me before I push to master (charts.mozilla.org)

[1] https://charts.paas.allizom.org/fxos/nominations.html#project=1.4,2.0,2.1,2.2,2.5
Flags: needinfo?(jocheng)
Flags: needinfo?(wmathanaraj)
We may move gecko to 44. We want to use the newest with at least one extra stabilisation on serviceworkers.
reading my last comment, it looks wrong. I will repeat the assumptions I made in full:

* I assumed that "Planned to branch out from: Firefox 43" means 2.5 will NOT contain **fx43**
* I assumed 2.3 and 2.4 do not exist

Should I include fx43 and fx44 now, or wait until later?
(In reply to Wilfred Mathanaraj [:WDM] from comment #14)
> We may move gecko to 44. We want to use the newest with at least one extra
> stabilisation on serviceworkers.

hi Wilfred, 
when you say "with at least one extra stabilization on serviceworkers." do you mean you would branch after 6 weeks in aurora or after 6 weeks in mozilla-central or any other thing...?
Flags: needinfo?(wmathanaraj)
branching discussion is still ongoing as to what process we follow - but we want to branch as late as possible - so we want to branch for 2.5 as late as November.
Flags: needinfo?(wmathanaraj)
I suggest I include fx43 and fx44 in the counts or 2.5.  This way, when features are being marked for 43 and 44, you will see them in the dashboards; then it will be obvious if/when it is decided they do not belong.  It would be harder to notice fx43 and fx44 missing from the counts in the event it is decided they do belong.

I prefer to choose the option that makes any discrepancy the most obvious.
I have included fx43 and fx44, with the intent we will open a new bug when more information comes to light.

I pushed changes to both PROD (http://charts.mozilla.org/) and STAGING (https://charts.paas.allizom.org/)
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Flags: needinfo?(jocheng)
(Reporter)

Updated

3 years ago
Blocks: 1222946
You need to log in before you can comment on or make changes to this bug.