From: "Justin M. Forbes" <jmforbes@linuxtx.org>
To: qemu-devel@nongnu.org
Cc: qemu-stable@nongnu.org
Subject: [Qemu-devel] Qemu stable releases
Date: Mon, 05 Dec 2011 14:08:03 -0600 [thread overview]
Message-ID: <1323115683.6884.8.camel@fedora64.linuxtx.org> (raw)
The stable tree for 1.0 has now been created and the mailing list
exists. I am curious as to people's thoughts on how we should proceed.
There was discussion of setting up a predictable time table for stable
releases, say monthly or bimonthly, though that seems a bit difficult
from past experience. Typically I get a flurry of patches shortly after
a release (and they have already started for 1.0). I have tried to get
a .1 release out in a timely manner, and then it seems patches for
stable become few and far between. In the 0.14 and 0.15 series, not
even enough to warrant a .2 release. Perhaps this is due to lack fixed
issues, or lack of effort to submit to stable. What I would like to
recommend is the following:
1) On the 15th of every month, the stable queue will be evaluated for
release.
2) If enough patches exist (or critical enough patches exist), a stable
release will be cut as soon as testing/push/mirror can be done. If
there are no patches, or not enough patches to warrant a release, they
will be held over until the next release.
3) Security fixes do not follow this schedule, and will trigger a stable
release as needed.
Questions, comments, concernes? How do people feel about this?
Justin
next reply other threads:[~2011-12-05 20:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 20:08 Justin M. Forbes [this message]
2011-12-06 9:27 ` [Qemu-devel] Qemu stable releases Stefan Hajnoczi
2011-12-09 10:39 ` Richard W.M. Jones
2011-12-09 12:01 ` Richard W.M. Jones
2011-12-09 13:25 ` Anthony Liguori
2011-12-09 13:47 ` Richard W.M. Jones
2011-12-09 12:55 ` Andreas Färber
2011-12-09 13:24 ` Anthony Liguori
2011-12-09 13:50 ` Andreas Färber
2011-12-09 13:28 ` Justin M. Forbes
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=1323115683.6884.8.camel@fedora64.linuxtx.org \
--to=jmforbes@linuxtx.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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).