[flang-dev] [llvm-dev] IMPORTANT: LLVM Bugzilla migration

[James Henderson via flang-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/flang-dev/attachments/20211122/21c3ff40/attachment.html>