release tracking flag refresh (21)

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Administration
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: glob, Assigned: glob)

Tracking

Production

Details

(Assignee)

Description

4 years ago
add release 21
disable release 17
seamonkey needs 2.18

when the last batch of custom fields were added, we encountered an issue which resulted in a failure of the db slaves (bug 821197).  i'd like to avoid a repeat of that scenario.

these fields need to be added early this week -- normally i add them at around sunday 8pm us/pacific, but i'd like to give our DBAs a heads-up, so i'm looking at doing this monday night if possible.


i'm thinking of adding a single field at a time, and watching the slaves to ensure they go mad.  open to better suggestions :)
All fields for release 21 were successfully added.

Marking as resolved.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

4 years ago
the fields have been added to the schema, but still need to be configured, reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(Assignee)

Comment 3

4 years ago
Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.0/
modified extensions/BMO/lib/Data.pm
Committed revision 8432.

Committing to: bzr+ssh://bjones%40mozilla.com@bzr.mozilla.org/bmo/4.2/
modified extensions/BMO/lib/Data.pm
Committed revision 8481.
Status: REOPENED → RESOLVED
Last Resolved: 4 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.