From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: Xen 4.3 release planning proposal Date: Thu, 30 Aug 2012 11:53:50 +0100 Message-ID: <503F463E.90505@cantab.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Dan Magenheimer Cc: George Dunlap , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 29/08/12 21:53, Dan Magenheimer wrote: > > Maybe it is time to move to match the well-known highly-greased > Linux kernel release process? This would include, for example, a short > window for new functionality and a xen-next for pre-window shaking > out and merging (of new functionality) and testing. As has > been pointed out, xen-unstable is, well, unstable for far too long. > > It may not be necessary to aggressively match Linus' 8-9 week release > cycle or weekly rcN releases, but the core process is known to > work very well, is reasonably well documented, and will be familiar > to many in the open source community. I think such a system only works if you have a short release cycle. If the only time to merge new features is two weeks in every 6/9 months then that is just far too long and is not very contributor-friendly. Xen doesn't have the number of contributors or changes that make a Linux kernel style process necessary. David