release configs should support old builds coming from a different repository

RESOLVED WONTFIX

Status

P5
normal
RESOLVED WONTFIX
8 years ago
5 years ago

People

(Reporter: catlee, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [automation])

(Reporter)

Description

8 years ago
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.
(Reporter)

Updated

7 years ago
Priority: -- → P5
Whiteboard: [automation]
No longer blocks: 714371
Mass move of bugs to Release Automation component.
Blocks: 714371
Component: Release Engineering → Release Engineering: Automation (Release Automation)
No longer blocks: 714371
We don't update users across channels anymore, I don't think we care about this.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WONTFIX
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.