Change Details

The #Code-Review migration to Phabricator is quite orthogonal to the RT and Bugzilla migrations, and we should start planning for it now. We need to request resources for the current quarter now, and in order to do this properly we need to have an initial plan that gives us an idea of the skills/roles needed and for how long. The basic elements of this plan can be extracted from the [[ https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals#Engineering_Community | WMF Engineering goals ]]: * Oct–Dec 2014 ** {T560} ** Decision on migrating continuous integration or not. * Jan–Mar 2015 ** Code review moved from Gerrit to Phabricator. CI too?

The #Code-Review migration to Phabricator is quite orthogonal to the RT and Bugzilla migrations, and we can start planning for it now. The basic elements of this plan can be extracted from the [[ https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals#Engineering_Community | WMF Engineering goals ]]: * October–December 2014 * Basic plan * January–March 2015 ** {T560} ** Decision on migrating continuous integration or not. * April–June 2015 ** Code review moved from Gerrit to Phabricator. CI too?

The #Code-Review migration to Phabricator is quite orthogonal to the RT and Bugzilla migrations, and we shouldcan start planning for it now. We need to request resources for the current quarter now, and in order to do this properly we need to have an initial plan that gives us an idea of the skills/roles needed and for how long. The basic elements of this plan can be extracted from the [[ https://www.mediawiki.org/wiki/Wikimedia_Engineering/2014-15_Goals#Engineering_Community | WMF Engineering goals ]]: * October–December 2014 * Basic plan * January–March 2015 ** {T560} ** Decision on migrating continuous integration or not. * Jan–Mar* April–June 2015 ** Code review moved from Gerrit to Phabricator. CI too?