All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Keir Fraser <keir@xensource.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [ANNOUNCEMENT] Schedule for Xen 3.0.4
Date: Fri, 24 Nov 2006 10:42:53 +0000	[thread overview]
Message-ID: <20061124104253.GA28087@totally.trollied.org> (raw)
In-Reply-To: <C18C79DB.4F96%keir@xensource.com>

On Fri, Nov 24, 2006 at 10:28:43AM +0000, Keir Fraser wrote:

> release candidates for 3.0.4 once or twice a week until we have a tree
> suitable for final release (hopefully by the middle of December). Meanwhile

Does this mean we have less than a month until the Xen API work is
frozen, as was previously the plan for 3.0.4? We're still discussing
aspects of it and AFAIK there's still a lot of work to do in just
finishing defining it, never mind coding it or any "can I actually
program against this" stuff.

regards,
john

  reply	other threads:[~2006-11-24 10:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 10:28 [ANNOUNCEMENT] Schedule for Xen 3.0.4 Keir Fraser
2006-11-24 10:42 ` John Levon [this message]
2006-11-24 10:58   ` Ewan Mellor
2006-11-24 15:54     ` Daniel P. Berrange
2006-11-24 16:34       ` Ewan Mellor
2006-11-24 18:22         ` Daniel P. Berrange
2006-11-28 14:26         ` Ewan Mellor
2006-11-28 14:37           ` Daniel P. Berrange
2006-11-29 17:12           ` Daniel P. Berrange
2006-11-24 12:44 ` Jan Beulich
2006-11-24 18:26 ` Chuck Short
2006-11-29 15:31 ` Sean Dague
2006-11-29 21:36   ` Ian Pratt
2006-11-30  9:05     ` Keir Fraser
2006-11-30 14:59 ` Pasi Kärkkäinen
2006-11-30 15:02   ` Keir Fraser
2006-11-30 15:08     ` Pasi Kärkkäinen
2006-11-30 16:57       ` Keir Fraser
2006-11-30 17:27       ` Ian Pratt
     [not found] <4566D99C.5050009@suse.de>
2006-11-24 14:05 ` Keir Fraser
2006-11-24 14:41   ` Gerd Hoffmann

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=20061124104253.GA28087@totally.trollied.org \
    --to=levon@movementarian.org \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.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 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.