From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: RFC: Survey on release cycle Date: Mon, 26 Oct 2015 15:25:26 +0000 Message-ID: <22062.17894.254978.106759@mariner.uk.xensource.com> References: <20151012173222.GE2421@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZqjeO-0003ii-GY for xen-devel@lists.xenproject.org; Mon, 26 Oct 2015 15:25:32 +0000 In-Reply-To: <20151012173222.GE2421@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org Wei Liu writes ("[Xen-devel] RFC: Survey on release cycle"): > 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). > > # 6 months release cycle + current stable release scheme > > The same stable release scheme applies (18 months full support + 18 > months security fixes). Encourage more people to step up to share the > maintenance burden if necessary. Automate part of the workflow to > maintain stable releases. Write down guideline for maintainers. +2 > # 6 months release cycle + LTS scheme > > Pick LTS release every 4 releases. Announce LTS before hand. Non-LTS > releases receive shorter support. Encourage more people to step up to > share the maintenance burden if necessary. Automate part of the > workflow to maintain stable releases and LTS releases. Write down > guideline for maintainers. +1 > The length of support hasn't been discussed thoroughly -- but to make > LTS scheme stand out the length of support would be longer than what > we have now (18 + 18). > > # 9 months release cycle + current stable release scheme -2 Ian.