All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: RFC: Survey on release cycle
Date: Wed, 14 Oct 2015 13:43:22 +0100	[thread overview]
Message-ID: <1444826602.23192.184.camel@citrix.com> (raw)
In-Reply-To: <561E672302000078000AAE59@prv-mh.provo.novell.com>

On Wed, 2015-10-14 at 06:30 -0600, Jan Beulich wrote:
> > > > On 14.10.15 at 14:21, <ian.campbell@citrix.com> wrote:
> > Aside: I'm a bit confused regarding whether our "stable release scheme"
> > is
> > defined in terms of number of concurrently supported releases or in
> > terms
> > of an absolute time. 
> > http://wiki.xenproject.org/wiki/Xen_Project_Maintenance_Releases defini
> > tely
> > says it is concurrent release based, but your proposal above suggests
> > otherwise. Is the wiki wrong?
> 
> I think the distinction wasn't relevant with the (intended) 9 month
> cycle.

That's true, it also wouldn't really be relevant with any given new cycle.

But it does make talking about the new schemes confusing when they are
described in terms of the current scheme implicitly assuming one way or the
other.

Ian.

  reply	other threads:[~2015-10-14 12:43 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 [this message]
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

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=1444826602.23192.184.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.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.