Page MenuHomePhabricator

Next Phabricator upgrade: 2015-06-24
Closed, ResolvedPublic


MediaWiki / Phabricator / Maintenance

Event: E19: Phabricator Deployment Wednesday, June 24th Midnight UTC

Tasks solved upstream but still not deployed in should add this task as blocker.

Previous deployment: T101929

Event Timeline

mmodell claimed this task.
mmodell raised the priority of this task from to Medium.
mmodell updated the task description. (Show Details)
mmodell added a project: Phabricator.
mmodell updated the task description. (Show Details)
mmodell set Security to None.

@Christopher: Upstream phabricator is now publishing updates on twitter when they upgrade their own cluster, so perhaps we should endeavor to follow the same stable version that they push:

Negative24 renamed this task from Next Phabricator upgrade 2015-06-17 to Next Phabricator upgrade: 2015-06-17.Jun 16 2015, 2:36 AM

@mmodell That is a good idea.

Also, please post (publicly) the current diffusion commit of Wikimedia Phabricator for external reference. It is difficult to reconcile the git commit hashes in gitblit with the upstream revisions.

Upstream is running from 6 June.

Last week, you pulled HEAD (10 June) right?

So, does not this mean that Wikimedia production is currently ahead of the upstream cluster?

Is the update going to include the new UI?

The new UI is in a separate branch and not in master, see

I couldn't log in to labs to test the latest update so today's deployment window didn't get used. I guess this has to be rescheduled.

mmodell renamed this task from Next Phabricator upgrade: 2015-06-17 to Next Phabricator upgrade: 2015-06-24.Jun 18 2015, 1:38 AM
mmodell updated the task description. (Show Details)

@Christopher: The upstream project just recently started running a 'stable' release - they even have a stable branch of libphutil, arcanist and phabricator. I have begun syncing up with the stable branch instead of master, and we are now nearly, but not quite, up to date with upstream/stable.

Also note: Now that we have merges in our fork, our SHAs will no longer match upstream's, even when we are running nearly-identical code (We have merged a few tiny WMF-specific changes at this point)

@mmodell Since most of Wikimedia's custom code has been made into an extension, could we get the small amount of code that is being merged in also into an extension? This would make deployments simpler and easier to track. Perhaps just a misc extension if code is too small to be made into a full extension.

@Negative24: unfortunately, no. Some changes don't work as extensions as extensions do not overlay or override built-in/core functionality. Extensions are only viable for situations where there is an explicit integration point built in to the upstream application.

Hacks to override things that upstream explicitly doesn't support modifying, can't be done with extensions.