From: Peter Maydell <peter.maydell@linaro.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Stefan Weil <sw@weilnetz.de>, Leon Alrae <leon.alrae@imgtec.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH] target-mips: fix call to memset in soft reset code
Date: Thu, 12 May 2016 09:04:32 +0100 [thread overview]
Message-ID: <CAFEAcA-Fir8WCSZqWhjGfr69Wp7QiFgECwwP=ar8ep=8CRDrsg@mail.gmail.com> (raw)
In-Reply-To: <57343365.3020603@de.ibm.com>
On 12 May 2016 at 08:40, Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Maybe a topic for this years QEMU summit could be to talk about
> release process and release criterias.
Yeah, I'm happy to talk about what we could do better with
releases (both on the mailing list and at the summit). A
couple of notes:
This time around we had to delay by at least a week because of
the timing of the CVEs -- we had to allow a reasonable time
before raising the embargo for distros to prepare fixes, and
the bugs came in pretty close to when we'd otherwise have done
our final rc for the release.
I think one significant difference between us and Linux is that
we have fewer people testing our rcs, so I worry that if we put
more stuff in then we are less likely to notice bugs in it
in time.
The intended purpose of the "few days gap then final release
is same as last rc" approach is to give a safety valve in
case the patches that went into the final rc had some
horrendous bug in them. In this case the last rc only had the
CVE fixes so was pretty safe, but in previous releases we've
often had a few more patches than that in final-rc. I don't
think two extra days before reopening the tree is a very
big cost.
thanks
-- PMM
next prev parent reply other threads:[~2016-05-12 8:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 16:44 [Qemu-devel] [PATCH] target-mips: fix call to memset in soft reset code Aurelien Jarno
2016-05-09 17:53 ` Stefan Weil
2016-05-09 17:55 ` Peter Maydell
2016-05-09 17:57 ` Peter Maydell
2016-05-11 19:28 ` Christian Borntraeger
2016-05-11 22:41 ` Peter Maydell
2016-05-12 7:40 ` Christian Borntraeger
2016-05-12 8:04 ` Peter Maydell [this message]
2016-05-12 8:06 ` Cornelia Huck
2016-05-12 8:16 ` Christian Borntraeger
2016-05-12 11:45 ` Leon Alrae
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='CAFEAcA-Fir8WCSZqWhjGfr69Wp7QiFgECwwP=ar8ep=8CRDrsg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=aurelien@aurel32.net \
--cc=borntraeger@de.ibm.com \
--cc=leon.alrae@imgtec.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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).