Move custom fields for inserted 3.5/3.6 releases

RESOLVED FIXED

Status

()

RESOLVED FIXED
8 years ago
7 years ago

People

(Reporter: dveditz, Assigned: marcia)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
We are inserting another 3.5/3.6 release and need to rename existing custom values to make room. The following should be done in order


field              action    value(s)
-------------      ------    --------
blocking1.9.2      rename    .16+  to .17+
blocking1.9.2      add       .16+
status1.9.2        rename    .16-fixed  to .17-fixed
status1.9.2        add       .16-fixed

blocking1.9.1      rename    .18+  to .19+
blocking1.9.1      add       .18+
status1.9.1        rename    .18-fixed to .19-fixed
status1.9.1        add       .18-fixed


I'll be doing the equivalent with the approval flags.

Then we need to fix up bug 642395 to reflect the original values, blocking/approved-for/fixed-in 3.6.16 and 3.5.18
(Reporter)

Updated

8 years ago
Group: core-security
(Reporter)

Updated

8 years ago
Group: core-security
Resolving fixed as I have made the requested changes.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.