* [Qemu-devel] 2.4 tree reopened; post-mortem of 2.3
@ 2015-04-27 17:04 Peter Maydell
2015-04-27 18:46 ` Andreas Färber
0 siblings, 1 reply; 2+ messages in thread
From: Peter Maydell @ 2015-04-27 17:04 UTC (permalink / raw)
To: QEMU Developers
Michael has just sent out the email announcing the final 2.3
release, and I've officially reopened git master for 2.4.
If you have any opinions about things we should try to do better
or just differently next release, this is probably a good place
to do that. Personally I have a couple of things:
(1) Timely application of security related patches
We had a couple of CVE-fixing patches which took longer than ideal
to be applied to master. I think we could do better than this,
and probably the solution here is to loop the appropriate submaintainer
and somebody with commit access to master (ie me) on the predisclosure
bit of our security process.
Do we also want to arrange for patches to be committed to stable
branches? It sounds like a good idea to me but I'll leave that up
to those who admin the stable branches.
(2) Late-breaking "this platform/compilation option combo is
completely broken" issues
Notably 32-bit PPC and ARM with latest libseccomp. Can we do
anything to try to surface this sort of thing earlier in the
release cycle, or is it just a fact of life that we have too many
combinations to be able to get to testing them all in time?
thanks
-- PMM
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] 2.4 tree reopened; post-mortem of 2.3
2015-04-27 17:04 [Qemu-devel] 2.4 tree reopened; post-mortem of 2.3 Peter Maydell
@ 2015-04-27 18:46 ` Andreas Färber
0 siblings, 0 replies; 2+ messages in thread
From: Andreas Färber @ 2015-04-27 18:46 UTC (permalink / raw)
To: Peter Maydell, QEMU Developers; +Cc: Alexander Graf
Am 27.04.2015 um 19:04 schrieb Peter Maydell:
> (2) Late-breaking "this platform/compilation option combo is
> completely broken" issues
>
> Notably 32-bit PPC and ARM with latest libseccomp. Can we do
> anything to try to surface this sort of thing earlier in the
> release cycle, or is it just a fact of life that we have too many
> combinations to be able to get to testing them all in time?
All the features that I have enabled for 2.3 in our OBS now (including
libseccomp via a revert) will also be build-tested once I check in the
next -rc0 tarball. For now I don't package nightly Git versions though.
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
Graham Norton; HRB 21284 (AG Nürnberg)
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-04-27 18:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-04-27 17:04 [Qemu-devel] 2.4 tree reopened; post-mortem of 2.3 Peter Maydell
2015-04-27 18:46 ` Andreas Färber
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).