From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com
Subject: Release manager for Xen 4.5
Date: Wed, 23 Apr 2014 12:17:04 -0400 [thread overview]
Message-ID: <20140423161704.GA10562@phenom.dumpdata.com> (raw)
Hey folks,
George has graciously volunteered to hand over the reins for
doing the release management to me.
He is going to enjoy more of the free time coding and such.
I put on the XenHackathon Wiki an slot to discuss roadmap
and what we want to have in Xen 4.5 - but we can also start
discussing it now.
The big question is how long do we want the cycle to be?
Xen 4.4 was eight months, so
a) did that work for you?
b) If it did not, would you want to be longer (9 months?)
c) or shorter (6 months?)
next reply other threads:[~2014-04-23 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 16:17 Konrad Rzeszutek Wilk [this message]
2014-04-23 16:38 ` Release manager for Xen 4.5 Igor Kozhukhov
2014-04-24 7:40 ` Jan Beulich
2014-04-25 10:44 ` Lars Kurth
2014-04-25 13:11 ` Konrad Rzeszutek Wilk
2014-05-06 11:41 ` Lars Kurth
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=20140423161704.GA10562@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--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 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).