Closed Bug 1297513 (snappy) Opened 8 years ago Closed 6 years ago

Automate generation of Firefox snap packages

Categories

(Release Engineering :: Release Automation: Snap, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: meta)

Tracking bug for all related automation and features.
Depends on: 1251407
Depends on: 1297514
Depends on: 1297516
Depends on: 1297519
Depends on: 1297520
Depends on: 1297524
Depends on: 1297526
Depends on: 1297530
Depends on: 1297531
Have we bug to generate nightly builds yet?
Priority: -- → P3
Depends on: 1346246
Any update on the official Snap package?
Depends on: 1436445
Depends on: 1436457
Depends on: 1436468
Depends on: 1441922
No longer depends on: 1441922
Depends on: 1451694
Depends on: 1456164
Depends on: 1456431
Component: Release Automation: Other → Release Automation: Snap
Depends on: 1461848
Depends on: 1517171
Depends on: 1461759
Depends on: 1525233

(In reply to Sylvestre Ledru [:sylvestre] from comment #3)

Available https://snapcraft.io/firefox

If this bug and bug 1297514 are not fixed, how is that happening? (they are marked as coming from Mozilla)

(In reply to Mike Hommey [:glandium] from comment #4)

(In reply to Sylvestre Ledru [:sylvestre] from comment #3)

Available https://snapcraft.io/firefox

If this bug and bug 1297514 are not fixed, how is that happening? (they are marked as coming from Mozilla)

This looks like a metabug for tracking ongoing work; I'm unclear on the status of bug 1297514.

Keywords: meta

I confirm Mozilla is the entity publishing https://snapcraft.io/firefox. This current bug was about making the Snap package itself, whereas bug 1297514 was about publishing it it.

We now have a dedicated component "Release Engineering :: Release Automation: Snap". So I don't think we need open meta-bugs anymore. I'm going to close both.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
No longer depends on: 1664824
You need to log in before you can comment on or make changes to this bug.