On 7 June 2016 at 20:15, Michael Roth wrote:
> Quoting Peter Maydell (2016-06-07 13:45:06)
>> But I think the real problem with a schedule which expects a
>> release at the tail end of August is that we then only have
>> three and a half months left til mid-December which is in
>> practice the lat
Quoting Peter Maydell (2016-06-07 13:45:06)
> On 7 June 2016 at 18:29, Michael Roth wrote:
> > I think it is actually bit shorter of a window this time. The last few
> > releases had around 2.5 to 3 months between n-1 release and hard freeze /
> > rc0
> > for n+1, but the proposed date would be j
On 7 June 2016 at 18:29, Michael Roth wrote:
> I think it is actually bit shorter of a window this time. The last few
> releases had around 2.5 to 3 months between n-1 release and hard freeze / rc0
> for n+1, but the proposed date would be just around 2 months.
Yeah, it's a bit short because the
Quoting Alex Bennée (2016-06-07 02:29:38)
>
> Peter Maydell writes:
>
> > Well, time to make a decision about our release date for 2.7.
> >
> > If you start out with "let's put the release in august like it
> > usually is but not so close to KVM Forum (24-26 Aug) as to
> > be likely to slip in t
On 7 June 2016 at 08:29, Alex Bennée wrote:
> Do you collect a list of baking features likely to go in or is it just a
> case of "patches have been on list by now"?
I don't collect feature lists; I treat QEMU releases as roughly
fixed dates, and whatever's ready to go in gets in. We have
settled
Peter Maydell writes:
> Well, time to make a decision about our release date for 2.7.
>
> If you start out with "let's put the release in august like it
> usually is but not so close to KVM Forum (24-26 Aug) as to
> be likely to slip in to it", then you get something like:
>
> Jun 21 softfreeze
On 06/06/2016 05:34 PM, Peter Maydell wrote:
> Well, time to make a decision about our release date for 2.7.
>
> If you start out with "let's put the release in august like it
> usually is but not so close to KVM Forum (24-26 Aug) as to
> be likely to slip in to it", then you get something like:
>
Well, time to make a decision about our release date for 2.7.
If you start out with "let's put the release in august like it
usually is but not so close to KVM Forum (24-26 Aug) as to
be likely to slip in to it", then you get something like:
Jun 21 softfreeze
Jul 12 hardfreeze, rc0
Jul 19 rc1
Jul
