xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Juergen Gross <JGross@suse.com>,
	LarsKurth <lars.kurth@citrix.com>,
	wei.liu2@citrix.com, Ian Campbell <ian.campbell@citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	cardoe@cardoe.com, xen-devel@lists.xenproject.org,
	netwiz@crc.id.au, Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: RFC: LTS and stable release scheme
Date: Tue, 6 Oct 2015 16:01:24 +0100	[thread overview]
Message-ID: <20151006150124.GA1949@zion.uk.xensource.com> (raw)
In-Reply-To: <5613FC4702000078000A8A69@prv-mh.provo.novell.com>

On Tue, Oct 06, 2015 at 08:52:23AM -0600, Jan Beulich wrote:
> >>> On 06.10.15 at 16:09, <wei.liu2@citrix.com> wrote:
> > What do you propose when we regarding stable branches when we switch to
> > 6 months cycle?
> 
> See the chicken-and-egg problem: I can't answer this, because the
> issues with the stable trees are the main reason I don't support the
> change to the release cycle (yet).
> 

I have mistakenly taken your final reply to the other thread as your
agreement to the new release cycle.  Maybe we should continue our
discussion there. Let's draw an conclusion if we really want 6 months
before pursuing this LTS topic further.

Wei.

> Jan

  reply	other threads:[~2015-10-06 15:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 11:07 RFC: LTS and stable release scheme Wei Liu
2015-10-06 12:57 ` George Dunlap
2015-10-06 13:10 ` Ian Campbell
2015-10-06 16:25   ` Wei Liu
2015-10-06 16:30     ` Ian Campbell
2015-10-06 13:15 ` Wei Liu
2015-10-06 13:38 ` Jan Beulich
2015-10-06 14:09   ` Wei Liu
2015-10-06 14:52     ` Jan Beulich
2015-10-06 15:01       ` Wei Liu [this message]
2015-10-07 17:45       ` George Dunlap
2015-10-08  8:05         ` Jan Beulich
2015-10-08 10:39           ` George Dunlap
2015-10-08 11:48             ` Jan Beulich
2015-10-08 10:59           ` Ian Jackson
2015-10-08 11:34             ` Jan Beulich
     [not found]             ` <561670CD02000078000A94AA@suse.com>
2015-10-08 11:49               ` Juergen Gross
2015-10-08 12:22                 ` Jan Beulich
     [not found]                 ` <56167C0802000078000A953E@suse.com>
2015-10-08 12:39                   ` Juergen Gross
2015-10-08 13:52                     ` Wei Liu
2015-10-08 11:10           ` Wei Liu
2015-10-08 12:13             ` Jan Beulich
2015-10-08 14:23               ` Wei Liu
2015-10-08 15:01                 ` Jan Beulich
2015-10-08 11:10           ` George Dunlap
2015-10-06 14:12   ` George Dunlap
2015-10-06 14:49     ` Jan Beulich
2015-10-07 17:56   ` George Dunlap
2015-10-08  8:15     ` Jan Beulich
2015-10-06 15:27 ` Dario Faggioli

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=20151006150124.GA1949@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=JGross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=netwiz@crc.id.au \
    --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 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).