Part of https://www.mediawiki.org/wiki/Phabricator/Plan
The current plan (in progress):
| Title | Reference | Author | Source Branch | Dest Branch | |
|---|---|---|---|---|---|
| maintain-kubeusers: bump to 0.0.122-20240221143623-84a40909 | repos/cloud/toolforge/toolforge-deploy!203 | project_1317_bot_df3177307bed93c3f34e421e26c86e38 | bump_maintain-kubeusers | main | |
| user: fix bad permission for skel-copied files | repos/cloud/toolforge/maintain-kubeusers!14 | dcaro | fix_permissions | main | |
| maintain-kubeusers: bump to 0.0.121-20240221131329-d6f9cd11 | repos/cloud/toolforge/toolforge-deploy!201 | project_1317_bot_df3177307bed93c3f34e421e26c86e38 | bump_maintain-kubeusers | main | |
| user: copy stuff from /etc/skel if there's anything | repos/cloud/toolforge/maintain-kubeusers!13 | dcaro | copy_skel | main | |
| Update mathjax-node and texvcjs | repos/mediawiki/services/mathoid!3 | physikerwelt | T137787 | main |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Qgil | T553 Engineering Community team goals for October 2014 | |||
| Resolved | Qgil | T174 Launch Wikimedia Phabricator Day 1 | |||
| Resolved | Qgil | T175 Nominate a team in charge of deploying and maintaining Wikimedia Phabricator code | |||
| Resolved | • RobLa-WMF | T17 Allocate resources for the migration and maintenance | |||
| Invalid | Qgil | T13 Plan to migrate everything to Phabricator |
gpaumier wrote on 2014-04-09 15:34:08 (UTC)
Content moved from the RfC page (specifics of ticket migration should go into T39: Set up permissions for Phabricator and T63: Phabricator requires a "real name" to register):
Potential sequences of migration:
- Speed: We could push to quickly have the new tool in place, given the limitations of our existing tools, and afterwards add missing functionality that we consider a requirement.
- Functional completeness: We could first make the prefered new tool provide nearly all functionality we consider required, and then migrate to the new tool.
- Later migration of tickets: We could start a fresh instance of the new tool with a higher number (100.000) to give us enough buffer to import Bugzilla and/or other tickets at a later date. We close existing infrastructure tools for ticket creation so new tickets are only handled in the new tool.
In any case, we should not add yet another tool to the mix while keeping the current usage of all our existing tools.
thiemowmde wrote on 2014-04-29 14:20:45 (UTC)
I really think we need Bugzilla, Gerrit and possibly GitHub integration for a few months. You can't just stop the old tools and copy everything to Phabricator. Migration needs time.
qgil wrote on 2014-04-30 16:17:53 (UTC)
Our current thinking is that an official Wikimedia Phabricator would open at least with all Bugzilla reports imported as Maniphest tasks. On the same day, Bugzilla would work only in read-only mode. The rest is all negotiable, and probably more akin to progressive migrations.
The full Bugziilla move on day 1 is the only way to assure a complete import of Bugzilla data to Phabricator. We cannot have two moving targets hoping to keep them in sync. Also, as disruptive as closing Bugzilla during a weekend sounds, the alternative of sending users to Bugzilla for some bugs and to Maniphest for some other bugs would be even worse. If you want to discuss the specific case of the Bugzilla migration, please do it at T39: Set up permissions for Phabricator.
qgil wrote on 2014-05-13 23:12:18 (UTC)
The general migration plan for Day 1 has been agreed and is documented at https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan
The details about the migration of Bugzilla, RT, Mingle, and Trello are discussed in their tasks. Gerrit and Jenkins plans are not defined yet, but they fall out of the scope of Day 1.
Therefore, the overall plan is resolved for Day 1. Editing priorities etc accordingly.
qgil wrote on 2014-07-09 16:54:34 (UTC)
The plan keeps evolving -- for good. https://legalpad.wikimedia.org/ has been deployed as a single-purpose instance. It will be merged to the main Wikimedia Phabricator, probably by Day 1.
The next step at https://www.mediawiki.org/wiki/Phabricator/Plan#Migration_plan is to set up an instance in production with Wikimedia SUL enabled. T314: "Invalid JWT signature from /identify" trying to log in is done and being tested in this Labs instance as well as the Legalpad site. @Rush has been playing with ways for claiming users identities in other systems by verifying the email addresses related to them. Andre and Rush still have to decide the exact blockers for the deployment of this instance, watch for details at T294: Super epic: Refactor moveToStep into a smaller function, make controllers for each step.
I'll get back to this task after T15: Migrate Bugzilla to Phabricator and T824: Phabricator as Wikimedia software project management tool.
is this ticket usually tracking things or can we close it? I don't think anyone is referencing it.
It's value is basically the Blocked By tasks. Maybe the original function of this task is now better covered by https://www.mediawiki.org/wiki/Phabricator#Migration_timeline
since T18 is going to be a ways out and mingle and trello is a collection of teams doing their own thing I think this task is not really tracking anything useful now (especially considering the wiki)
Resolving as Invalid at this point. Se the reasoning in the comments above. The overall migration can be followed at https://www.mediawiki.org/wiki/Phabricator#Migration_timeline
Mentioned in SAL (#wikimedia-analytics) [2017-02-01T17:27:06Z] <joal> Restarting 2 webrequest-load text jobs that failed during NM restart (2016-02-01T11:00 and T13:00)