qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
	KVM devel mailing list <kvm@vger.kernel.org>,
	quintela@redhat.com
Subject: Re: [Qemu-devel] KVM call agenda for October 11th
Date: Tue, 11 Oct 2011 07:54:23 -0500	[thread overview]
Message-ID: <4E943C7F.50601@codemonkey.ws> (raw)
In-Reply-To: <4E942A41.7070707@redhat.com>

On 10/11/2011 06:36 AM, Paolo Bonzini wrote:
> On 10/10/2011 01:35 PM, Juan Quintela wrote:
>>
>> Hi
>>
>> Please send in any agenda items you are interested in covering.
>
> Planning the feature freeze:
>
> - what is left to merge?
>
> - test day?

Great topic.  Just a reminder, we're looking at release dates of:

| 2011-10-15
| Soft freeze
|-
| 2011-11-01
| Hard master
|-
| 2011-11-07
| Tag qemu-1.0-rc1
|-
| 2011-11-14
| Tag qemu-1.0-rc2
|-
| 2011-11-21
| Tag qemu-1.0-rc3
|-
| 2011-11-28
| Tag qemu-1.0-rc4
|-
| 2011-12-01
| Tag qemu-1.0

Soft Freeze FAQ:

== What is the soft feature freeze? ==

The soft feature freeze is the beginning of the stabilization phase of QEMU's 
development process.  By the date of the soft feature freeze, any major feature 
should have some code posted to the qemu-devel mailing list if it's targeting a 
given release.

== What should I do by the soft feature freeze? ==

For any major feature that you're targeting to the next release, you should:

# Make sure that you've posted a patch series to qemu-devel
# Write a Feature page on the qemu.org wiki describing the feature and the 
motivation
# On the release planning wiki page, link to your feature wiki page.

== Will my patches be rejected if I don't post before the soft feature freeze? ==

That's ultimately up to the subsystem maintainer.  It's a value call based on 
the relative importance of the feature verses the disruptiveness of the feature. 
  It's always best to avoid this problem in the first place and release early, 
release often[http://en.wikipedia.org/wiki/Release_early,_release_often].

Regards,

Anthony Liguori

>
> Paolo
>

  reply	other threads:[~2011-10-11 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10 11:35 [Qemu-devel] KVM call agenda for October 11th Juan Quintela
2011-10-11 11:36 ` Paolo Bonzini
2011-10-11 12:54   ` Anthony Liguori [this message]
2011-10-11 11:48 ` Avi Kivity
2011-10-11 13:01   ` Anthony Liguori
2011-10-11 13:21     ` Avi Kivity
2011-10-11 13:27       ` Anthony Liguori
2011-10-11 13:47         ` Avi Kivity
2011-10-11 13:57           ` Anthony Liguori
2011-10-11 14:01             ` Avi Kivity
2011-10-11 14:34               ` Anthony Liguori
2011-10-11 14:43                 ` Avi Kivity
2011-10-11 13:27   ` Juan Quintela
2011-10-11 13:54     ` Anthony Liguori
2011-10-11 15:39       ` Stefan Berger

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=4E943C7F.50601@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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).