From: Markus Armbruster <armbru@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [RFC] 1.4 release schedule
Date: Thu, 06 Dec 2012 09:05:34 +0100 [thread overview]
Message-ID: <87624fa9m9.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <CAAu8pHtJqwXc=-0RBEBMkAg+5NZo1=J5RMJrsLD+Hy67N_Bnsw@mail.gmail.com> (Blue Swirl's message of "Wed, 5 Dec 2012 19:58:50 +0000")
Blue Swirl <blauwirbel@gmail.com> writes:
> On Wed, Dec 5, 2012 at 7:41 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Hi,
>>
>>
>> On 12/05/2012 08:28 PM, Blue Swirl wrote:
>>>
>>> On Tue, Dec 4, 2012 at 10:00 PM, Anthony Liguori <aliguori@us.ibm.com>
>>> wrote:
>>>>
>>>> Peter Maydell <peter.maydell@linaro.org> writes:
>>>>
>>>>> On 4 December 2012 18:38, Blue Swirl <blauwirbel@gmail.com> wrote:
>>>>>>
>>>>>> The definition of the hard freeze bothers me. A few patches that went
>>>>>> in after 1.3-rc0 were not bug fixes but just new features, so the
>>>>>> difference between soft and hard freezes was not clear.
>>>>>
>>>>>
>>>>> My vote for this would be to adhere to our definition
>>>>> and only commit bugfixes.
>>>>
>>>>
>>>> Let's get specific. What was committed post hard freeze that's not a
>>>> bug fix?
>>>
>>>
>>> d3067b0 Documentation: Update image format information
>>> a13e5e0 Documentation: Update block cache mode information
>>> 044d003 qemu-tech.texi: update implemented xtensa features list
>>
>>
>> Adding missing / updating docs to be more accurate is a bug fix,
>> and one with a very low chance of causing regressions at that.
>
> I don't think they are bug fixes but improvements to documentation
> features. But I agree patches only touching documentation, comment and
> string contents could be exempted.
What about improvements to tests? No impact on anything but "make
check".
[...]
next prev parent reply other threads:[~2012-12-06 8:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:30 [Qemu-devel] [RFC] 1.4 release schedule Anthony Liguori
2012-12-03 21:34 ` Johnson, Eric
2012-12-03 21:41 ` Anthony Liguori
2012-12-04 18:38 ` Blue Swirl
2012-12-04 18:42 ` Peter Maydell
2012-12-04 19:16 ` Blue Swirl
2012-12-04 22:00 ` Anthony Liguori
2012-12-05 19:28 ` Blue Swirl
2012-12-05 19:41 ` Hans de Goede
2012-12-05 19:58 ` Blue Swirl
2012-12-06 8:05 ` Markus Armbruster [this message]
2012-12-06 21:27 ` Blue Swirl
2012-12-06 10:19 ` Kevin Wolf
2012-12-06 21:45 ` Blue Swirl
2012-12-06 9:01 ` Andreas Färber
2012-12-06 21:35 ` Blue Swirl
2012-12-04 18:41 ` 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=87624fa9m9.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=hdegoede@redhat.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.