Which 30 minute slot are you thinking of? Would it be always the same slot, or depending? Do you plan to use it regularly, or would we be booking the option to do it?

Syncing this with Greg's deployments weekly newsletter is a good idea. This and a notice in the homepage will save us regular notifications to wikitech-l.

In T76522#806313, @Qgil wrote:

Which 30 minute slot are you thinking of? Would it be always the same slot, or depending? Do you plan to use it regularly, or would we be booking the option to do it?

Syncing this with Greg's deployments weekly newsletter is a good idea. This and a notice in the homepage will save us regular notifications to wikitech-l.

I requested something semi-sane for UTC-6 and UTC-8. My thought is to have a block reserved weekly for needed Phabricator actions at the same time each week. We would probably use it once or twice a month, but it's there and expected in case either way. Rarely can we not wait a week, and if it's more urgent it wouldn't be something we waited to announce anyway.

Just chatted with Chase on IRC. Wednesdays at 7am Pacific. Will be in next week's calendar (and on-going).

@Legoktm we should get your stuff in then. Sorry more wait, it's all schedule shuffling :)

@Qgil, how best can we make this known?

Thanks @greg

See description. Also, what do you think about https://phab-01.wmflabs.org/ ?

Alright, maybe we don't need the countdown for the weekly maintenance breaks.

I have added a panel to the homepage, and a section here: https://www.mediawiki.org/wiki/Phabricator#Weekly_update_.2F_maintenance_window

@Aklapper, can you continue with the communication, as part of the regular process for communicating service interruptions?

T77082 is useful. What about this: after a new upgrade has been completed, a new task for the next upgrade can be created (even if the date is not known yet). This way we can add it as blocker of the tasks that have been fixed upstream, and whatever else is waiting for the update.

we could have a generic next upgrade task, or make a project to mark these tasks blocked by upgrade. In practice we don't always know how far up to the chain we can go because things in HEAD could be contentious and/or needing more review. But yeah in general sounds sane.