Let's do it!

00:30 UTC like last time?

Yay!
I'm curious about the guestimation timeframe (for how long Phab might be down) to communicate, and how I/we can help (I have parttime plans for that UTC Friday but will definitely be around when needed!).

@greg, are you in?

sure: https://wikitech.wikimedia.org/w/index.php?title=Deployments&diff=136954&oldid=136951

Communicated to WMF Engineering and Product management.

Should we enable Countdown here? See https://phab-01.wmflabs.org/

PS: the fan of my laptop seems to love it...

Can we make it not do seconds? That is wholly distracting :)

I have no idea, but this countdown doesn't have (m)any configuration options.

Let's agree first on the exact time that RT and Phabricator will be pulled down to start the migration. @chasemp and @greg must agree on a reasonable timing. The hard deadline for the decision must be the end of Greg's Roadmap and Deployments weekly meeting today at 19:00 UTC. Once the time is confirmed, we will announce the migration plan.

Keeping the Unbreak Now priority while we confirm the migration start time.

Ouch, I wasn't aware that this downtime would affect Phabricator as well as RT. I think RT (with its relatively limited, internal user base) can be down for 24 hours with little notice, but for Phabricator at this point we should do better. Is (long) Phabricator downtime strictly necessary for this? If it is, we should probably do this during a weekend again, and with much more notice to other teams.

Any news?

@mark requested next Wednesday, discussed in ops meeting. Objections? (4 or 6 P.M. PST to midnight or 2A.M.)

Sounds good! 4pm, for your own sanity?

I think that would be ok, yes. The earlier times are much easier for me as they don't extend into the twilight hours as much.

@greg, are you ok with Wednesday 17 December at 4pm Pacific? If you are, then this is a decision.

Yeah, that should be fine.

What kind of downtime for phab are we expecting?

4 P.M. - Midnight maintenance.

@Aklapper, can you take care of the announcements? I would do it after the short maintenance break today, not to confuse people, but still today, a week before the migration.

In T76773#836325, @Qgil wrote:

@Aklapper, can you take care of the announcements?

Yeah, though really wondering where to make these announcements (we didn't document this in T473).

• wikitech-l and mediawiki-l are obvious candidates
• but does e.g. a banner on mediawiki.org make sense or is that overkill?
• Custom widget on the frontpage of https://phabricator.wikimedia.org (which probably not many people will see)?

And where do we redirect in those eight hours? Recycle https://www.mediawiki.org/wiki/Phabricator/Bugzilla_migration_weekend ? Abuse https://www.mediawiki.org/wiki/Phabricator/Maintenance ? New page?

Banner on mediawiki.org sounds like an overkill indeed.

Custom widget, you can recycle the one we have now.

Landing page for the redirect, see T76989

No banners on mediawiki.org for the RT migration. I suggest you don't bother sending to mediawiki-l.

I might suggest a site notice on wikitech perhaps?

In T76773#838286, @Krenair wrote:

I suggest you don't bother sending to mediawiki-l.

Why not? Not that we are not only announcing the RT migration, we are also announcing that Phabricator will be down 8 hours.

MediaWiki-l

MediaWiki announcements and site admin list
This is a multilingual list for help/support with running/configuring MediaWiki. It is intended for people who are running wikis with the MediaWiki software and for announcements of new versions, bug fixes, and security issues.

The announcements are available without the discussion in the mediawiki-announce list. Active development discussion will generally be in wikitech-l.

OK, fair. :)

Sent announcement email to 'wikitech-l', 'mediawiki-l' and internal 'engineering':
https://lists.wikimedia.org/pipermail/wikitech-l/2014-December/079816.html

so since you sent the announcements i guess that makes this task resolved. because now it's scheduled. right?

remove notice from phab front page? (or change to past tense)

Ooops! Done. Thank you.