Page MenuHomePhabricator

Deploy CentralNotice schema change
Closed, ResolvedPublic1 Estimated Story Points


The easiest deployment procedure is probably the sql.php method from tin, documented here:

Event Timeline

awight claimed this task.
awight raised the priority of this task from to Medium.
awight updated the task description. (Show Details)
awight moved this task from Backlog to Pending Deployment on the Fundraising Sprint N*E*R*D board.
awight added subscribers: gerritbot, Liuxinyu970226, Aklapper and 2 others.
awight renamed this task from Deploy schema change to Deploy CentralNotice schema change.Jul 1 2015, 10:27 PM
awight set Security to None.

Removing from the sprint, after discussion. This can happen much closer to the time we deploy the feature proper.

A slightly mutant BLOB version has been deployed to master hence betawiki, note that the rest of the migration has to happen in a second patch now.

Is this blocked on something that makes us want to wait?

It's deployed to the beta cluster, but not to production. It could be deployed to production (the BLOB issue mentioned above is OK, no need for a second patch), though I was thinking of waiting until we tested everything on the beta cluster... Just on the intuition of not wanting to send anything to production until the user-facing feature (in this case, banner history) has been seen working as promised on beta. It doesn't necessarily have to be that way, though....