From: Thomas Huth <thuth@redhat.com>
To: QEMU Developers <qemu-devel@nongnu.org>,
qemu-discuss <qemu-discuss@nongnu.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Switching to the GitLab bug tracker
Date: Mon, 3 May 2021 13:16:51 +0200 [thread overview]
Message-ID: <a6d77040-1dba-90c7-5ebe-5778177e686e@redhat.com> (raw)
Hi everybody!
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
Please note that this has some implications:
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.
2) It should be possible for everybody who has a Gitlab account to open new
bugs. If you are a maintainer of one of the QEMU subsystems, you might want
to help with changing certain aspects of bug tickets, too, e.g. add labels
or assign a ticket to you or somebody else. In that case you need to be
listed as a "Reporter" in the QEMU project, so please then get in touch with
one of the "Owners" of the project (see
https://gitlab.com/qemu-project/qemu/-/project_members ) and ask them to add
you as a "Reporter".
3) Gitlab has a nice mechanism for closing bugs automatically once the fix
gets merged to the master branch. To use this feature, please mark your
commit messages with a "Resolves: <URL-to-the-ticket>" line. See:
https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically
4) I'm in progress of automatically migrating the open bug tickets from
Launchpad to the Gitlab tracker. If you're interested, please keep an eye on
those tickets and tell me if you spot any oddity there - the script that I'm
using for the migration might not be perfect yet.
Thomas
next reply other threads:[~2021-05-03 11:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 11:16 Thomas Huth [this message]
2021-05-04 8:43 ` Switching to the GitLab bug tracker 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
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=a6d77040-1dba-90c7-5ebe-5778177e686e@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.