Closed Bug 483233 Opened 15 years ago Closed 15 years ago

Create release automation factory/build steps for partner repacks

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: coop, Assigned: coop)

References

Details

Once we have a script in place that can batch up partner repacks (bug 483232), we can hook up that script to the tail-end of the current release automation process.

We only do partner repacks for 3.0 right now, but we should future-proof this as much as possible, i.e. be hg-aware.

We'll also need to decide on where the created repacks are going to be staged for QA access.
Priority: -- → P3
Status: NEW → ASSIGNED
Priority: P3 → P2
Depends on: 486528
Blocks: 486573
These patches landed as part of bug 483232.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.