Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-29 Thread Tom Stellard via lldb-dev
Hi, Thanks to everyone who provided feedback. I would like to propose a more detailed plan based on the everyone's comments. It seems like there was a strong preference to maintain the bug ID numbers, so this proposal tries to address that. TLDR; This proposes to maintain bug ID numbers by ov

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-24 Thread Tom Stellard via lldb-dev
On 04/24/2020 03:24 AM, Sam McCall wrote: > clangd's experience using github issues to track bugs (in a separate repo) > has been very positive, and I'm glad you're pushing on this! > > Part of this has been that our issue tracker has been scoped to our > subproject only, which is a scope that t

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-21 Thread Philip Reames via lldb-dev
+1 to James's take I'd prefer simplicity of implementation over perfection here. Philip On 4/20/20 4:08 PM, James Y Knight via llvm-dev wrote: In a previous discussion, one other suggestion had been to migrate all the bugzilla bugs to a separate initially-private "bug archive" repository in g

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-21 Thread David Blaikie via lldb-dev
All things being equal, I'd prefer Richard Smith's proposal that doesn't involve needing a new/old numbering scheme, but lets us keep a single numbering/redirection (& I doubt we need the first 200 bugs in any case - has anyone referred to bugs that early in the last 5 years, say? But wouldn't mind

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-21 Thread Anton Korobeynikov via lldb-dev
Hi James, > Please could we replace the "llvm-tools" with a single label for each LLVM > tool (i.e. labels for llvm-ar, llvm-as, llvm-cxxfilt, llvm-objdump etc etc). Sorry, I missed the subcomponents for the tools when I did the migration of the labels. Will add them! -- With best regards, Anto

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-21 Thread James Henderson via lldb-dev
Please could we replace the "llvm-tools" with a single label for each LLVM tool (i.e. labels for llvm-ar, llvm-as, llvm-cxxfilt, llvm-objdump etc etc). As mentioned on multiple occasions now, this is much more user-friendly both for people filing issues, and for those like myself who are only inter

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-21 Thread Anton Korobeynikov via lldb-dev
> On 04/20/2020 04:08 PM, James Y Knight wrote: > > In a previous discussion, one other suggestion had been to migrate all the > > bugzilla bugs to a separate initially-private "bug archive" repository in > > github. This has a few benefits: > > 1. If the migration is messed up, the repo can be d

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread Tom Stellard via lldb-dev
On 04/20/2020 04:08 PM, James Y Knight wrote: > In a previous discussion, one other suggestion had been to migrate all the > bugzilla bugs to a separate initially-private "bug archive" repository in > github. This has a few benefits: > 1. If the migration is messed up, the repo can be deleted, an

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread Tom Stellard via lldb-dev
On 04/20/2020 09:15 PM, Mehdi AMINI wrote: > Hi, > > How is the user workflow to file bugs? Do we have some sort of template? Do > they have to pick a label? > We don't have any templates defined yet, we need someone to volunteer to do this. Users would not be required to pick a label, they wo

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread James Y Knight via lldb-dev
In a previous discussion, one other suggestion had been to migrate all the bugzilla bugs to a separate initially-private "bug archive" repository in github. This has a few benefits: 1. If the migration is messed up, the repo can be deleted, and the process run again, until we get a result we like.

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread Anton Korobeynikov via lldb-dev
Just to clarify a bit: what I wanted to say is that it's unlikely that we will be able to ensure that bugzilla issue numbers after migration would coincide with github issue numbers. And therefore proper mapping will be necessary. And this mapping would be more complex than just rewriting the URL.

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread Anton Korobeynikov via lldb-dev
> Can we preserve the existing bug numbers if we migrate this way? There are > lots of references to "PRx" in checked in LLVM artifacts and elsewhere in > the world, as well as links to llvm.org/PRx, and if we can preserve all > the issue numbers this would ease the transition pain subst

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread Tom Stellard via lldb-dev
On 04/20/2020 12:49 PM, Richard Smith wrote: > On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev > mailto:llvm-...@lists.llvm.org>> wrote: > > Hi, > > I wanted to continue discussing the plan to migrate from Bugzilla to > Github. > It was suggested that I start a new thread an

Re: [lldb-dev] [llvm-dev] RFC: Switching from Bugzilla to Github Issues [UPDATED]

2020-04-20 Thread Richard Smith via lldb-dev
On Mon, 20 Apr 2020 at 12:31, Tom Stellard via llvm-dev < llvm-...@lists.llvm.org> wrote: > Hi, > > I wanted to continue discussing the plan to migrate from Bugzilla to > Github. > It was suggested that I start a new thread and give a summary of the > proposal > and what has changed since it was o