From: Gerd Hoffmann <kraxel@suse.de>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: RE: New Release Process
Date: Fri, 27 Jan 2006 11:56:18 +0100 [thread overview]
Message-ID: <43D9FC52.2070507@suse.de> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D40A3A3@liverpoolst.ad.cl.cam.ac.uk>
Hi,
> SuSE have said they are actually going to base their release off 2.6.16,
> even though we're still likely to be on 2.6.16-rcX by their freeze date.
> One thing we could do to help them is to break with tradition and to
> check the 2.6.16-rcX into the tree rather than the most recent stable
> release, 2.6.15. This would help get 2.6.16 stabilized quicker, which
> would certainly help them. 2.6.16 is already at rc1, which means that
> many of the 'rough edges' should have been found, so I doubt we'll be
> hurting ourselves too much. This is -unstable, after all.
Question: Which tree(s) are run through the XenRT test suite? Is this
only xen-unstable.hg? If so, then merging 2.6.16-rc1 into unstable
would be very helpful. Not only for us, but also to make it stable for
the mainline merge. If the linux-2.6-xen.hg and ext/linux-2.6-merge.hg
trees are regression-tested as well it would be less important. But
would probably still give us more people testing the code on different
hardware ...
cheers,
Gerd
--
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.
http://www.suse.de/~kraxel/just-married.jpeg
next prev parent reply other threads:[~2006-01-27 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 18:20 New Release Process Ian Pratt
2006-01-26 18:30 ` Mark Williamson
2006-01-26 18:32 ` Nivedita Singhvi
2006-01-26 18:45 ` Matt Ayres
2006-01-27 10:36 ` Keir Fraser
2006-01-27 23:18 ` Matt Ayres
2006-01-26 19:31 ` Anthony Liguori
2006-01-27 10:56 ` Gerd Hoffmann [this message]
2006-01-27 15:04 ` Vincent Hanquez
2006-01-27 21:45 ` Paul Larson
-- strict thread matches above, loose matches on Subject: below --
2006-01-28 8:40 Ian Pratt
2006-01-27 22:10 Ian Pratt
2006-01-27 19:56 Wahlig, Elsie
2006-01-27 3:02 Nakajima, Jun
2006-01-26 23:34 Ian Pratt
2006-01-26 19:42 Nakajima, Jun
2006-01-24 23:11 Ian Pratt
2006-01-24 23:18 ` Matt Ayres
2006-01-25 9:59 ` Patrick Scharrenberg
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=43D9FC52.2070507@suse.de \
--to=kraxel@suse.de \
--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.