On Thu, 2010-12-02 at 16:06 -0600, Brian Jackson wrote:
> On Monday, November 29, 2010 11:42:49 am Anthony Liguori wrote:
> > Hi,
> >
> > 0.13 was a mess of a release (largely due to my lack of time) and I'd
> > like to get us back onto a predictable schedule.
> >
> > Here's what I propose:
> >
On Monday, November 29, 2010 11:42:49 am Anthony Liguori wrote:
> Hi,
>
> 0.13 was a mess of a release (largely due to my lack of time) and I'd
> like to get us back onto a predictable schedule.
>
> Here's what I propose:
>
> 12/6 - fork off stable-0.14 tree; simultaneously release qemu-0.14.0-r
On Tue, 30 Nov 2010, Kevin Wolf wrote:
> Am 29.11.2010 18:42, schrieb Anthony Liguori:
> > 0.13 was a mess of a release (largely due to my lack of time) and I'd
> > like to get us back onto a predictable schedule.
>
> Telling people six days in advance when the fork will be is hardly
> predictab
Here's a slightly modified schedule to allow some outstanding bits on
the block tree to be merged before release.
12/17 - release qemu-0.14.0-rc0, for stable-0.14
12/27 - release qemu-0.14.0-rc1
1/3 - release qemu-0.14.0-rc2
1/5 - release qemu-0.14.0 based on -rc2 with just versioning changes
On Tue, 30 Nov 2010 15:49:24 +0100
Kevin Wolf wrote:
> Am 30.11.2010 15:12, schrieb Anthony Liguori:
> > On 11/30/2010 04:15 AM, Kevin Wolf wrote:
> >> Am 29.11.2010 18:42, schrieb Anthony Liguori:
> >>
> >>> 0.13 was a mess of a release (largely due to my lack of time) and I'd
> >>> like to
Am 29.11.2010 18:42, schrieb Anthony Liguori:
> 0.13 was a mess of a release (largely due to my lack of time) and I'd
> like to get us back onto a predictable schedule.
Telling people six days in advance when the fork will be is hardly
predictable. :-)
For example, in the block area there are cu
On 11/30/2010 04:15 AM, Kevin Wolf wrote:
Am 29.11.2010 18:42, schrieb Anthony Liguori:
0.13 was a mess of a release (largely due to my lack of time) and I'd
like to get us back onto a predictable schedule.
Telling people six days in advance when the fork will be is hardly
predictable
Am 30.11.2010 15:12, schrieb Anthony Liguori:
> On 11/30/2010 04:15 AM, Kevin Wolf wrote:
>> Am 29.11.2010 18:42, schrieb Anthony Liguori:
>>
>>> 0.13 was a mess of a release (largely due to my lack of time) and I'd
>>> like to get us back onto a predictable schedule.
>>>
>> Telling peopl
On Mon, 2010-11-29 at 14:14 -0600, Anthony Liguori wrote:
> 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
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 l
On 29.11.2010, at 20:29, Anthony Liguori wrote:
> On 11/29/2010 12:10 PM, Alexander Graf wrote:
>> On 29.11.2010, at 18:42, Anthony Liguori wrote:
>>
>>
>>> Hi,
>>>
>>> 0.13 was a mess of a release (largely due to my lack of time) and I'd like
>>> to get us back onto a predictable schedule.
On 11/29/2010 12:10 PM, Alexander Graf wrote:
On 29.11.2010, at 18:42, Anthony Liguori wrote:
Hi,
0.13 was a mess of a release (largely due to my lack of time) and I'd like to
get us back onto a predictable schedule.
Here's what I propose:
12/6 - fork off stable-0.14 tree; simultaneousl
On 29.11.2010, at 18:42, Anthony Liguori wrote:
> Hi,
>
> 0.13 was a mess of a release (largely due to my lack of time) and I'd like to
> get us back onto a predictable schedule.
>
> Here's what I propose:
>
> 12/6 - fork off stable-0.14 tree; simultaneously release qemu-0.14.0-rc0
>
> For t
Hi,
0.13 was a mess of a release (largely due to my lack of time) and I'd
like to get us back onto a predictable schedule.
Here's what I propose:
12/6 - fork off stable-0.14 tree; simultaneously release qemu-0.14.0-rc0
For the stable-0.14 tree, I'd like to have Justin be in charge of
collec
14 matches
Mail list logo
