Last week's SEDE update left out poor Stack Overflow. And it did it again this week.
Let me answer on behalf of Nick Craver:
Though we'll be a little rocky making this time until we're back in New York - it's when it should happen!
For the curious:
We have a kerberos pass-through auth issue that's ~ 60% likely to fail in the refresh for complicated reasons. Ultimately we need to restart the Colorado SQL servers to use the correct SPNs for Kerberos...and we don't want to do that while they're live for hopefully obvious reasons :)
This was left as a comment on my pull request to fix the day mentioned in the FAQ: Change the FAQ to mention Sunday as the update date