From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexander Graf <agraf@suse.de>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] QEMU 0.14.0 release plan
Date: Mon, 29 Nov 2010 14:14:44 -0600 [thread overview]
Message-ID: <4CF409B4.8010508@codemonkey.ws> (raw)
In-Reply-To: <A420B057-044D-4B97-B8BB-CAD9C431371F@suse.de>
On 11/29/2010 01:58 PM, Alexander Graf wrote:
> On 29.11.2010, at 20:29, Anthony Liguori wrote:
>
>
>> Is 2 just right?
>>
> I was thinking of a more sophisticated model. Maybe 1 maintainer + 1 user? Or 1 person who knows his way around the area + 1 more?
>
+ 1 user? cute :-)
2 Acks seems like a good place to start.
>>
>>>> Thoughts?
>>>>
>>>>
>>> Please set up a mailing list we can just CC for stable candidates, so they don't get lost. Motivation for keeping track of stable stuff differs between developers and it's essential to make the kick-off easily accessible. It's worked out very well for Linux, so why not for us?
>>>
>>>
>> Is the desire to filter mail or have private discussions that are not on qemu-devel?
>>
>> If it's the former, a [STABLE] tag in the subject would work just as well. If it's the later, I think it runs contrary to the goal of getting more people involved in stable.
>>
> The desire is to have an easy to set tag. [STABLE] to me indicates that the patch is specifically made for stable. CC to stable@ tells me that the patch should go into stable as soon as it's submitted upstream and if it doesn't apply cleanly, the stable maintainer nags the author about a backport.
>
Okay, as long as stable is just there for CC and qemu-devel stays in the
loop. Can't do it right now but remind me again when Savannah is back up.
Regards,
Anthony Liguori
> Alex
>
>
next prev parent reply other threads:[~2010-11-29 20:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 17:42 [Qemu-devel] [RFC] QEMU 0.14.0 release plan Anthony Liguori
2010-11-29 18:10 ` Alexander Graf
2010-11-29 19:29 ` Anthony Liguori
2010-11-29 19:58 ` Alexander Graf
2010-11-29 20:14 ` Anthony Liguori [this message]
2010-11-30 10:15 ` Kevin Wolf
2010-11-30 14:12 ` Anthony Liguori
2010-11-30 14:49 ` Kevin Wolf
2010-12-01 12:56 ` Luiz Capitulino
2010-12-02 16:13 ` Randy Smith
2010-12-02 22:06 ` Brian Jackson
2010-12-02 22:44 ` Nicholas A. Bellinger
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=4CF409B4.8010508@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=agraf@suse.de \
--cc=jmforbes@linuxtx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.