Bugzilla-Phabricator migration (almost) completed

List overview All Threads
Download

newer

older

Composer and the end user of...

RFC about extensions continuous...

Quim Gil

24 Nov 2014 24 Nov '14

7:41 a.m.

Happy Monday! We did it. https://phabricator.wikimedia.org now contains all the Bugzilla reports. If you need to check the original Bugzilla, it can be found at https://old-bugzilla-wikimedia.org (never mind the certificate warning, it will go away today or so). Important notes: * If your Bugzilla activity still hasn't been assigned to you, just wait. bzimport is processing the data of about 800 users. It assigns tasks first, then comments. Don't be surprised if you see a task assigned to you, while your comments still belong to bzimport. * Another ongoing background task: after injecting 73k tasks, it is possible that not all the content is indexed yet, so some search results might still be missing. * Join and watch the projects that matter to you. We have almost 700 new projects imported that nobody is watching currently. This is especially relevant if you were "default CC" in Bugzilla components. Details: https://www.mediawiki.org/wiki/Phabricator/Help#Receiving_updates_and_notif… and https://phabricator.wikimedia.org/T75699 * Do not change project names and policies for now. You may break links in Phabricator and mediawiki.org. See https://www.mediawiki.org/wiki/Phabricator/Requesting_a_new_project#Guideli… * Bugzilla URLs redirect to Phabricator (most of them) or old-bugzilla (some). Details: https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla#Redirected_URLs_… If you find bugs, please report them under the "Phabricator" project. If you need support, ask in #wikimedia-devtools. As usual, all the relevant details can be found at https://www.mediawiki.org/wiki/Phabricator/versus_Bugzilla BIG THANK YOU to everybody involved in this big, long, and complex migration. It has been really exciting to deploy a Phabricator instance with 75k tasks, the biggest Maniphest container we are aware of. And well, this is only the beginning. Right now we will focus in the most urgent post-Bugzilla-migration tasks, while starting to prepare the RT migration. Your tasks, comments, and tokens are welcome. Check the current backlog at https://phabricator.wikimedia.org/maniphest/query/y2CdmZwKv3oZ/#R -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

Show replies by date

Isarra Yos

24 Nov 24 Nov

7:45 a.m.

On 24/11/14 07:41, Quim Gil wrote:

...

To clarify the typo, that should be https://old-bugzilla.wikimedia.org . Also this is all pretty awesome. -I

Chad

5:23 p.m.

On Sun Nov 23 2014 at 11:45:32 PM Isarra Yos <zhorishna(a)gmail.com> wrote:

...

On 24/11/14 07:41, Quim Gil wrote:

Happy Monday! We did it. https://phabricator.wikimedia.org now contains all the

Bugzilla

reports. If you need to check the original Bugzilla, it can be found at https://old-bugzilla-wikimedia.org (never mind the certificate warning,

will go away today or so).

To clarify the typo, that should be https://old-bugzilla.wikimedia.org . Also this is all pretty awesome.

This is really really awesome you guys. Major props to the entire team for getting this done. Only problems I see at this point are cosmetic and totally fixable and tasks are already filed :) -Chad

James Forrester

5:32 p.m.

On 24 November 2014 at 09:23, Chad <innocentkiller(a)gmail.com> wrote:

...

On Sun Nov 23 2014 at 11:45:32 PM Isarra Yos <zhorishna(a)gmail.com> wrote:

On 24/11/14 07:41, Quim Gil wrote: > Happy Monday! > > We did it. https://phabricator.wikimedia.org now contains all the

Bugzilla reports.

This is really really awesome you guys. Major props to the entire team for getting this done. Only problems I see at this point are cosmetic and totally fixable and tasks are already filed :)

+1. Brilliant work, everyone. :-) J. -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester

Alex Monk

5:47 p.m.

+1 from me as well. Great work to everyone involved in this migration. On 24 November 2014 at 17:32, James Forrester <jforrester(a)wikimedia.org> wrote:

...

On 24 November 2014 at 09:23, Chad <innocentkiller(a)gmail.com> wrote:

On Sun Nov 23 2014 at 11:45:32 PM Isarra Yos <zhorishna(a)gmail.com>

wrote:

On 24/11/14 07:41, Quim Gil wrote: > Happy Monday! > > We did it. https://phabricator.wikimedia.org now contains all the

Bugzilla reports.

This is really really awesome you guys. Major props to the entire team

for

getting this done. Only problems I see at this point are cosmetic and totally fixable and tasks are already filed :)

+1. Brilliant work, everyone. :-) J. -- James D. Forrester Product Manager, Editing Wikimedia Foundation, Inc. jforrester(a)wikimedia.org | @jdforrester _______________________________________________ Wikitech-l mailing list Wikitech-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Matthew Flaschen

25 Nov 25 Nov

6:09 a.m.

On 11/24/2014 12:23 PM, Chad wrote:

...

This is really really awesome you guys. Major props to the entire team for getting this done.

Agreed, this is awesome. Thank you. Matt Flaschen

Antoine Musso

24 Nov 24 Nov

5:53 p.m.

Le 24/11/2014 08:41, Quim Gil a écrit :

...

We did it. https://phabricator.wikimedia.org now contains all the Bugzilla reports.

Hello, It is working nicely and the transition has been very smooth for my use cases. I still don't understand how we ended up starting the migration to Phabricator. I first heard of people willing to move to Phabricator back in January while I was in San Francisco. I am still unsure whether there was a real plan or whether those people were sensing my opinion on it. After a couple beers and hours of discussion about bug and workflows, I was pretty much convinced it was a good idea and said so. I was less convinced about us migrating in "just 2 weeks" though :-) Whatever cabal is running behind, that is a nice move. Thank you! Thank you for anyone that got involved in one way or an other in this challenging move. You all did a very nice and professional works other those last months. I am proud of Wikimedia. -- Antoine "hashar" Musso

Arthur Richards

6:17 p.m.

This is phabulous news! On Mon, Nov 24, 2014 at 10:53 AM, Antoine Musso <hashar+wmf(a)free.fr> wrote:

...

Le 24/11/2014 08:41, Quim Gil a écrit :

We did it. https://phabricator.wikimedia.org now contains all the

Bugzilla

reports.

-- Arthur Richards Team Practices Manager [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687

S Page

10:11 p.m.

phantastic! I suggest phuket <https://en.wikipedia.org/wiki/Phuket_Province> for the devtools team party/recovery/planning offsite. So far the Phabricator TNNNN task number of every BZ URL in my browser autocompletion is its bug number + 2000. Is this a happy coincidence? On Sun, Nov 23, 2014 at 11:41 PM, Quim Gil <qgil(a)wikimedia.org> wrote:

...

It has been really exciting to deploy a Phabricator instance with 75k tasks, the biggest Maniphest container we are aware of.

That explains the new Mercedes purchased by our sales rep at Facebook :) And well, this is only the beginning. Right now we will focus in the most

...

urgent post-Bugzilla-migration tasks, while starting to prepare the RT migration. Your tasks, comments, and tokens are welcome. Check the current backlog at https://phabricator.wikimedia.org/maniphest/query/y2CdmZwKv3oZ/#R

I'll be converting some of Flow's tasks in Trello to Phabricator, using string and glue or whatever. I invite anyone else attempting project migration to https://phabricator.wikimedia.org/T36 and the team practices mailing list https://lists.wikimedia.org/mailman/listinfo/teampractices -- =S Page Features engineer

Matthew Flaschen

25 Nov 25 Nov

6:12 a.m.

On 11/24/2014 05:11 PM, S Page wrote:

...

I doubt it, unless https://phabricator.wikimedia.org/T1998 , https://phabricator.wikimedia.org/T1999 , and https://phabricator.wikimedia.org/T2000 are all super-secret security bugs. :) Matt Flaschen

Andre Klapper

5:35 p.m.

On Mon, 2014-11-24 at 14:11 -0800, S Page wrote:

...

So far the Phabricator TNNNN task number of every BZ URL in my browser autocompletion is its bug number + 2000. Is this a happy coincidence?

It's a gift that took Chase (and Springle IIRC) a while to implement, based on past discussions in https://phabricator.wikimedia.org/T857 andre -- Andre Klapper | Wikimedia Bugwrangler http://blogs.gnome.org/aklapper/

Antoine Musso

11:06 p.m.

Le 25/11/2014 18:35, Andre Klapper a écrit :

...

On Mon, 2014-11-24 at 14:11 -0800, S Page wrote:

> So far the Phabricator TNNNN task number of every BZ URL in my browser > autocompletion is its bug number + 2000. Is this a happy coincidence?

It's a gift that took Chase (and Springle IIRC) a while to implement, based on past discussions in https://phabricator.wikimedia.org/T857

That is a nice trick and very easy to remember. Anyway, the bugzilla redirector works just fine ;-] Kudos again. -- Antoine "hashar" Musso

Matthew Flaschen

6:18 a.m.

On 11/24/2014 02:41 AM, Quim Gil wrote:

...

* Join and watch the projects that matter to you. We have almost 700 new projects imported that nobody is watching currently. This is especially relevant if you were "default CC" in Bugzilla components.

You may or may not want to do this, depending what you're looking for. If you are just "Subscribed" to a project, you will still see anytime the project is a: * Subscriber * Reviewer or Auditor (doesn't apply yet until we use Phabricator for code review) This means adding the project itself as a CC (this may not be used commonly yet, but it works) will in turn mean any subscribers to the project see all updates to that task (or mock, or whatever). "Watch", on the other hand, makes you see absolutely *everything* that happens to every task in the project. It's even more all-encompassing than Bugzilla's default CC. With default CC you can unsubscribe to an individual bug after being initially CCed. With Watch, it's all or nothing. Regardless, you will also see any updates to tasks where you're individually CCed or assigned. See https://secure.phabricator.com/T6113#76710 . I believe it should be possible to use Herald to setup default CC with semantics similar to Bugzilla (you're CCed initially, but you can unCC to an individual task). Matt Flaschen

Quim Gil

10:30 a.m.

(Top posting for extra attention) About default CCs in Bugzilla, if you were one of them, see https://www.mediawiki.org/wiki/Phabricator/Bugzilla_default_CCs Bugzilla default CCs were not imported as Members of the corresponding Phabricator project https://phabricator.wikimedia.org/T75699 On Tue, Nov 25, 2014 at 7:18 AM, Matthew Flaschen <mflaschen(a)wikimedia.org> wrote:

...

On 11/24/2014 02:41 AM, Quim Gil wrote:

-- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil

Kartik Mistry

6:21 a.m.

On Mon, Nov 24, 2014 at 1:11 PM, Quim Gil <qgil(a)wikimedia.org> wrote:

...

We did it. https://phabricator.wikimedia.org now contains all the Bugzilla reports. If you need to check the original Bugzilla, it can be found at https://old-bugzilla-wikimedia.org (never mind the certificate warning, it will go away today or so).

Thanks to all involved in migration!! -- Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_ {kartikm, 0x1f1f}.wordpress.com

3474

days inactive

3475

days old

wikitech-l@lists.wikimedia.org

Manage subscription

14 comments

11 participants

tags (0)

participants (11)

Alex Monk
Andre Klapper
Antoine Musso
Arthur Richards
Chad
Isarra Yos
James Forrester
Kartik Mistry
Matthew Flaschen
Quim Gil
S Page