[flang-dev] [F18] Bugzilla for Flang post-LLVM merge

[David Truby via flang-dev]

Hi Nichols,

We aren't going to attempt to migrate all those issues as there's no way to automate that.
Our intention is to try and resolve the issues that are on github as well as on bugzilla, but new reports should be opened on bugzilla only.

If you have an issue on there and want to raise the visibility of it, you could open it on bugzilla and close the github one and it should make it more visible at the moment. However I do think we want to fix the github issues too.

Thanks
David Truby
________________________________
From: Romero, Nichols A. <naromero at anl.gov>
Sent: 21 April 2020 20:22
To: David Truby <David.Truby at arm.com>; via flang-dev <flang-dev at lists.llvm.org>
Subject: Re: [flang-dev] [F18] Bugzilla for Flang post-LLVM merge


David,



Just to double-check and make sure we are all on the same page



We are NOT migrating these github issues:

https://github.com/flang-compiler/f18/issues



over to Bugzilla? Only issues arising post LLVM merge, will go into Bugzilla.





From: flang-dev <flang-dev-bounces at lists.llvm.org> on behalf of David Truby via flang-dev <flang-dev at lists.llvm.org>
Reply-To: David Truby <David.Truby at arm.com>
Date: Tuesday, April 7, 2020 at 5:36 AM
To: via flang-dev <flang-dev at lists.llvm.org>
Subject: [flang-dev] [F18] Bugzilla for Flang post-LLVM merge



Hi all,



Since we're imminently moving to LLVM we should also move to use the same bug tracking infrastructure as they do.

The LLVM Bugzilla admin team have kindly set up a project for us in bugs.llvm.org; we have split the project at the moment into the components Frontend, FIR and Driver although this can be adjusted if anyone thinks there's a better separation.

Bugzilla will automatically CC people when new bugs are submitted; at the moment I have just asked for myself to be CC'd as I didn't want to volunteer anyone else's email addresses without their permission, if you wouldn't mind being CC'd on any of those components then please let me know and I will pass on your email address to add to the list.



The current proposal is to move over to the bug tracker that LLVM uses for new bugs, but to leave the currently open issues on the F18 github open so that we don't have to manually move everything over; I believe this is the same as the approach MLIR took.



Thanks!

David Truby
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/flang-dev/attachments/20200424/d4930833/attachment-0001.html>