Closed Bug 1191896 Opened 10 years ago Closed 10 years ago

Determine how many releases back Firefox update tests should handle, and how to work with watershed releases

Categories

(Release Engineering :: Release Automation, defect)

Product:
Release Engineering
Component:
Release Automation
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1173976

People

(Reporter: whimboo, Unassigned)

Details

The following request has not been implemented on bug 1148546 and therefore needs a separate bug. A definition which hasn't been fully agreed on yet is how many releases back we need those tests to be run. The support matrix we agreed on in Portland last year can be found here: https://github.com/mozilla/mozmill-ci/issues/535 Robert, maybe you can repeat what specifically you need. Thanks.
Flags: needinfo?(kairo)
Is this a dupe of bug 1173976?
Blocks: 1182796
Yes, and hurray for a dupe! :)
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(kairo)
Resolution: --- → DUPLICATE
Whiteboard: [qa-automation-blocked]
No longer blocks: 1182796
No longer depends on: 1148546
(In reply to Henrik Skupin (:whimboo) from comment #0) > The support matrix we agreed on in Portland > last year can be found here: https://github.com/mozilla/mozmill-ci/issues/535 The needs we specified there have not changed.
You need to log in before you can comment on or make changes to this bug.