xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <dvrabel@cantab.net>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: Xen 4.3 release planning proposal
Date: Thu, 30 Aug 2012 11:53:50 +0100	[thread overview]
Message-ID: <503F463E.90505@cantab.net> (raw)
In-Reply-To: <f9a8835e-95d8-4495-8c9d-4fa769913549@default>

On 29/08/12 21:53, Dan Magenheimer wrote:
> 
> Maybe it is time to move to match the well-known highly-greased
> Linux kernel release process?  This would include, for example, a short
> window for new functionality and a xen-next for pre-window shaking
> out and merging (of new functionality) and testing.  As has
> been pointed out, xen-unstable is, well, unstable for far too long.
>
> It may not be necessary to aggressively match Linus' 8-9 week release
> cycle or weekly rcN releases, but the core process is known to
> work very well, is reasonably well documented, and will be familiar
> to many in the open source community.

I think such a system only works if you have a short release cycle.  If
the only time to merge new features is two weeks in every 6/9 months
then that is just far too long and is not very contributor-friendly.

Xen doesn't have the number of contributors or changes that make a Linux
kernel style process necessary.

David

  parent reply	other threads:[~2012-08-30 10:53 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
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 [this message]
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=503F463E.90505@cantab.net \
    --to=dvrabel@cantab.net \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=dan.magenheimer@oracle.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).