llvm dev - Nov 2021 - IMPORTANT: LLVM Bugzilla migration

Dear Fellow LLVM'ers,

I'm happy to announce that we were able to find workarounds for the
vast majority of GitHub limitations and our dry import went
successfully.

Therefore, the following migration roadmap is proposed:

1. We will put Bugzilla in read-only mode on Wednesday, November 24
23:59 Pacific Time. This will be the last chance to submit the
bugzilla username => github username mapping.
2. We will download the data from Bugzilla and prepare the final
"migration dump" on Thursday, November 25.
3. We will perform the actual migration on November 26 - November 27
and verify the results
4. If everything will go smoothly, we will open the LLVM GitHub repo
for issues no later than on Monday, November 29. Bugzilla will remain
in read-only mode after the migration.

Please DO NOT submit any issues to LLVM github repo during the
migration as it might interfere with the migration process.

Please let me know if there are any objections to this schedule.

-- 
With best regards, Anton Korobeynikov
On behalf of the LLVM Foundation,

Hi Anton,
Perhaps I have missed it, but how do I submit the Bugzilla to GitHub
username mapping?
Warm regards,
Deep

On Sat, 20 Nov, 2021, 4:24 pm Anton Korobeynikov via llvm-dev, <
llvm-dev at lists.llvm.org> wrote:
> Dear Fellow LLVM'ers,
>
> I'm happy to announce that we were able to find workarounds for the
> vast majority of GitHub limitations and our dry import went
> successfully.
>
> Therefore, the following migration roadmap is proposed:
>
> 1. We will put Bugzilla in read-only mode on Wednesday, November 24
> 23:59 Pacific Time. This will be the last chance to submit the
> bugzilla username => github username mapping.
> 2. We will download the data from Bugzilla and prepare the final
> "migration dump" on Thursday, November 25.
> 3. We will perform the actual migration on November 26 - November 27
> and verify the results
> 4. If everything will go smoothly, we will open the LLVM GitHub repo
> for issues no later than on Monday, November 29. Bugzilla will remain
> in read-only mode after the migration.
>
> Please DO NOT submit any issues to LLVM github repo during the
> migration as it might interfere with the migration process.
>
> Please let me know if there are any objections to this schedule.
>
> --
> With best regards, Anton Korobeynikov
> On behalf of the LLVM Foundation,
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211120/b4105add/attachment.html>

awesome, really glad to hear! Thanks for all the hard work!

(I guess this was probably answered somewhere else/documented somewhere:
But will the llvm.org/PRXXXX links be redirected to the github issues at
some point as part of this migration?)

On Sat, Nov 20, 2021 at 2:54 AM Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear Fellow LLVM'ers,
>
> I'm happy to announce that we were able to find workarounds for the
> vast majority of GitHub limitations and our dry import went
> successfully.
>
> Therefore, the following migration roadmap is proposed:
>
> 1. We will put Bugzilla in read-only mode on Wednesday, November 24
> 23:59 Pacific Time. This will be the last chance to submit the
> bugzilla username => github username mapping.
> 2. We will download the data from Bugzilla and prepare the final
> "migration dump" on Thursday, November 25.
> 3. We will perform the actual migration on November 26 - November 27
> and verify the results
> 4. If everything will go smoothly, we will open the LLVM GitHub repo
> for issues no later than on Monday, November 29. Bugzilla will remain
> in read-only mode after the migration.
>
> Please DO NOT submit any issues to LLVM github repo during the
> migration as it might interfere with the migration process.
>
> Please let me know if there are any objections to this schedule.
>
> --
> With best regards, Anton Korobeynikov
> On behalf of the LLVM Foundation,
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211120/347d3028/attachment.html>

While I find important information here about migrating
away from Bugzilla in this thread, I kind of lack information
about what we are migrating to.

I've understood that we are migrating from Bugzilla to some
GitHub supported issue handling, but I have zero experience
with issue handling in GitHub.

Here are some of the questions that popped up:

- Where will I find the new tool for PRs?

- Can I find and look at the result of the dry import already
  today to familiarize and learn about it?

- And are there any guidelines specific for the LLVM project
  related to how to deal with PRs in GitHub?

- Will it be possible to setup emails notification similar
  to Bugzilla (e.g. make sure I'm automatically CC:ed on all
  issues that my co-workers are involved in)?

Regards,
Björn

> -----Original Message-----
> From: llvm-dev <llvm-dev-bounces at lists.llvm.org> On Behalf Of
Anton
> Korobeynikov via llvm-dev
> Sent: den 20 november 2021 11:54
> To: llvm-dev <llvm-dev at lists.llvm.org>; clang developer list
<cfe-
> dev at lists.llvm.org>; Flang Development List <flang-dev at
lists.llvm.org>;
> openmp-dev (openmp-dev at lists.llvm.org) <openmp-dev at
lists.llvm.org>; polly-
> dev at googlegroups.com
> Subject: [llvm-dev] IMPORTANT: LLVM Bugzilla migration
> 
> Dear Fellow LLVM'ers,
> 
> I'm happy to announce that we were able to find workarounds for the
> vast majority of GitHub limitations and our dry import went
> successfully.
> 
> Therefore, the following migration roadmap is proposed:
> 
> 1. We will put Bugzilla in read-only mode on Wednesday, November 24
> 23:59 Pacific Time. This will be the last chance to submit the
> bugzilla username => github username mapping.
> 2. We will download the data from Bugzilla and prepare the final
> "migration dump" on Thursday, November 25.
> 3. We will perform the actual migration on November 26 - November 27
> and verify the results
> 4. If everything will go smoothly, we will open the LLVM GitHub repo
> for issues no later than on Monday, November 29. Bugzilla will remain
> in read-only mode after the migration.
> 
> Please DO NOT submit any issues to LLVM github repo during the
> migration as it might interfere with the migration process.
> 
> Please let me know if there are any objections to this schedule.
> 
> --
> With best regards, Anton Korobeynikov
> On behalf of the LLVM Foundation,
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

All sounds great to me! I wouldn't be surprised if we need to add some
documentation on how to use Github Issues specifically related to LLVM
(e.g. what labels to apply etc), although I can't really say what that
content may be. I believe our bugzilla documentation is virtually
non-existent (I apologise if I'm wrong), so this isn't a blocker though.

James

On Sat, 20 Nov 2021 at 10:54, Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear Fellow LLVM'ers,
>
> I'm happy to announce that we were able to find workarounds for the
> vast majority of GitHub limitations and our dry import went
> successfully.
>
> Therefore, the following migration roadmap is proposed:
>
> 1. We will put Bugzilla in read-only mode on Wednesday, November 24
> 23:59 Pacific Time. This will be the last chance to submit the
> bugzilla username => github username mapping.
> 2. We will download the data from Bugzilla and prepare the final
> "migration dump" on Thursday, November 25.
> 3. We will perform the actual migration on November 26 - November 27
> and verify the results
> 4. If everything will go smoothly, we will open the LLVM GitHub repo
> for issues no later than on Monday, November 29. Bugzilla will remain
> in read-only mode after the migration.
>
> Please DO NOT submit any issues to LLVM github repo during the
> migration as it might interfere with the migration process.
>
> Please let me know if there are any objections to this schedule.
>
> --
> With best regards, Anton Korobeynikov
> On behalf of the LLVM Foundation,
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211122/21c3ff40/attachment.html>

Looking at the PDF you posted on the other thread, it appears that users
who did not fill out the migration google-sheet have their comments
migrated with no author-attribution of any kind (not name, not username, or
even "Anonymous LLVM Contributor #123". Is that correct?

Thus, it seems pretty important that at least all of the active
contributors have filled out the sheet before the migration -- have they?
What % of contributors will be converted with comment attribution? (or
maybe better: what percent of comments are by someone who filled out the
migration sheet vs anonymous?)

I imagine it'd be pretty easy for folks to forget that they didn't fill
out
the sheet, since there's no way to verify whether you did or not.



On Sat, Nov 20, 2021 at 5:54 AM Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear Fellow LLVM'ers,
>
> I'm happy to announce that we were able to find workarounds for the
> vast majority of GitHub limitations and our dry import went
> successfully.
>
> Therefore, the following migration roadmap is proposed:
>
> 1. We will put Bugzilla in read-only mode on Wednesday, November 24
> 23:59 Pacific Time. This will be the last chance to submit the
> bugzilla username => github username mapping.
> 2. We will download the data from Bugzilla and prepare the final
> "migration dump" on Thursday, November 25.
> 3. We will perform the actual migration on November 26 - November 27
> and verify the results
> 4. If everything will go smoothly, we will open the LLVM GitHub repo
> for issues no later than on Monday, November 29. Bugzilla will remain
> in read-only mode after the migration.
>
> Please DO NOT submit any issues to LLVM github repo during the
> migration as it might interfere with the migration process.
>
> Please let me know if there are any objections to this schedule.
>
> --
> With best regards, Anton Korobeynikov
> On behalf of the LLVM Foundation,
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211122/af084b77/attachment.html>

On Sat, 20 Nov 2021 at 10:54, Anton Korobeynikov via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Please DO NOT submit any issues to LLVM github repo during the
> migration as it might interfere with the migration process.

We occasionally have issues created by people that don't read this list, so
it'd be better if we could have a way to disable new issues from GH's
own
settings.

I haven't found a way on my own repos, but perhaps the migration process
can do that as part of the setup / teardown.

--renato
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20211122/8a955d39/attachment.html>