All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>
Cc: Juergen Gross <JGross@suse.com>,
	LarsKurth <lars.kurth@citrix.com>, Wei Liu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Steven Haigh <netwiz@crc.id.au>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>
Subject: Re: RFC: LTS and stable release scheme
Date: Thu, 8 Oct 2015 12:10:54 +0100	[thread overview]
Message-ID: <56164F3E.3050205@citrix.com> (raw)
In-Reply-To: <56163FFF02000078000A9303@prv-mh.provo.novell.com>

On 08/10/15 09:05, Jan Beulich wrote:
>> It has so far been assumed in this discussion that this would be an
>> undue burden, and therefore not acceptable.
> 
> I don't think anyone said "undue". All that was said was that the
> amount of work to be put into this increases.

I think it's worth saying that the amount of effort it takes to make
maintenance releases -- in particular, the amount of tedious busy work
for you -- is a first-order consideration in this, particularly as you
don't see any value in the change.  It is certainly not reasonable for
everyone who is not directly affected to vote to give you more work, and
it would be perfectly reasonable for you to say that if we went to a
6-month release cycle, others would have to share (or take) the burden
of doing that busy-work.

 -George

  parent reply	other threads:[~2015-10-08 11:11 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
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 [this message]
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=56164F3E.3050205@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=George.Dunlap@eu.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=ian.campbell@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=netwiz@crc.id.au \
    --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.