Updates to the "iterations" and "blocking-loop" fields.

RESOLVED FIXED

Status

()

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: shell, Assigned: dkl)

Tracking

Production

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Hi, sorry to ask - but:

Can we change the dropdown option below "iterations" to be "39.3 - 30 Mar", the dates moved in a week for release.

Also - we're simplifying the blocking-loop flag - so we'll need fewer changes:
can we remove drop down options from "blocking-loop" for 35?, 35+, 36?, 36+, 37?, 37+ (keep 38? and keep 38+), 39?, 39+, 40?, 40+, 41?, 41+
Summary: Update some drop down items → Updates to the "iterations" and "blocking-loop" fields.
(Assignee)

Comment 1

4 years ago
(In reply to sescalante from comment #0)
> Hi, sorry to ask - but:
> 
> Can we change the dropdown option below "iterations" to be "39.3 - 30 Mar",
> the dates moved in a week for release.

Done

> Also - we're simplifying the blocking-loop flag - so we'll need fewer
> changes:
> can we remove drop down options from "blocking-loop" for 35?, 35+, 36?, 36+,
> 37?, 37+ (keep 38? and keep 38+), 39?, 39+, 40?, 40+, 41?, 41+

Before I do this I need to clarify. Do you mean the only number options available should be Fx38? and Fx38+ and all others should be disabled?

dkl
Flags: needinfo?(sescalante)
(Reporter)

Comment 2

4 years ago
Thanks DKL - sorry for the slow "need info" reply - I was on vacation.

We can remove drop down options from "blocking-loop" for ALL specific release targets: Fx35?, Fx35+, Fx36?, Fx36+, Fx37?, Fx37+, Fx38?, Fx38+, Fx39?, Fx39+, Fx40?, Fx40+, Fx41?, Fx41+

We've cleaned up the triage process to remove adding specific targets (since we just aren't that good at predicting the exact release we'll hit them).
Flags: needinfo?(sescalante)
(Assignee)

Comment 3

4 years ago
Done
Assignee: nobody → dkl
Status: NEW → RESOLVED
Last Resolved: 4 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.