From: "Daniel P. Berrangé" <berrange@redhat.com>
To: P J P <ppandit@redhat.com>
Cc: peter.maydell@linaro.org,
Stefano Stabellini <sstabellini@kernel.org>,
Petr Matousek <pmatouse@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Darren Kenny <darren.kenny@oracle.com>,
Michael Roth <michael.roth@amd.com>
Subject: Re: [PATCH v1 1/1] security-process: update process information
Date: Thu, 3 Dec 2020 09:43:51 +0000 [thread overview]
Message-ID: <20201203094351.GB2952498@redhat.com> (raw)
In-Reply-To: <15934ps9-4so0-p464-s473-3sps7s652021@erqung.pbz>
On Thu, Dec 03, 2020 at 11:32:44AM +0530, P J P wrote:
> +-- On Wed, 2 Dec 2020, Daniel P. Berrangé wrote --+
> | > + - If issue is found to be less severe, an upstream public bug (or an
> | > + issue) will be created immediately.
> |
> | No need to repeat "or an issue". I think it would read more clearly as
> |
> | - If the severity of the issue is sufficiently low, an upstream public bug
> | may be created immediately.
>
> * Let's settle on public GitLab issues, shall we?
>
> * Tomorrow after an issue triage if someone asks where should they create a
> public tracker, it's better to have one definite answer, instead of choose
> either LaunchPad or GitLab issues.
>
> * OR is it better to have both? ie. file a public tracker anywhere as per ones
> convenience?
>
> * One GitLab is good I think.
Just link to the page where QEMU documents its bug tracker. That is
current laucnhpad, but may change to Gitlab. The security docs don't
need to mention the specific host, if we just link to the bugs page.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-12-03 9:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-30 13:49 [PATCH v1 0/1] security-process: update with mailing list details P J P
2020-11-30 13:49 ` [PATCH v1 1/1] security-process: update process information P J P
2020-12-01 19:49 ` Konrad Rzeszutek Wilk
2020-12-02 12:19 ` P J P
2020-12-02 12:34 ` Daniel P. Berrangé
2020-12-03 3:29 ` Stefano Stabellini
2020-12-03 5:36 ` P J P
2020-12-03 5:22 ` P J P
2020-12-03 6:02 ` P J P
2020-12-03 9:43 ` Daniel P. Berrangé [this message]
2020-12-02 13:50 ` Philippe Mathieu-Daudé
2020-12-03 5:21 ` P J P
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=20201203094351.GB2952498@redhat.com \
--to=berrange@redhat.com \
--cc=darren.kenny@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=michael.roth@amd.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmatouse@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=stefanha@gmail.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).