From: Aurelien Jarno <aurelien@aurel32.net>
To: Chris Wright <chrisw@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] KVM call minutes for July 20
Date: Tue, 20 Jul 2010 18:29:52 +0200 [thread overview]
Message-ID: <20100720162952.GK26579@hall.aurel32.net> (raw)
In-Reply-To: <20100720144551.GB32665@x200.localdomain>
It's a pitty I can't easily attend to this conference call, as it seems
a lot of decisions are taken there. Anyway let me comment the part
concerning 0.12 stable:
On Tue, Jul 20, 2010 at 07:45:51AM -0700, Chris Wright wrote:
> 0.12.stable
> - start w/ git tree + pull requests
> - release process is separate from commit access
> - justin will put up a tree for pull requests
> - there's current backlog, what about that?
I think someone should actively follow the patches committed to HEAD and
backport them when they seems to be stable material. I guess it's what's
Justin plans to do.
OTOH, it might be useful if people sending patches to HEAD adds a small
comment about cherry-picking the patch to stable if it applies.
> - anthony's concern with -stable is the testing (upstream tree gets more
> testing than -stable)
Debian gets regular uploads with the contents of the -stable tree
between to releases. Also patches from trunk are all cherry-picked from
HEAD.
> - 0.12.5?
> - planning to do next w/ 0.13 release
> - aurelien may cut a release
Following the minutes from last week, I sent a call for release, with a
deadline today. I only got the patch series from Kevin. There are
currently 44 patches waiting in the stable tree, so I guess we can go
for a release. I plan to do that later this week if nobody opposes.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2010-07-20 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 14:45 KVM call minutes for July 20 Chris Wright
2010-07-20 16:29 ` Aurelien Jarno [this message]
2010-07-20 17:55 ` [Qemu-devel] " Anthony Liguori
2010-07-20 16:40 ` David S. Ahern
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=20100720162952.GK26579@hall.aurel32.net \
--to=aurelien@aurel32.net \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@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