[llvm-dev] [cfe-dev] RFC: Switching from Bugzilla to Github Issues
James Y Knight via llvm-dev
llvm-dev at lists.llvm.org
Mon Mar 16 09:27:02 PDT 2020
Yes, this is one option that has been discussed previously.
We can import bugs from bugzilla into a separate (initially empty)
"imported bugs" repository, and then allow people to move bugs that are
still active over to the LLVM repository (or maybe setup some automation to
do that automatically as needed).
Note that when you move a bug between repositories in github, it
automatically sets up a redirect from the old repository/bug# to the new
On Mon, Mar 16, 2020 at 11:39 AM Hubert Tong via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Mon, Mar 16, 2020 at 11:30 AM David Chisnall via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>> On 16/03/2020 15:08, Tom Stellard via llvm-dev wrote:
>> > This was a mistake on my part. The plan is to disable creation of new
>> bugs in bugzilla and not
>> > to make it read-only. If you look at the original RFC, it says GitHub
>> > would be used for new issues, and existing issues will continue to be
>> updated in bugzilla,
>> > and this is what I'm proposing.
>> Does this mean that we're giving up on aligning Bugzilla PRs with GitHub
>> issue numbers? This won't be possible once people have created issues /
>> PRs on GitHub. It looks as if we have a hundred or so PRs / issues
>> already, so maybe it's too late to think about this...
> It is possible to set up a common "repository" for issues that is not tied
> to the specific code repositories (llvm-project, llvm-lnt, etc.).
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-dev