Closed Bug 669303 Opened 13 years ago Closed 12 years ago

release configs should support old builds coming from a different repository

Categories

(Release Engineering :: Release Automation: Other, defect, P5)

Product:
Release Engineering
Component:
Release Automation: Other
Platform:
x86_64
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: catlee, Unassigned)

Details

(Whiteboard: [automation]) 

In the new rapid release world we may frequently have the situation where Firefox X is released before Firefox (X+1)b1 is. For 5.0, drivers wanted 5.0b7 users updated to 5.0 and then to 6.0b1.

Our release configs assume that the old build was generated from the same repository as the current build. AIUI, the only thing that oldBaseTag is used for is shipped-locales. We should be able to get that from a different repository.
Priority: -- → P5
Whiteboard: [automation]
No longer blocks: hg-automation
Mass move of bugs to Release Automation component.
Blocks: hg-automation
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: hg-automation
We don't update users across channels anymore, I don't think we care about this.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.