Closed
Bug 1432692
Opened 8 years ago
Closed 7 years ago
Disable Android Background Services product
Categories
(bugzilla.mozilla.org :: Graveyard Tasks, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mcomella, Assigned: dylan)
References
Details
To my knowledge, the "Android Background Services" product is no longer maintained and I think we should prevent new bugs from being filed against it.
Android Background Services is a historic separation of the Firefox for Android repositories: the main Firefox for Android development happened in mozilla-central and Android background services (e.g. sync) were developed by another team on github ([1] is the now archived repo).
For a short while, bugs for related features were still being filed in the background services product but, afaik, they've since moved to Firefox for Android (e.g. :grisha mentions accounts/sync work is now in Firefox for Android on IRC [2]).
By leaving the Android Background Services component open, I have the following concerns:
- Users unfamiliar with the product will file bugs there
- Filed bugs will not get triaged (e.g. there are no triage owners for the whole product)
I would propose:
- Prevent new bugs from being filed against the product (can this be done? Is this "disabling"?)
- Removing the product from the bugzilla product landing pages
- I'll begin the process of moving open bugs to the appropriate Firefox for Android components. My team is the new core triage owner for the general Firefox for Android product so I feel this would fit into our responsibility.
[1]: https://github.com/mozilla-services/android-sync
[2]: https://mozilla.logbot.info/mobile/20180124#c14180719
Reporter | ||
Comment 1•8 years ago
|
||
FYI: I sent out a mailing list post requesting feedback so if you wait a few days and there are no new comments in this bug, we can be more sure there are no current users of the product: https://mail.mozilla.org/pipermail/mobile-firefox-dev/2018-January/002388.html
Comment 2•8 years ago
|
||
+1 to doing this. There are still some open bugs in the component, I see 73 there may be security bugs. If the bugs are useful we should migrate them to Firefox for Android or close them. Should be quick if the right people are around and the main thing that is discussed is should we move the bug to Firefox for Android.
https://bugzilla.mozilla.org/buglist.cgi?list_id=13981347&resolution=---&classification=Client%20Software&classification=Components&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&product=Android%20Background%20Services
Depends on: 1432965
I've gone ahead and disabled Android Background Services for new bugs. If I don't hear by friday, I'll ask Dylan to graveyard to component.
Component: Administration → Graveyard Tasks
Reporter | ||
Comment 4•8 years ago
|
||
I triaged all the open bugs in Android Background Services today – there are no more open bugs.
Emma, what is the graveyard? I'd like to keep the product and its bugs around for historical searches. Will the graveyard keep the bugs around for this? Note: I asked the same question in https://bugzilla.mozilla.org/show_bug.cgi?id=1432697#c2
Reporter | ||
Comment 5•8 years ago
|
||
Note: I don't have sec-access so I may have missed those bugs if they exist.
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(ehumphries)
Comment 6•8 years ago
|
||
Graveyard is a classification. Users can still search for bugs and the bug id number URL will still take you to the bug. https://bugzilla.mozilla.org/query.cgi?query_format=advanced
Flags: needinfo?(ehumphries)
Reporter | ||
Comment 7•8 years ago
|
||
Dylan, can you graveyard the component, as per comment 19? (or perhaps this will happen automatically?)
Flags: needinfo?(dylan)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → dylan
Flags: needinfo?(dylan)
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Comment 8•7 years ago
|
||
It still appears on https://bugzilla.mozilla.org/enter_bug.cgi?full=1
Flags: needinfo?(dylan)
You need to log in
before you can comment on or make changes to this bug.
Description
•