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.
the fields have been added to the schema, but still need to be configured, reopening.
Committing to: bzr+ssh://email@example.com/bmo/4.0/
Committed revision 8432.
Committing to: bzr+ssh://firstname.lastname@example.org/bmo/4.2/
Committed revision 8481.