All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.4 development update: Feature freeze has started
Date: Thu, 14 Nov 2013 10:28:13 +0100	[thread overview]
Message-ID: <1384421293.29902.46.camel@Abyss> (raw)
In-Reply-To: <CAFLBxZZ=3WdJtMROacABo5rjgG0AWcJ+NBYjJaKMoTxFOa78hg@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1013 bytes --]

On lun, 2013-11-11 at 17:18 +0000, George Dunlap wrote:

> = Timeline =
> 
> Here is our current timeline based on a 6-month release:
> 
> * Feature freeze: 18 October 2013 <== WE ARE HERE
> * Code freezing point: 18 November 2013 (Note date change)
> * First RC: 6 December 2013
> * Release: 21 January 2014
> 

> == Open ==

> * credit scheduler doesn't update other fields when tslice updated from sysctl
>  > Reported by Luwei Cheng <lwcheng@cs.hku.hk>
>  > http://bugs.xenproject.org/xen/bug/16
> 
George, are you working on this? If you plan to/already started
(especially considering that now that PVH is in you're going to have
tons of free time! :-P :-P), then fine.

If not, I'm ok trying to have a look...

Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  parent reply	other threads:[~2013-11-14  9:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-11 17:18 Xen 4.4 development update: Feature freeze has started George Dunlap
2013-11-11 17:32 ` Andrew Cooper
2013-11-15 14:36   ` George Dunlap
2013-11-15 14:44     ` Jan Beulich
2013-11-15 14:48     ` Andrew Cooper
2013-11-15 14:52       ` Andrew Cooper
2013-11-11 18:03 ` Konrad Rzeszutek Wilk
2013-11-12  8:55   ` Jan Beulich
2013-11-12 12:04     ` Stefano Stabellini
2013-11-12 14:17       ` Konrad Rzeszutek Wilk
2013-11-12  9:24   ` Ian Campbell
2013-11-11 20:49 ` Boris Ostrovsky
2013-11-11 21:02 ` Ben Guthro
2013-11-12 10:54 ` David Vrabel
2013-11-12 11:09 ` Ian Campbell
2013-11-12 11:11   ` Roger Pau Monné
2013-11-15 15:37     ` George Dunlap
2013-11-15 15:51       ` Roger Pau Monné
2013-11-12 11:20   ` Wei Liu
2013-11-12 11:53   ` Fabio Fantoni
2013-11-12 12:49   ` Stefano Stabellini
2013-11-12 14:20   ` Konrad Rzeszutek Wilk
2013-11-12 14:22     ` Ian Campbell
2013-11-12 14:26     ` Wei Liu
2013-11-12 15:07       ` Konrad Rzeszutek Wilk
2013-11-12 15:16         ` Wei Liu
2013-11-15 16:11   ` George Dunlap
2013-11-15 16:28   ` George Dunlap
2013-11-19 10:47     ` Ian Campbell
2013-11-14  9:28 ` Dario Faggioli [this message]
2013-11-14 14:16   ` Nate Studer
2013-11-14 22:20     ` Dario Faggioli
2013-11-15  9:03       ` Jan Beulich
2013-11-15  9:41         ` Dario Faggioli
2013-11-15  9:00   ` Jan Beulich
2013-11-14  9:38 ` Dario Faggioli
2013-11-14 13:42   ` Elena Ufimtseva
2013-11-15 16:34   ` George Dunlap
2013-11-15 18:07     ` Dario Faggioli
2013-11-15 20:39 ` Shriram Rajagopalan

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=1384421293.29902.46.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xen.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 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.