From: Thomas Huth <thuth@redhat.com>
To: "John Snow" <jsnow@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Alistair Francis" <alistair23@gmail.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: Migrating to the gitlab issue tracker
Date: Thu, 21 Jan 2021 11:57:56 +0100 [thread overview]
Message-ID: <d4dd9e44-9023-b655-b23f-cf139b178bf0@redhat.com> (raw)
In-Reply-To: <c75f91b7-6972-9e48-efa9-49792fc011d2@redhat.com>
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é <berrange@redhat.com> 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 consult two entirely separate bug tracking systems
>> to see what our reported bugs are. We must have an entry
>> in the new BTS for every 'live' bug, whether it was originally
>> reported to LP or to gitlab.
>>
>
> OK. I will try to investigate using the Launchpad API to pull our existing
> information, and then using the Gitlab API to re-create them. We will lose
> things like the list of subscribers and account information. Tags, Priority
> and Status can be preserved as labels. I'm not sure what the fate of
> attachments and other things are yet, I will see.
Hi John,
since we are switched now the main git repo to gitlab, and many of the
incomplete bugs on Launchpad already expired, what about switching the bug
tracker to Gitlab now, too? How far did you get with your migration scripts?
Thomas
next prev parent reply other threads:[~2021-01-21 10:59 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:01 Migrating to the gitlab issue tracker John Snow
2020-10-29 16:30 ` Daniel P. Berrangé
2020-10-29 16:41 ` Cornelia Huck
2020-10-29 16:49 ` Alistair Francis
2020-10-29 17:12 ` John Snow
2020-10-29 17:36 ` Kashyap Chamarthy
2020-10-29 19:55 ` Thomas Huth
2020-10-29 20:27 ` John Snow
2020-10-30 9:23 ` Daniel P. Berrangé
2020-10-30 10:03 ` Peter Maydell
2020-10-30 10:10 ` Daniel P. Berrangé
2020-10-30 10:57 ` Peter Maydell
2020-11-05 0:06 ` John Snow
2020-11-05 6:14 ` Thomas Huth
2020-11-05 9:54 ` Daniel P. Berrangé
2020-11-05 15:44 ` John Snow
2020-11-05 15:50 ` Daniel P. Berrangé
2020-11-08 9:00 ` Thomas Huth
2020-11-08 11:58 ` Peter Maydell
2020-11-09 8:04 ` Thomas Huth
2020-11-09 10:10 ` Daniel P. Berrangé
2020-11-09 10:14 ` Peter Maydell
2021-01-21 10:57 ` Thomas Huth [this message]
2021-01-21 16:20 ` John Snow
2020-10-30 10:26 ` Alex Bennée
2020-10-30 12:53 ` John Snow
2020-11-08 8:57 ` Thomas Huth
2020-10-29 18:04 ` John Snow
2020-10-29 20:33 ` Cornelia Huck
2020-10-30 9:16 ` Stefan Hajnoczi
2020-10-30 15:39 ` John Snow
2020-11-02 13:57 ` Laszlo Ersek
2020-11-02 14:26 ` Daniel P. Berrangé
2020-11-02 14:42 ` Eric Blake
2020-11-04 17:10 ` Laszlo Ersek
2020-11-04 17:03 ` Laszlo Ersek
2020-11-04 17:19 ` Daniel P. Berrangé
2020-11-06 15:37 ` Laszlo Ersek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d4dd9e44-9023-b655-b23f-cf139b178bf0@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alistair23@gmail.com \
--cc=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).