From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"John Snow" <jsnow@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [qemu-web PATCH] Update website to point to the new bug tracker at GitLab instead of Launchpad
Date: Mon, 3 May 2021 12:56:45 +0200 [thread overview]
Message-ID: <0cc06563-a543-fcdd-0fe3-c5a6eec4c514@redhat.com> (raw)
In-Reply-To: <92c95d95-dd59-4e52-ee14-a6b3925d43e0@amsat.org>
On 03/05/2021 12.47, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On 5/3/21 12:30 PM, Thomas Huth wrote:
>> We've started migrating the bug tickets from Launchpad to GitLab, so
>> it does not make too much sense anymore that users open new tickets
>> in the old system. Let's direct them now to the GitLab tracker instead.
>
> We should document the user has to request a Gitlab 'Reporter' access to
> the project, and warn there might be a delay of some days before the
> request to be accepted, before the user be able to fill the bug.
>
I think it is possible for everybody with a Gitlab account to file bugs. We
already have two tickets that were created by non-members:
https://gitlab.com/qemu-project/qemu/-/issues/47
https://gitlab.com/qemu-project/qemu/-/issues/45
AFAIK, you just need the "Reporter" state if you want to add labels to a
ticket, or if you want to assign it to somebody else.
Thomas
next prev parent reply other threads:[~2021-05-03 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 10:30 [qemu-web PATCH] Update website to point to the new bug tracker at GitLab instead of Launchpad Thomas Huth
2021-05-03 10:47 ` Philippe Mathieu-Daudé
2021-05-03 10:56 ` Thomas Huth [this message]
2021-05-03 13:05 ` Philippe Mathieu-Daudé
2021-05-03 23:26 ` John Snow
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=0cc06563-a543-fcdd-0fe3-c5a6eec4c514@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).