xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: Xen 4.8 Development Update
Date: Wed, 20 Jul 2016 11:23:12 +0100	[thread overview]
Message-ID: <20160720102311.GA28784@citrix.com> (raw)
In-Reply-To: <684a4490-27cd-f11d-fd1e-c9bd20b550eb@citrix.com>

On Wed, Jul 20, 2016 at 10:34:01AM +0100, Andrew Cooper wrote:
> On 19/07/16 14:48, Wei Liu wrote:
> > This email only tracks big items for xen.git tree. Please reply for items you
> > woulk like to see in 4.8 so that people have an idea what is going on and
> > prioritise accordingly.
> >
> > You're welcome to provide description and use cases of the feature you're
> > working on.
> >
> > = Timeline =
> >
> > We now adopt a fixed cut-off date scheme. We will release twice a
> > year. The upcoming 4.8 timeline are as followed:
> >
> > * Last posting date: September 16, 2016
> > * Hard code freeze: September 30, 2016
> > * RC1: TBD
> > * Release: December 2, 2016
> >
> > Note that we don't have freeze exception scheme anymore. All patches
> > that wish to go into 4.8 must be posted no later than the last posting
> > date. All patches posted after that date will be automatically queued
> > into next release.
> >
> > RCs will be arranged immediately after freeze.
> >
> > = Projects =
> 
> I think it would be very wise to have a goal of
> 
> == Testing ==
> *  Have OSSTest running XTF tests
>   - Wei Liu
>   - Andrew Cooper
> 
> for 4.8
> 

This email only tracks code that would affect xen.git so I didn't add
that here.

But since you think it is relevant I can track it as well.

Wei.

> ~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-07-20 10:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 13:48 Xen 4.8 Development Update Wei Liu
2016-07-19 16:06 ` Tamas K Lengyel
2016-07-19 16:08   ` Wei Liu
2016-07-20  9:34 ` Andrew Cooper
2016-07-20 10:23   ` Wei Liu [this message]
2016-07-21  9:35 ` Andre Przywara
2016-07-21  9:37   ` Wei Liu
2016-07-21 14:02     ` Konrad Rzeszutek Wilk
2016-07-21 16:07 ` George Dunlap
2016-07-26 22:35   ` Pasi Kärkkäinen
2016-07-26 10:58 ` Daniel Kiper
  -- strict thread matches above, loose matches on Subject: below --
2016-08-03 11:33 Wei Liu
2016-08-03 11:56 ` Julien Grall
2016-08-03 12:03   ` Wei Liu
2016-08-03 12:15     ` Julien Grall
2016-08-31  8:30 Wei Liu
2016-08-31 12:37 ` Andrew Cooper
2016-08-31 12:39   ` Wei Liu
2016-08-31 14:21 ` Konrad Rzeszutek Wilk
2016-09-05 15:47   ` Dario Faggioli
2016-09-06 13:09     ` Konrad Rzeszutek Wilk
2016-08-31 15:00 ` Boris Ostrovsky
2016-09-01  6:04 ` Juergen Gross
2016-09-01  6:36 ` Sergej Proskurin
2016-09-08  7:29 ` Juergen Gross
2016-09-12 21:00 ` Daniel Kiper

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=20160720102311.GA28784@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).