Hi, if you were wondering what is going on in Phabricator land...
Summary: You can see
https://phabricator.wikimedia.org , you can touch
https://phab-01.wmflabs.org/ , you will have a chance to provide feedback
about the Bugzilla migration before the migration, based on a test instance
with a sample of bugs imported.
In detail:
*
https://phabricator.wikimedia.org exists as a read-only instance and it
contains the tasks that were migrated from the now decommissioned
fab.wmflabs.org. Registration is disabled while we fix some tasks --
details at
https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan .
We will post here when the issues have been fixed.
* We have a test instance at
https://phab-01.wmflabs.org/ where you can
play as much as you want. This instance is for testing and experimenting
only. Anything in there can disappear in a whim.
* When we open
phabricator.wikimedia.org, the creation of new projects will
be still disabled. Existing projects will be able to continue their work,
but we are asking new projects to wait a few weeks, until we complete the
Bugzilla migration. It's going to be still a bumpy road before Day 1, and
we want to control the impact of these disruptions as much as possible.
* RT migration will follow. Details will be shared in advance.
* Bugzilla migration will follow. Details will be shared in advance as
well, but we have a rough idea of the sequence of steps. Details available
in the migration plan linked above, pasted here for convenience:
1. Earliest possible/expected date: October 06 but favoring Friday
October 10 to interrupt engineering less (starting over the weekend).
Bugzilla downtime expected of 1-3 days. Checklist:
2. Instructions to use Phabricator for bug reporting and project
management.
3. Documentation of data and features that will not be available in
Phabricator after the migration.
Phabricator test instance available with a sample of Bugzilla reports
imported automatically (say 1 of each 10, about 700 reports).
4. At least one week of margin to receive community feedback and
implement improvements.
5. Documentation of the migration process detailing sequence of steps and
timeline expected.
6. Go-NoGo meeting with the Phabricator team (Andre, Chase, Mukunda,
Quim), Erik, Rob, MarkB, and Greg.
Stay tuned. :)
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil