All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: 3.0.3 freeze
Date: Mon, 28 Aug 2006 15:58:39 +0100	[thread overview]
Message-ID: <20060828145839.GB862@redhat.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D5724D7@liverpoolst.ad.cl.cam.ac.uk>

On Tue, Aug 22, 2006 at 05:03:27PM +0100, Ian Pratt wrote:
> I think its time to declare a 3.0.3 feature freeze. We've got all the
> 'must have' feature patches in -unstable and many of the 'would be nice'
> variety too.

[snip]

> Now the tree is in 'freeze' state, please can everyone get ready to do
> some serious testing. We're still working on a handful of known issues
> we can reproduce, so this message isn't quite a full call to arms for
> testing from the user community yet, but it would be great if developers
> could start giving it a workout.  

Is the current bug fixing leading upto 3.0.3 still taking place on the
xen-unstable.hg tree, or has it branched & moved to another tree now ?

The 3.0 tree listed on xenbits doesn't seem to have any recent updates

  http://xenbits.xensource.com/xen-3.0-testing.hg

But xen-unstable.hg is receiving major changes that we really were not
expecting for a tree that is in freeze state. For example, the following
changeset that went into xen-unstable at the weekend will likely break
compatabilty for libvirt in quite a major way

  http://xenbits.xensource.com/xen-unstable.hg?cs=86d26e6ec89b

  "Replace dom0_ops hypercall with three new hypercalls:
    1. platform_op -- used by dom0 kernel to perform actions on the
       hardware platform (e.g., MTRR access, microcode update, platform
       quirks, ...)
    2. domctl -- used by management tools to control a specified domain
    3. sysctl -- used by management tools for system-wide actions"

Is this change going into 3.0.3, or is xen-unstable now reflecting the
development for 3.0.4 ?  We've got the means to support this new format
for hypercalls in libvirt, while keeping compatability for old API 
(detectable at runtime), but if its not going to 3.0.3 we can postpone 
this dev work... 

Regards,
Dan
--
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  parent reply	other threads:[~2006-08-28 14:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22 16:03 3.0.3 freeze Ian Pratt
2006-08-22 16:34 ` Sean Dague
2006-08-22 21:00 ` Ryan Harper
2006-08-22 21:12   ` Subrahmanian, Raj
2006-08-25  0:53 ` Tuan Van
2006-08-28 14:58 ` Daniel P. Berrange [this message]
2006-08-28 15:08   ` Keir Fraser
2006-08-28 15:21     ` Daniel P. Berrange
2006-08-28 15:49     ` Daniel Veillard
2006-08-28 16:32       ` Keir Fraser
2006-08-28 16:47         ` Rik van Riel
2006-08-28 16:48           ` Keir Fraser
2006-08-28 17:12             ` Rik van Riel
2006-08-28 17:19               ` Keir Fraser
2006-08-28 17:56         ` Daniel Veillard
2006-09-12 11:06 ` Anthony Wright
2006-09-12 11:40   ` Ian Pratt
2006-09-12 12:55     ` Anthony Wright
2006-09-12 13:45       ` Matt Ayres
2006-09-12 22:00         ` John Lenz
2006-09-13  9:33           ` Nicholas Lee
2006-09-19 11:21     ` Anthony Wright
2006-09-19 12:56       ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-08-28 15:22 Ian Pratt
2006-08-28 16:48 Ian Pratt
2006-08-28 17:03 ` Daniel P. Berrange
2006-08-28 20:16 ` Daniel Veillard

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=20060828145839.GB862@redhat.com \
    --to=berrange@redhat.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.