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

2020-04-30 Thread Tom Stellard via lldb-dev
On 04/29/2020 01:19 PM, David Blaikie wrote: > Generally sounds pretty good to me - only variation on the theme (& certainly > imho dealer's choice at this point - if you/whoever ends up doing this > doesn't like the sound of it, they shouldn't feel they have to do it this > way) - maybe creatin

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

2020-04-29 Thread David Blaikie via lldb-dev
Generally sounds pretty good to me - only variation on the theme (& certainly imho dealer's choice at this point - if you/whoever ends up doing this doesn't like the sound of it, they shouldn't feel they have to do it this way) - maybe creating blank issues up to the current bugzilla PR number (& m

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

2020-04-27 Thread Philip Reames via lldb-dev
On 4/25/20 10:02 PM, Mehdi AMINI via cfe-dev wrote: On Fri, Apr 24, 2020 at 12:04 PM Tom Stellard via llvm-dev mailto:llvm-...@lists.llvm.org>> wrote: 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

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

2020-04-24 Thread Richard Smith via lldb-dev
On Fri, 24 Apr 2020 at 14:13, Sam McCall via cfe-dev wrote: > On Fri, Apr 24, 2020 at 9:03 PM Tom Stellard wrote: > >> 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

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

2020-04-22 Thread Philip Reames via lldb-dev
On 4/22/20 2:35 PM, Richard Smith wrote: On Wed, 22 Apr 2020 at 09:45, Philip Reames via cfe-dev mailto:cfe-...@lists.llvm.org>> wrote: On 4/21/20 6:50 PM, Richard Smith wrote: On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev mailto:llvm-...@lists.llvm.org>> wrote:

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

2020-04-22 Thread Richard Smith via lldb-dev
On Wed, 22 Apr 2020 at 09:45, Philip Reames via cfe-dev < cfe-...@lists.llvm.org> wrote: > On 4/21/20 6:50 PM, Richard Smith wrote: > > On Tue, 21 Apr 2020 at 17:00, Tom Stellard via llvm-dev < > llvm-...@lists.llvm.org> wrote: > >> On 04/21/2020 03:36 PM, Richard Smith via llvm-dev wrote: >> > On

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

2020-04-22 Thread James Henderson via lldb-dev
Github may do things in a canonical way, but I think you'll find that lots of people will refer to them by other means in review comments, email threads, etc. Let's avoid any risk of ambiguity... Also, there's no guarantee in the future that Github won't decide to start auto-linking PR1234 as well

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

2020-04-22 Thread James Y Knight via lldb-dev
GitHub canonically uses "#NNN" to refer to its bugs or pull requests, and also supports "GH-NNN". We'll want to switch to one of those schemes, so that automatic linking works properly. So, in that case, PR1234 == legacy issue, #1234 or GH-1234 == new issue. (See https://help.github.com/en/github/

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

2020-04-22 Thread Anton Korobeynikov via lldb-dev
Hi Konrad, Thanks for the scripts – look useful! For the record, here is the result of previous experiments https://github.com/asl/llvm-bugzilla/issues On Wed, Apr 22, 2020 at 2:21 PM Konrad Kleine via cfe-dev wrote: > > I wanted to try importing llvm bugs into a fresh github repo and here's my

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

2020-04-22 Thread Konrad Kleine via lldb-dev
I wanted to try importing llvm bugs into a fresh github repo and here's my result so far (import is still running): https://github.com/kwk/test-llvm-bz-import-4 . I've written the scripts ( https://github.com/kwk/bz2gh) myself because I wanted to remain in control and don't make my life more compli

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

2020-04-22 Thread Dimitry Andric via lldb-dev
Since Bugzilla numbers are all under 50,000 (at least for now:), can't we simply bump the GitHub issue/pull request numbers to 50,000, and start from there? Then it would be easy to identify: < 5 means Bugzilla, >= 5 means GitHub. Now somebody's only gotta find a way to file 5-200

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

2020-04-22 Thread James Henderson via lldb-dev
Similar to other people's experiences, I've worked on a common code base that supported three different platforms, and each platform used a different bugzilla with it's own numbering scheme. I regularly came across references to "BZ123456" with no indication as to which of the three systems that re

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

2020-04-21 Thread Philip Reames via lldb-dev
On 4/21/20 3:36 PM, Richard Smith wrote: On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev mailto:cfe-...@lists.llvm.org>> wrote: +1 to James's take I'd prefer simplicity of implementation over perfection here. If we end up with two different bug numbering systems, that's a pr

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

2020-04-21 Thread Richard Smith via lldb-dev
On Tue, 21 Apr 2020 at 11:04, Philip Reames via cfe-dev < cfe-...@lists.llvm.org> wrote: > +1 to James's take > > I'd prefer simplicity of implementation over perfection here. > If we end up with two different bug numbering systems, that's a problem that we will be paying for for many years. It's

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

2020-04-20 Thread Fangrui Song via lldb-dev
On 2020-04-20, Richard Smith via cfe-dev wrote: On Mon, 20 Apr 2020 at 13:57, Anton Korobeynikov via cfe-dev < cfe-...@lists.llvm.org> wrote: > If we are reasonably certain that no one would be opening new issues on GitHub while the migration is running... And pull requests (the numbering is co

Re: [lldb-dev] [cfe-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 13:57, Anton Korobeynikov via cfe-dev < cfe-...@lists.llvm.org> wrote: > > If we are reasonably certain that no one would be opening new issues on > GitHub while the migration is running... > And pull requests (the numbering is common for issues and pull > requests) as well.

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

2020-04-20 Thread Anton Korobeynikov via lldb-dev
> If we are reasonably certain that no one would be opening new issues on > GitHub while the migration is running... And pull requests (the numbering is common for issues and pull requests) as well. And we cannot disable pull requests at all. And I'm afraid the issues will need to be opened as wel

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

2020-04-20 Thread Richard Smith via lldb-dev
210 issues have been filed on github so far. That's negligible compared to the total number we have, so a minor additional effort for those seems acceptable if we can't actually clean them out and reuse the numbers. So suppose we start with bugzilla issue #211 and migrate the issues to github one

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

2020-03-25 Thread Tom Stellard via lldb-dev
On 03/16/2020 07:53 AM, Aaron Ballman wrote: > On Mon, Mar 16, 2020 at 10:44 AM Tom Stellard via cfe-dev > wrote: >> >> On 02/10/2020 07:40 PM, Tom Stellard wrote: >>> On 01/30/2020 12:47 PM, David Major wrote: Would it make sense to wait until 10.0.0 is released, in order to keep all t

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

2020-03-25 Thread Tom Stellard via lldb-dev
On 03/16/2020 10:18 AM, Roman Lebedev wrote: > On Mon, Mar 16, 2020 at 8:13 PM Florian Hahn via cfe-dev > wrote: >> >> Hi, >> >> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev >> wrote: >> >> I've also implemented a notification system using GitHub actions that will >> make >> it possible

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

2020-03-17 Thread Tom Stellard via lldb-dev
On 03/17/2020 06:39 AM, Roman Lebedev wrote: > On Tue, Mar 17, 2020 at 4:35 PM Tom Stellard wrote: >> >> On 03/16/2020 11:09 PM, Roman Lebedev wrote: >>> On Tue, Mar 17, 2020 at 6:07 AM Tom Stellard via cfe-dev >>> wrote: On 03/16/2020 10:13 AM, Florian Hahn wrote: > Hi, > >

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

2020-03-17 Thread Tom Stellard via lldb-dev
On 03/16/2020 11:09 PM, Roman Lebedev wrote: > On Tue, Mar 17, 2020 at 6:07 AM Tom Stellard via cfe-dev > wrote: >> >> On 03/16/2020 10:13 AM, Florian Hahn wrote: >>> Hi, >>> On Mar 16, 2020, at 14:43, Tom Stellard via llvm-dev mailto:llvm-...@lists.llvm.org>> wrote: I've also

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

2020-03-17 Thread James Henderson via lldb-dev
Quite possibly. I am one of the current self-volunteered triagers on each of the GNU-equivalent LLVM binutils, and somebody who is therefore on the CC list for several bugzilla components with small numbers. I don't have the expertise to triage 95% of issues that come in elsewhere so me being in so

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

2020-03-16 Thread James Y Knight via lldb-dev
I think we ought to setup some sort of organized scheme for volunteers to do triage of incoming issues, to make sure they've got enough actionable info, and direct to the correct people as needed. (This would actually be a really nice thing to have, regardless of which bugtracking system we have.)

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

2020-03-16 Thread James Henderson via lldb-dev
On Mon, 16 Mar 2020 at 15:08, Tom Stellard wrote: > On 03/16/2020 08:00 AM, James Henderson wrote: > > > > > > On Mon, 16 Mar 2020 at 14:44, Tom Stellard via cfe-dev < > cfe-...@lists.llvm.org > wrote: > > > > On 02/10/2020 07:40 PM, Tom Stellard wrote: > >

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

2020-03-16 Thread Tom Stellard via lldb-dev
On 03/16/2020 08:00 AM, James Henderson wrote: > > > On Mon, 16 Mar 2020 at 14:44, Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On 02/10/2020 07:40 PM, Tom Stellard wrote: > > On 01/30/2020 12:47 PM, David Major wrote: > >> Would it make sense to wait until

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

2020-03-16 Thread James Henderson via lldb-dev
On Mon, 16 Mar 2020 at 14:44, Tom Stellard via cfe-dev < cfe-...@lists.llvm.org> wrote: > On 02/10/2020 07:40 PM, Tom Stellard wrote: > > On 01/30/2020 12:47 PM, David Major wrote: > >> Would it make sense to wait until 10.0.0 is released, in order to keep > all the blockers in one place? > >> > >

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

2020-03-16 Thread Aaron Ballman via lldb-dev
On Mon, Mar 16, 2020 at 10:44 AM Tom Stellard via cfe-dev wrote: > > On 02/10/2020 07:40 PM, Tom Stellard wrote: > > On 01/30/2020 12:47 PM, David Major wrote: > >> Would it make sense to wait until 10.0.0 is released, in order to keep all > >> the blockers in one place? > >> > > > > Yes, I think

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

2020-02-03 Thread Jacob Lifshay via lldb-dev
On Mon, Feb 3, 2020, 09:00 Michael Kruse wrote: > Am Do., 30. Jan. 2020 um 13:29 Uhr schrieb Jacob Lifshay via cfe-dev > : > > > > On Thu, Jan 30, 2020, 10:22 Tom Stellard via llvm-dev < > llvm-...@lists.llvm.org> wrote: > >> > >> Hi, > >> > >> I want to restart this discussion. There seemed to

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

2020-01-31 Thread Fangrui Song via lldb-dev
On 2020-01-30, Anton Korobeynikov via cfe-dev wrote: Will you be able to start numbering in github at a number larger than the largest bug in bugzilla? It would be annoying to have overlapping bug numbers. Bug numbers exist in code comments, list archives, etc., etc. If someone reads 'clang

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

2020-01-30 Thread Tom Stellard via lldb-dev
On 01/30/2020 10:48 AM, Mehdi AMINI wrote: > Hi, > > > > > On Thu, Jan 30, 2020 at 10:21 AM Tom Stellard via cfe-dev > mailto:cfe-...@lists.llvm.org>> wrote: > > On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > > We held a round-table at the llvm dev conference about what

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

2020-01-30 Thread Aaron Ballman via lldb-dev
My concern about switching is that I will now need to use two issue trackers instead of one when doing things like searching for related bugs. ~Aaron On Thu, Jan 30, 2020, 1:31 PM Tom Stellard wrote: > On 01/30/2020 10:24 AM, Aaron Ballman wrote: > > On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard

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

2020-01-30 Thread Tom Stellard via lldb-dev
On 01/30/2020 10:24 AM, Aaron Ballman wrote: > On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev > wrote: >> >> On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: >>> We held a round-table at the llvm dev conference about what other pieces of >>> Github infrastructure we may want t

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

2020-01-30 Thread Aaron Ballman via lldb-dev
On Thu, Jan 30, 2020 at 1:21 PM Tom Stellard via cfe-dev wrote: > > On 10/24/2019 07:54 PM, James Y Knight via llvm-dev wrote: > > We held a round-table at the llvm dev conference about what other pieces of > > Github infrastructure we may want to use. This thread in particular is > > about swit