Open
Bug 1795407
Opened 2 years ago
Updated 2 years ago
Create third party dependency upgrade policy
Categories
(Fenix :: General, task)
Tracking
(Not tracked)
NEW
People
(Reporter: csadilek, Unassigned)
Details
From github: https://github.com/mozilla-mobile/android-components/issues/8798.
Without having a regular process or policy to upgrade dependencies, it's easy to get behind. For example, we're currently on version 17 of Firebase but it's on 25. https://github.com/mozilla-mobile/android-components/issues/8459#issuecomment-713965989 This has the following impacts:
- lack of bug and security fixes
- potentially harder to upgrade to the newest version
We should consider creating such a policy. Ideally, we can share this policy with fenix as well because, afaik, they have no such policy.
┆Issue is synchronized with this Jira Task
Change performed by the Move to Bugzilla add-on.
Updated•2 years ago
|
Severity: -- → N/A
Type: defect → task
You need to log in
before you can comment on or make changes to this bug.
Description
•