From: Thomas Huth <thuth@redhat.com>
To: "Stefano Garzarella" <sgarzare@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
qemu-discuss <qemu-discuss@nongnu.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: Switching to the GitLab bug tracker
Date: Wed, 5 May 2021 11:58:45 +0200 [thread overview]
Message-ID: <f7d8205b-ad22-877f-78ad-486beb56d4fc@redhat.com> (raw)
In-Reply-To: <20210505095530.lvpuyunqzv422app@steredhat>
On 05/05/2021 11.55, Stefano Garzarella wrote:
> On Tue, May 04, 2021 at 12:20:03PM +0200, Philippe Mathieu-Daudé wrote:
>> On 5/4/21 10:43 AM, Stefan Hajnoczi wrote:
>>> On Mon, May 03, 2021 at 01:16:51PM +0200, Thomas Huth wrote:
>>>> As you might have already noticed by some other mails on the qemu-devel
>>>> mailing list, we are in progress of switching our bug tracking tool from
>>>> Launchpad to Gitlab. The new tracker can now be found here:
>>>>
>>>> https://gitlab.com/qemu-project/qemu/-/issues
>>>
>>> Thank you for doing this, Thomas!
>>>
>>>> 1) We likely won't have the possibility anymore to automatically send
>>>> e-mail
>>>> notifications for new bugs to the qemu-devel mailing list. If you want to
>>>> get informed about new bugs, please use the notification mechanism from
>>>> Gitlab instead. That means, log into your gitlab account, browse to
>>>>
>>>> https://gitlab.com/qemu-project/qemu
>>>>
>>>> and click on the bell icon at the top of the page to manage your
>>>> notifications, e.g. enable notifications for "New issues" there.
>>>
>>> All maintainers and most regular contributors should follow the issue
>>> tracker so that QEMU developers are aware of new issues. Please do this!
>>>
>>> An alternative mechanism is the RSS/Atom feed available by clicking the
>>> "Subscribe to RSS feed" button left of the "New issue" button here:
>>>
>>> https://gitlab.com/qemu-project/qemu/-/issues
>>
>> You can also subscribe to labels of interest [*] going to
>> https://gitlab.com/qemu-project/qemu/-/labels
>>
>> For example in my case I subscribed to receive notifications
>> only from these labels:
>>
>> - kind:Bug
>> - Storage
>> - pflash
>> - Fuzzer
>> - workflow:Merged
>
> Cool feature, I also subscribed to some labels.
>
> I was trying to assign a label, for example "Storage" to this issue:
> https://gitlab.com/qemu-project/qemu/-/issues/96
>
> but I can't, should I have some special permission/role?
Yes, you need to be at least a "Reporter" in the members list of a project
to be able to add labels. You can ask one of the owners (see
https://gitlab.com/qemu-project/qemu/-/project_members) to add you as a
reporter.
Thomas
next prev parent reply other threads:[~2021-05-05 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 11:16 Switching to the GitLab bug tracker Thomas Huth
2021-05-04 8:43 ` Stefan Hajnoczi
2021-05-04 10:20 ` Philippe Mathieu-Daudé
2021-05-05 9:55 ` Stefano Garzarella
2021-05-05 9:58 ` Daniel P. Berrangé
2021-06-04 10:37 ` Philippe Mathieu-Daudé
2021-05-05 9:58 ` Thomas Huth [this message]
2021-05-05 10:16 ` Stefano Garzarella
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=f7d8205b-ad22-877f-78ad-486beb56d4fc@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
/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).