All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [ANNOUNCE] We are now in soft freeze for 1.6
Date: Sun, 21 Jul 2013 07:52:17 -0500	[thread overview]
Message-ID: <87ppuculby.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA--wyW==_-Q9yizVE3aJAFVsmnQkqpoEiM9RnmAaZmq9A@mail.gmail.com>

Peter Maydell <peter.maydell@linaro.org> writes:

> On 15 July 2013 16:15, Anthony Liguori <aliguori@us.ibm.com> wrote:
>> Hard freeze is two weeks away.
>>
>> http://wiki.qemu.org/Planning/1.6
>
> I've just noticed that this is still inconsistent. That
> page says:
>
> "Soft feature freeze. Major features should have initial code
> committed by this date."
>
> but it links to http://wiki.qemu.org/Planning/SoftFeatureFreeze
> which says
> "By the date of the soft feature freeze, any major feature
> should have some code posted to the qemu-devel mailing list"
>
> I'm pretty sure the latter is right (you only need code
> posted, not committed) -- can we fix whichever of the two
> pages is wrong, please?

It depends on the definition of "major".  Any *feature* should have
patches posted by soft freeze.  I guess a tiny feature would be an
exception.

For major features (things that have a high likelihood of breaking
things), the feature should have started getting merged already.

I'll update the wiki text to be clearer.

Regards,

Anthony Liguori

>
> thanks
> -- PMM

  reply	other threads:[~2013-07-21 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 15:15 [Qemu-devel] [ANNOUNCE] We are now in soft freeze for 1.6 Anthony Liguori
2013-07-19 11:07 ` Peter Maydell
2013-07-21 12:52   ` Anthony Liguori [this message]
2013-10-15 12:50     ` Peter Maydell
2013-10-18 14:38     ` Peter Maydell

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=87ppuculby.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=peter.maydell@linaro.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.