Description

Send now an email to all Bugzilla users in the lines of "ACTION REQUIRED: JOIN PHABRICATOR", explaining that this is how you will have your Bugzilla history migrated to Phabricator on the launch date.

Send a second and last email to all Bugzilla users as we have a date confirmed, telling them the details about dates when the service will be down and a reminder about JOIN PHABRICATOR NOW, IT TAKES ONE MINUTE.

After agreeing on the idea (T572), Quim can draft the emails and get them reviewed. Then @Aklapper could send them on the dates agreed.

First email DRAFT, FEEDBACK AND EDITS WELCOME

Join Wikimedia Phabricator for a smooth Bugzilla migration **

Dear Wikimedia Bugzilla user,

https://phabricator.wikimedia.org will replace Bugzilla soon. We have released a preview with a sample of several thousands of Bugzilla reports automatically migrated. Your feedback is welcome.

If you have not created an account in Wikimedia Phabricator yet, please follow these steps now:

Create your Phabricator account at https://phabricator.wikimedia.org/auth/start/ by clicking the "Login or Register - MediaWiki" button below the LDAP registration form. A dialog will be displayed saying "phabricator-production would like to have basic access on your behalf on all projects of this site." After clicking "Allow" you will see a "Phabricator Registration" dialog asking you to define a username in Phabricator, an email address, and a name (which does not have to be your real name). Afterwards, add the email address(es) that you have used in Bugzilla in https://phabricator.wikimedia.org/settings/panel/email/

That's it! Your Bugzilla activity will be connected to your Phabricator username as soon as the migration from Bugzilla is completed.

If you register an account after the Wikimedia Phabricator launch, you will still be able to claim your Bugzilla activity. However it will take us longer to connect your new username with your migrated data.

We plan to archive Bugzilla and migrate its data to https://phabricator.wikimedia.org starting on Friday, 21 November at 00:30 UTC. If you haven't created your Wikimedia Phabricator account with the email address(es) you have used in Bugzilla, we recommend you to do it now.

Provide a date when adding new bugs to Phabricator is ok (starting now?)

Depends on the project... Task creation in Phabricator has been available for a while but projects which are hosted in Bugzilla are in Bugzilla until Bugzilla is open. Only one bugtracker for a project.

Provide a date when Bugzilla will stop accepting new bugs

Provide a date when Bugzilla will stop accepting changes to existing bugs

Chase proposed to send this email out once T552 (testing instance with imported data) is up which should take another 2-4 working days.
Then we could also include a link to that test instance to allow people to take a look at it and provide feedback (where?).

If you want to receive notifications about bugs you voted, you will need to subscribe to them manually after the migration. You can find the tickets that you have voted on

Better, thanks, but still useless. How do I find the bugs I voted which I wasn't cc'd to? We're certainly not telling users to manually open them one by one, are we? (Personally I'll do some regex cleanup of the votes list, enter the list of IDs in advanced search, filter by bugs I'm not cc'd on. But most users are not able to do any of these.)

Speaking of which, is there an interface for bulk bug changes on phabricator?

Better, thanks, but still useless. How do I find the bugs I voted which I wasn't cc'd to? We're certainly not telling users to manually open them one by one, are we? (Personally I'll do some regex cleanup of the votes list, enter the list of IDs in advanced search, filter by bugs I'm not cc'd on. But most users are not able to do any of these.)

Go to the "My votes" page and click on "view all as bug list" on the bottom to get a comma-separated list of bug ids.

If you need to filter out bugs you are CCd on, you can edit the bugzilla search, but then it's more complicated to extract the results (probably need to export to CSV and do some text processing). But if you just want to CC to all the bugs you have voted for, that's not needed.

No way that I am aware of, plus I don't see an obvious reason why you'd suddenly want to receive mail notifications for a ticket that you had voted on. Wasn't the whole argumentation of (ab)using Bugzilla's voting as some kind of "watchlist" that you didn't want to receive mail notifications? Also see T264.

We're certainly not telling users to manually open them one by one, are we?

I'm telling users that their Bugzilla votes won't be migrated to Phabricator. I don't tell anybody to open anything. :)

Either I'm blind or the second notification is nowhere to be seen in my mailbox (yes, spam folder included). Hopefully it is just me... @Aklapper, do you have a way to check how many recipients did you use this time, and whether you got more bounces/errors than last time?

I mean, if it's just me and a few others, this is not problematic. But if half the users haven't received it... at least we should know.

@Qgil: Number of bounces was slightly larger this time than first time. Recipients list was same as last time (I see your address in BCC of the 4th email I sent around 02:13UTC; each email=50 recipients).

So my subscriptions will be migrated together with bugzilla data. Phabricator doesn't offer any easy to use feature for such a job, AFAICS.

IMHO worth sending a separate email with subject "Migrate your Wikimedia bugzilla votes now" to all the users who ever voted a bug. Ideally we'd also provide the link from step (2) (or even an HTML save of it) but that would require some work.

But the email only linked another section and for unrelated purposes ("Find all the details about the differences"), so I didn't reach said instructions. Moreover, due to T624 it's much better to perform batch changes on bugzilla, which is less spammy.

So if we sent such a message, the included instructions wouldn't work for approx. half of the recipients.

We could just give editbugs to everyone in old-bugzilla.

enter the comma-separated list into the bugzilla id field (which doesn't seem to exist yet)

And still doesn't exist, or not as you imagined it. So the only option is to take the bugzilla ID, put them in a spreadsheet, add 2000 on each row, take the new list of IDs, put into "task IDs" field. Heh, imagine if T857 had not been partially fixed! Can still be improved by fixing T857 completely though (or by giving us a really-advanced and really-userfriendly search like bugzilla's).