xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Attilio Rao <attilio.rao@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen 4.3 release planning proposal
Date: Tue, 21 Aug 2012 15:36:58 +0100	[thread overview]
Message-ID: <50339D0A.2070909@citrix.com> (raw)
In-Reply-To: <5033BAA00200007800096BB0@nat28.tlf.novell.com>

On 21/08/12 15:43, Jan Beulich wrote:
>>>> On 20.08.12 at 18:46, George Dunlap<George.Dunlap@eu.citrix.com>  wrote:
>>>>          
>> So I propose that we move to a time-based release schedule.  Rather
>> than aiming for a release date, I propose that we aim to do a "feature
>> freeze" six months after the 4.2 release -- that would be around March
>> 1, 2013.  That way we'll probably end up releasing in 9 months' time,
>> around June 2013.  This is one of the things we can discuss at the Dev
>> Meeting before the Xen Summit next week.  If you have other opinions,
>> please let us know.
>>      
> That would make for a scheduled 3 month feature freeze. I don't
> recall for how long we've been in feature freeze for 4.2 now, but
> from my perspective this is already definitely too long. Over that
> time I accumulated around 50 patches (not counting the bug fixes
> that I keep posting), and I'm sure it was never that bad during
> earlier feature freeze periods.
>
>    
>> * Event channel scalability
>>    owner: attilio@citrix
>>    Increase limit on event channels (currently 1024 for 32-bit guests,
>>    4096 for 64-bit guests)
>>      
> This one I have on my todo list as well.
>
>    

Do you mean that you already have a patch for that?
I'm starting making a complete plan for it. I discussed with Ian 
Campbell some aspects and I plan to send a detailed e-mail in the next 
few days.

Attilio

  reply	other threads:[~2012-08-21 14:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 16:46 Xen 4.3 release planning proposal George Dunlap
2012-08-20 19:14 ` Pasi Kärkkäinen
2012-08-21 12:56   ` George Dunlap
2012-08-21 18:27     ` Pasi Kärkkäinen
2012-12-17 23:57   ` Martinx - ジェームズ
2012-12-18  7:03     ` Pasi Kärkkäinen
2012-12-18 13:37       ` Martinx - ジェームズ
2012-12-18 13:49         ` Jan Beulich
2012-08-20 20:28 ` Konrad Rzeszutek Wilk
2012-08-21 10:06   ` George Dunlap
2012-08-21 14:26     ` Konrad Rzeszutek Wilk
2012-08-21 14:43 ` Jan Beulich
2012-08-21 14:36   ` Attilio Rao [this message]
2012-08-21 14:55     ` Jan Beulich
2012-08-21 15:04   ` George Dunlap
2012-08-29 20:53 ` Dan Magenheimer
2012-08-30 10:24   ` Andrew Cooper
2012-08-30 10:53   ` David Vrabel
2012-08-30 16:11     ` Dan Magenheimer
2012-08-31 11:01       ` Jan Beulich
2012-08-31 17:59         ` Dan Magenheimer
     [not found] <mailman.11058.1345490072.1399.xen-devel@lists.xen.org>
2012-08-21 14:50 ` Andres Lagar-Cavilla
2012-08-21 18:44   ` Pasi Kärkkäinen

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=50339D0A.2070909@citrix.com \
    --to=attilio.rao@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.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 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).