Closed
Bug 1894192
Opened 1 year ago
Closed 1 year ago
Please create "Release Engineering :: Release Automation: Packaging" and retire "Release Automation: Snap"
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jlorenzo, Assigned: dkl)
References
(Depends on 1 open bug)
Details
Other Requests
Requested changes
New component:
- Product: Release Engineering
- Component: Release Automation: Packaging
- Description: Issues with Mozilla's official Firefox packages (e.g.: .deb, Flatpak)
- Default Assignee: nobody@mozilla.org
- Triage Owner: gbustamante@mozilla.com
In addition, we should tweak the description of this component:
- Product: Firefox Build System
- Component: Third Party Packaging
- New description: Repacks of the Firefox releases by third party vendors (e.g.: Snap, RPM, ...)
Finally, let's retire this component (there should be no bugs left open there):
- Product: Release Engineering
- Component: Release Automation: Snap
Context
A while ago, we created the component Release Automation: Snap. This predates bug 1452285, but I can't find the actual one. Back then, Mozilla used to build the Snap package. Canonical took over it a few years ago which notably led to the creation of Firefox Build System :: Third Party Packaging (bug 1775284). Similarly, bug 1620874 created Release Automation: Flatpak and bug 1647688 closed it.
Since then, several things have changed. What's the situation today?
- Snap remain built by Canonical (i.e.: no change). Thus, it should belong to
Third Party Packaging - Flatpak is still here and is exclusively build and published by MoCo (and more precisely the Release Engineering team). So it should belong to
Release Automation: Packaging - Earlier this year, we officially shipped a debian package (bug 1799516). It should belong to
Release Automation: Packagingtoo.
I'm happy to provide additional details if needed.
| Assignee | ||
Comment 1•1 year ago
|
||
all done.
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•