All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
	Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: RFC: Survey on release cycle
Date: Thu, 29 Oct 2015 15:12:15 +0000	[thread overview]
Message-ID: <5632374F.80401@citrix.com> (raw)
In-Reply-To: <20151012173222.GE2421@zion.uk.xensource.com>

On 12/10/15 18:32, Wei Liu wrote:
> Hi all
>
> <snip>
>
> Please express your preference with -2 (strongly argue against), -1
> (not happy but not against), +1 (happy but won't argue for) and +2
> (happy and argue for).

With my XenServer hat on, the precise release doesn't matter too much. 
For a XenServer release, we will choose something (generally lastest
stable-X.Y) and freeze on it, with only targeted bug/security fixes
being backported later on.

However, with my upstream hat on, we do have a problem, and changing the
release cadence seems to be a plausible experiment to investigate fixing it.

>
> # 6 months release cycle + current stable release scheme
> # 6 months release cycle + LTS scheme

+1 to either of these.

>
>
> # 9 months release cycle + current stable release scheme

-1

>
> Don't change anything.

-1

~Andrew

      parent reply	other threads:[~2015-10-29 15:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 17:32 RFC: Survey on release cycle Wei Liu
2015-10-14 10:41 ` Dario Faggioli
2015-10-14 10:57 ` Stefano Stabellini
2015-10-14 12:21 ` Ian Campbell
2015-10-14 12:30   ` Jan Beulich
2015-10-14 12:43     ` Ian Campbell
2015-10-14 13:08   ` Wei Liu
2015-10-14 14:57     ` Ian Campbell
2015-10-26 15:27   ` Ian Jackson
2015-10-15  7:47 ` Jan Beulich
2015-10-15  9:33 ` Ian Campbell
2015-10-15 12:32   ` Olaf Hering
2015-10-15 16:42 ` Juergen Gross
2015-10-26 15:25 ` Ian Jackson
2015-10-29 15:12 ` Andrew Cooper [this message]

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=5632374F.80401@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=wei.liu2@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 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.