Closed
Bug 1253588
Opened 9 years ago
Closed 8 years ago
Enable bookmark history menu experiment by default
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(firefox45+ wontfix, firefox46+ verified, firefox47+ verified)
People
(Reporter: Margaret, Assigned: Margaret)
References
Details
Attachments
(2 files)
67 bytes,
text/x-github-pull-request
|
lizzard
:
approval-mozilla-aurora+
lizzard
:
approval-mozilla-beta+
|
Details | Review |
67 bytes,
text/x-github-pull-request
|
sebastian
:
review+
lizzard
:
approval-mozilla-release+
|
Details | Review |
[Tracking Requested - why for this release]: Feature intended to release in 46.
Right now this experiment is limited to nightly, but we should enable it by default to let it ride to release.
This experiment is actually in 45, so we could enable it for release users if we want, but I think we should start by enabling it for beta users.
Flags: needinfo?(bbermes)
Comment 1•9 years ago
|
||
Can we enable it for both, beta and release? What's your rationale to start with beta first?
Flags: needinfo?(bbermes) → needinfo?(margaret.leibovic)
Assignee | ||
Comment 2•9 years ago
|
||
(In reply to Barbara Bermes [:barbara] from comment #1)
> Can we enable it for both, beta and release? What's your rationale to start
> with beta first?
Just being cautious. So far only Nightly users have seen this change, so it would be good to at least spend a few days with it on beta before rolling out to release.
Flags: needinfo?(margaret.leibovic)
Comment 3•9 years ago
|
||
I agree that we should use switchboard to do staged roll-out and can also do channel roll-outs, but do you really think we need to be cautious for this specific addition?
I could see being cautious for other changes could be more valuable.
So my question, why not just pushing it to all -- it's a great addition.
The only thing I would support is to actually to staged roll-out on a defined channel, and monitor cohorts usage of history and bookmark panel.
Flags: needinfo?(margaret.leibovic)
Assignee | ||
Comment 4•9 years ago
|
||
(In reply to Barbara Bermes [:barbara] from comment #3)
> I agree that we should use switchboard to do staged roll-out and can also do
> channel roll-outs, but do you really think we need to be cautious for this
> specific addition?
>
> I could see being cautious for other changes could be more valuable.
>
> So my question, why not just pushing it to all -- it's a great addition.
>
> The only thing I would support is to actually to staged roll-out on a
> defined channel, and monitor cohorts usage of history and bookmark panel.
Yes, this is what I'm proposing. Let's roll it out to beta users next week, and then if people are using the menu item (I suppose this is where we need some threshold to determine what we think is good), then we can roll it out to release users as well.
I also view this as a good opportunity to go through the motions of a staged roll-out, even if we know we want to release to all users. Let's test this out with a low-controversy feature like menu items, before we try to do more impactful things like notifications.
Flags: needinfo?(margaret.leibovic)
Comment 5•9 years ago
|
||
ok, so this will be 46 Beta next week and after x days that can be turned on for release 45 as well?
Flags: needinfo?(margaret.leibovic)
Comment 6•9 years ago
|
||
Staged rollout sounds good to me, no need to rush it to release. Tracking for 46 since this is a new feature.
Sylvestre, adding tracking? for 45 in case this ends up moving to release.
status-firefox45:
--- → ?
status-firefox46:
--- → affected
status-firefox47:
--- → affected
tracking-firefox45:
--- → ?
tracking-firefox47:
--- → +
Assignee | ||
Comment 7•9 years ago
|
||
This is something new: I'm asking for approval to merge this Switchboard config change to production. Just hitting the merge button on this PR would automatically turn this feature on for all Aurora/Beta users.
Approval Request Comment
[Feature/regressing bug #]: bug 1231792
[User impact if declined]: Users won't see bookmark/history menu items.
[Describe test coverage new/current, TreeHerder]: No automated tests, baked on Nightly for a few weeks. We should have UI telemetry data to tell us whether people are using these menu items, but I have not seen updated dashboards with that data.
[Risks and why]: Low-risk, enables two menu items that are currently disabled on aurora/beta. The main risk comes from using Switchboard, but it's much better to be taking that risk now with this small feature than later with a bigger one.
[String/UUID change made/needed]: None.
Flags: needinfo?(margaret.leibovic)
Attachment #8727425 -
Flags: approval-mozilla-beta?
Attachment #8727425 -
Flags: approval-mozilla-aurora?
Comment 8•9 years ago
|
||
Comment on attachment 8727425 [details] [review]
PR to enable bookmarks/history menu items on aurora/beta
Discussed this with Margaret, and it's OK by me.
Let's test this process out. If something goes wrong, we can fix it with Switchboard without having to wait for a new beta build.
Attachment #8727425 -
Flags: approval-mozilla-beta?
Attachment #8727425 -
Flags: approval-mozilla-beta+
Attachment #8727425 -
Flags: approval-mozilla-aurora?
Attachment #8727425 -
Flags: approval-mozilla-aurora+
Assignee | ||
Comment 9•9 years ago
|
||
I just merged this config change, the menu items should be live on aurora and beta.
Comment 10•9 years ago
|
||
Verified as fixed on Firefox 46 Beta 1. Tested on several devices
Comment 11•9 years ago
|
||
Ok, tracking in case we want to enable that in 45.
Updated•8 years ago
|
Assignee | ||
Comment 12•8 years ago
|
||
Using release version tracking flags is confusing here, because the config change here only enabled this for aurora/beta, not release.
I will create a PR to enable this on release, but shipping this feature can happen independently of shipping Firefox 46.
Assignee | ||
Comment 13•8 years ago
|
||
I'm requesting approval for this to make this process more transparent. For the future, I think we should create match cases with version numbers, instead of just app IDs, so that we can have things be automatically enabled when a new version moves to release.
We'll want to merge this tomorrow with the release of 46 if we want it to have the bookmark/history menu item. I don't think the precise timing really matters, so I don't want us to stress out about this too much.
Approval Request Comment
[Feature/regressing bug #]: bug 1231792
[User impact if declined]: no bookmark/history menu item
[Describe test coverage new/current, TreeHerder]: baked on beta
[Risks and why]: low-risk, can disable feature again with another PR
[String/UUID change made/needed]: none
Attachment #8745122 -
Flags: review?(s.kaspari)
Attachment #8745122 -
Flags: approval-mozilla-release?
Assignee | ||
Updated•8 years ago
|
Flags: needinfo?(lhenry)
Comment 14•8 years ago
|
||
Comment on attachment 8745122 [details] [review]
PR to enable bookmark-history experiment on all channels
(Comments/Questions on GitHub)
Attachment #8745122 -
Flags: review?(s.kaspari) → review+
Comment 15•8 years ago
|
||
Bookmarks and history are displayed in Menu. Verified as fixed on Firefox 47 Beta 1. Tested on One A2001 (Android 5.1.1), Nexus 9 (Android 6.0), ZTE Grand X (Android 4.0.4)
Comment 16•8 years ago
|
||
Comment on attachment 8745122 [details] [review]
PR to enable bookmark-history experiment on all channels
OK for 46 release.
Flags: needinfo?(lhenry)
Attachment #8745122 -
Flags: approval-mozilla-release? → approval-mozilla-release+
Assignee | ||
Comment 17•8 years ago
|
||
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•