[meta] Integrate with Fakespot to provide more reliable shopping experience
Categories
(Fenix :: Shopping, enhancement, P2)
Tracking
(Not tracked)
People
(Reporter: jmahon, Unassigned)
References
(Depends on 3 open bugs)
Details
(Keywords: meta, Whiteboard: [fxdroid][shopping][fakespot])
Attachments
(4 files)
Initiative summary to follow.
Miro board visualizing the current roadmap to completion.
Updated•1 year ago
|
Reporter | ||
Comment 1•1 year ago
|
||
Leaving a general "status update" comment in lieu of having all these items outlined in child tasks:
Last week:
- Introduced engineers to project & began connecting with Desktop/Fakespot teams
- Got estimates for all tasks
- Held scoping meetings
Plans for this week:
Clarify scope:
- [Daniela] Identify opportunities to minimize scope for the MVP
- [Android Eng] Re-estimate tasks to get further clarity on projected target release
- [Android Eng] Meet for implementation "kickoff" (technically we've already kicked off, just asynchronously)
Minimize unknowns:
- [Cathy] Write implementation planning doc (to review next week)
- [Rahul] Connect with Desktop & Fakespot engineers to learn and consult on API expectations
- [Rahul] Connect with Gijs/Jared to learn about OHTTP and whether we need to do anything about it on our end
Set up workflow:
- [Joe] Create miro board for at-a-glance view of project
- [Joe] Create all (currently known) tickets
- [Daniela/Chris] Connect this metabug into Jira appropriately
Updated•1 year ago
|
Updated•1 year ago
|
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Comment 3•1 year ago
|
||
Comment 4•1 year ago
|
||
Created a new QA meta bug to track all issues found by QA: https://bugzilla.mozilla.org/show_bug.cgi?id=1857438
Comment 5•1 year ago
|
||
Comment 6•1 year ago
|
||
Updated•1 year ago
|
Comment 7•9 months ago
|
||
The Android team has not been keeping our P1 bug list up to date, so we're resetting all our P1 bugs to P2 to avoid signalling that we're actively working on bugs that we're not. The BMO documentation https://wiki.mozilla.org/BMO/UserGuide/BugFields#priority says P1 means "fix in the current release cycle" and P2 means "fix in the next release cycle or the following (nightly + 1 or nightly + 2)".
If you are actively working on this bug and expect to ship it in Fx 122 or 123, then please restore the priority back to P1.
Updated•5 months ago
|
Description
•