All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: 3.0-testing Status
Date: Wed, 14 Sep 2005 10:11:39 -0500	[thread overview]
Message-ID: <20050914151139.GA9386@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32DDE5@liverpoolst.ad.cl.cam.ac.uk>

* Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk> [2005-09-14 09:03]:
> > I was curious if there's an estimation on when 3.0-testing is 
> > going to be declared?  Is there a list of things that are 
> > outstanding before it will happen?
> 
> Renaming the -unstable tree would be a fairly pointless exercise so we
> haven't done so. We've been operating in 'testing' mode for some time,

Do you have any sort of list of features/bugs that you are tracking?
Also, do you have a list of your criteria for when 3.0 testing is ready
for release?  This sort of information and status would help us
understand where our efforts should be focused.

> working our way through the issues that are reported (and the ones that
> our extensive regression test infrastructure 'XenRT' picks up).

XenRT?  First I've heard of this.  Is it available? source? status?
output?  Anything on the wiki?

> Many of the oustanding issues are to do with the wide variety of
> hardware platforms xen is run on. To this end Dan/Chris/Tim have worked
> over the summer to create an automated 'test CD'. The CD is by no means
> as extensive as XenRT, but is targeted specifically to find h/w platform
> issues (does it boot, does network work, video, disks etc). We'll
> officially release the CD as soon as there are no platform-related
> issues on any of the machines we have access to (which is a fair range).
> We're quite close to that. 

Do any of the xensource guys file bugs in bugzilla regarding these
platform bugs that XenRT is turning up?  Even if they are fixed right
away, it is nice to have a record of issues that were encountered.

I'd also be interested in seen what range of hw you guys are testing
over as well.  


-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  parent reply	other threads:[~2005-09-14 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14  9:42 3.0-testing Status Ian Pratt
2005-09-14 13:19 ` Anthony Liguori
2005-09-14 15:08   ` Sean Dague
2005-09-14 15:11 ` Ryan Harper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-09-14 20:49 Ian Pratt
2005-09-14 21:46 ` Sean Dague
2005-09-13 18:25 Anthony Liguori

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=20050914151139.GA9386@us.ibm.com \
    --to=ryanh@us.ibm.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.