Re: Migrating to the gitlab issue tracker

2021-01-21 Thread John Snow
On 1/21/21 5:57 AM, Thomas Huth wrote: On 05/11/2020 01.06, John Snow wrote: On 10/30/20 6:57 AM, Peter Maydell wrote: On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: This makes it more appealing to leave existing bugs in the LP tracker until they are resolved, auto-closed, or there i

Re: Migrating to the gitlab issue tracker

2021-01-21 Thread Thomas Huth
On 05/11/2020 01.06, John Snow wrote: On 10/30/20 6:57 AM, Peter Maydell wrote: On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: This makes it more appealing to leave existing bugs in the LP tracker until they are resolved, auto-closed, or there is a compelling reason to move to gitlab.

Re: Migrating to the gitlab issue tracker

2020-11-09 Thread Peter Maydell
On Mon, 9 Nov 2020 at 10:11, Daniel P. Berrangé wrote: > > On Sun, Nov 08, 2020 at 11:58:28AM +, Peter Maydell wrote: > > On Sun, 8 Nov 2020 at 09:01, Thomas Huth wrote: > > > I agree with Daniel. Please let's not clog the new bug tracker right from > > > the start with hundreds of bugs - tha

Re: Migrating to the gitlab issue tracker

2020-11-09 Thread Daniel P . Berrangé
On Sun, Nov 08, 2020 at 11:58:28AM +, Peter Maydell wrote: > On Sun, 8 Nov 2020 at 09:01, Thomas Huth wrote: > > I agree with Daniel. Please let's not clog the new bug tracker right from > > the start with hundreds of bugs - that only makes it harder to focus on the > > tickets that are really

Re: Migrating to the gitlab issue tracker

2020-11-09 Thread Thomas Huth
On 08/11/2020 12.58, Peter Maydell wrote: > On Sun, 8 Nov 2020 at 09:01, Thomas Huth wrote: >> I agree with Daniel. Please let's not clog the new bug tracker right from >> the start with hundreds of bugs - that only makes it harder to focus on the >> tickets that are really important. Let's use th

Re: Migrating to the gitlab issue tracker

2020-11-08 Thread Peter Maydell
On Sun, 8 Nov 2020 at 09:01, Thomas Huth wrote: > I agree with Daniel. Please let's not clog the new bug tracker right from > the start with hundreds of bugs - that only makes it harder to focus on the > tickets that are really important. Let's use the migration instead to start > as clean as poss

Re: Migrating to the gitlab issue tracker

2020-11-08 Thread Thomas Huth
On 05/11/2020 16.50, Daniel P. Berrangé wrote: > On Thu, Nov 05, 2020 at 10:44:42AM -0500, John Snow wrote: >> On 11/5/20 1:14 AM, Thomas Huth wrote: >>> On 05/11/2020 01.06, John Snow wrote: On 10/30/20 6:57 AM, Peter Maydell wrote: > On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé >>>

Re: Migrating to the gitlab issue tracker

2020-11-08 Thread Thomas Huth
On 30/10/2020 13.53, John Snow wrote: > On 10/30/20 6:26 AM, Alex Bennée wrote: >> Can we extract data as a CSV from Launchpad? > > Not sure, I don't have maintainer access there. Thomas? I've never seen such an option. But (as you've already discovered) there is an API for Launchpad which can be

Re: Migrating to the gitlab issue tracker

2020-11-06 Thread Laszlo Ersek
On 11/04/20 18:19, Daniel P. Berrangé wrote: > This just sounds like fairly niche requirements for which directly > subscribing to the project issue tracker will satisfy 99% of the time. OK. Laszlo

Re: Migrating to the gitlab issue tracker

2020-11-05 Thread Daniel P . Berrangé
On Thu, Nov 05, 2020 at 10:44:42AM -0500, John Snow wrote: > On 11/5/20 1:14 AM, Thomas Huth wrote: > > On 05/11/2020 01.06, John Snow wrote: > > > On 10/30/20 6:57 AM, Peter Maydell wrote: > > > > On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé > > > > wrote: > > > > > This > > > > > makes it m

Re: Migrating to the gitlab issue tracker

2020-11-05 Thread John Snow
On 11/5/20 1:14 AM, Thomas Huth wrote: On 05/11/2020 01.06, John Snow wrote: On 10/30/20 6:57 AM, Peter Maydell wrote: On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: This makes it more appealing to leave existing bugs in the LP tracker until they are resolved, auto-closed, or there i

Re: Migrating to the gitlab issue tracker

2020-11-05 Thread Daniel P . Berrangé
On Thu, Nov 05, 2020 at 07:14:47AM +0100, Thomas Huth wrote: > On 05/11/2020 01.06, John Snow wrote: > > On 10/30/20 6:57 AM, Peter Maydell wrote: > >> On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé > >> wrote: > >>> This > >>> makes it more appealing to leave existing bugs in the LP tracker un

Re: Migrating to the gitlab issue tracker

2020-11-04 Thread Thomas Huth
On 05/11/2020 01.06, John Snow wrote: > On 10/30/20 6:57 AM, Peter Maydell wrote: >> On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: >>> This >>> makes it more appealing to leave existing bugs in the LP tracker until >>> they are resolved, auto-closed, or there is a compelling reason to mo

Re: Migrating to the gitlab issue tracker

2020-11-04 Thread John Snow
On 10/30/20 6:57 AM, Peter Maydell wrote: On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: This makes it more appealing to leave existing bugs in the LP tracker until they are resolved, auto-closed, or there is a compelling reason to move to gitlab. The compelling reason is that there

Re: Migrating to the gitlab issue tracker

2020-11-04 Thread Daniel P . Berrangé
On Wed, Nov 04, 2020 at 06:03:26PM +0100, Laszlo Ersek wrote: > On 11/02/20 15:26, Daniel P. Berrangé wrote: > > On Mon, Nov 02, 2020 at 02:57:49PM +0100, Laszlo Ersek wrote: > >> On 10/30/20 10:16, Stefan Hajnoczi wrote: > >>> On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: > In ex

Re: Migrating to the gitlab issue tracker

2020-11-04 Thread Laszlo Ersek
On 11/02/20 15:42, Eric Blake wrote: > On 11/2/20 8:26 AM, Daniel P. Berrangé wrote: >> On Mon, Nov 02, 2020 at 02:57:49PM +0100, Laszlo Ersek wrote: >>> On 10/30/20 10:16, Stefan Hajnoczi wrote: On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: > In experimenting with my mirror o

Re: Migrating to the gitlab issue tracker

2020-11-04 Thread Laszlo Ersek
On 11/02/20 15:26, Daniel P. Berrangé wrote: > On Mon, Nov 02, 2020 at 02:57:49PM +0100, Laszlo Ersek wrote: >> On 10/30/20 10:16, Stefan Hajnoczi wrote: >>> On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: In experimenting with my mirror on gitlab though, I was unable to find a >>>

Re: Migrating to the gitlab issue tracker

2020-11-02 Thread Eric Blake
On 11/2/20 8:26 AM, Daniel P. Berrangé wrote: > On Mon, Nov 02, 2020 at 02:57:49PM +0100, Laszlo Ersek wrote: >> On 10/30/20 10:16, Stefan Hajnoczi wrote: >>> On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: In experimenting with my mirror on gitlab though, I was unable to find a >>

Re: Migrating to the gitlab issue tracker

2020-11-02 Thread Daniel P . Berrangé
On Mon, Nov 02, 2020 at 02:57:49PM +0100, Laszlo Ersek wrote: > On 10/30/20 10:16, Stefan Hajnoczi wrote: > > On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: > >> In experimenting with my mirror on gitlab though, I was unable to find a > >> way > >> to configure it to send issue tracker

Re: Migrating to the gitlab issue tracker

2020-11-02 Thread Laszlo Ersek
On 10/30/20 10:16, Stefan Hajnoczi wrote: > On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: >> In experimenting with my mirror on gitlab though, I was unable to find a way >> to configure it to send issue tracker notifications to the email list. A >> move to gitlab would likely mean, the

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread John Snow
On 10/30/20 5:16 AM, Stefan Hajnoczi wrote: On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: In experimenting with my mirror on gitlab though, I was unable to find a way to configure it to send issue tracker notifications to the email list. A move to gitlab would likely mean, then: 1.

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread John Snow
On 10/30/20 6:26 AM, Alex Bennée wrote: Can we extract data as a CSV from Launchpad? Not sure, I don't have maintainer access there. Thomas? --js

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread Peter Maydell
On Fri, 30 Oct 2020 at 10:10, Daniel P. Berrangé wrote: > This > makes it more appealing to leave existing bugs in the LP tracker until > they are resolved, auto-closed, or there is a compelling reason to move > to gitlab. The compelling reason is that there is no way that I want to have to consu

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread Alex Bennée
John Snow writes: > On 10/29/20 3:55 PM, Thomas Huth wrote: >> On 29/10/2020 18.12, John Snow wrote: >>> On 10/29/20 12:49 PM, Alistair Francis wrote: On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: > > On Thu, 29 Oct 2020 12:01:27 -0400 > John Snow wrote: > >> I

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread Daniel P . Berrangé
On Fri, Oct 30, 2020 at 10:03:44AM +, Peter Maydell wrote: > On Fri, 30 Oct 2020 at 09:23, Daniel P. Berrangé wrote: > > My convincing strategy is "do nothing" :-) > > I am, er, not convinced :-) > > > Most importantly we need to be able to make the existing "QEMU" component > > in launch re

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread Peter Maydell
On Fri, 30 Oct 2020 at 09:23, Daniel P. Berrangé wrote: > My convincing strategy is "do nothing" :-) I am, er, not convinced :-) > Most importantly we need to be able to make the existing "QEMU" component > in launch read-only to prevent people filing new bugs there, ideally with > a change in t

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread Daniel P . Berrangé
On Thu, Oct 29, 2020 at 04:27:44PM -0400, John Snow wrote: > On 10/29/20 3:55 PM, Thomas Huth wrote: > > On 29/10/2020 18.12, John Snow wrote: > > > On 10/29/20 12:49 PM, Alistair Francis wrote: > > > > On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: > > > > > > > > > > On Thu, 29 Oct 2020 1

Re: Migrating to the gitlab issue tracker

2020-10-30 Thread Stefan Hajnoczi
On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: > In experimenting with my mirror on gitlab though, I was unable to find a way > to configure it to send issue tracker notifications to the email list. A > move to gitlab would likely mean, then: > > 1. The cessation of (automatic) issue t

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread Cornelia Huck
On Thu, 29 Oct 2020 14:04:04 -0400 John Snow wrote: > On 10/29/20 12:41 PM, Cornelia Huck wrote: > > On Thu, 29 Oct 2020 12:01:27 -0400 > > John Snow wrote: > > > >> If you're in the CC list, it's because you are listed in MAINTAINERS. > > > > > > > >> > >> Paolo's QEMU keynote this mo

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread John Snow
On 10/29/20 3:55 PM, Thomas Huth wrote: On 29/10/2020 18.12, John Snow wrote: On 10/29/20 12:49 PM, Alistair Francis wrote: On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: On Thu, 29 Oct 2020 12:01:27 -0400 John Snow wrote: If you're in the CC list, it's because you are listed in MAI

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread Thomas Huth
On 29/10/2020 18.12, John Snow wrote: > On 10/29/20 12:49 PM, Alistair Francis wrote: >> On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: >>> >>> On Thu, 29 Oct 2020 12:01:27 -0400 >>> John Snow wrote: >>> If you're in the CC list, it's because you are listed in MAINTAINERS. >>> >>> >>>

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread John Snow
On 10/29/20 12:41 PM, Cornelia Huck wrote: On Thu, 29 Oct 2020 12:01:27 -0400 John Snow wrote: If you're in the CC list, it's because you are listed in MAINTAINERS. Paolo's QEMU keynote this morning mentioned the possible use of the Gitlab issue tracker instead of using Launchpad. I'm q

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread Kashyap Chamarthy
On Thu, Oct 29, 2020 at 01:12:22PM -0400, John Snow wrote: Hi, [...] > Mostly I was looking for any hard objections over the idea of issues not > necessarily being sent to the list anymore, if there were any. Not an objection, but I would miss discovering "interesting" issues by virtue of bug e

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread John Snow
On 10/29/20 12:49 PM, Alistair Francis wrote: On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: On Thu, 29 Oct 2020 12:01:27 -0400 John Snow wrote: If you're in the CC list, it's because you are listed in MAINTAINERS. Paolo's QEMU keynote this morning mentioned the possible use of

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread Alistair Francis
On Thu, Oct 29, 2020 at 9:41 AM Cornelia Huck wrote: > > On Thu, 29 Oct 2020 12:01:27 -0400 > John Snow wrote: > > > If you're in the CC list, it's because you are listed in MAINTAINERS. > > > > > > > Paolo's QEMU keynote this morning mentioned the possible use of the > > Gitlab issue tracker in

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread Cornelia Huck
On Thu, 29 Oct 2020 12:01:27 -0400 John Snow wrote: > If you're in the CC list, it's because you are listed in MAINTAINERS. > > Paolo's QEMU keynote this morning mentioned the possible use of the > Gitlab issue tracker instead of using Launchpad. > > I'm quite fond of the gitlab issue track

Re: Migrating to the gitlab issue tracker

2020-10-29 Thread Daniel P . Berrangé
On Thu, Oct 29, 2020 at 12:01:27PM -0400, John Snow wrote: > If you're in the CC list, it's because you are listed in MAINTAINERS. > > Paolo's QEMU keynote this morning mentioned the possible use of the Gitlab > issue tracker instead of using Launchpad. > > I'm quite fond of the gitlab issue trac