Return-Path: X-Original-To: apmail-mahout-dev-archive@www.apache.org Delivered-To: apmail-mahout-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26B4A17CD4 for ; Tue, 14 Apr 2015 07:14:49 +0000 (UTC) Received: (qmail 47677 invoked by uid 500); 14 Apr 2015 07:14:48 -0000 Delivered-To: apmail-mahout-dev-archive@mahout.apache.org Received: (qmail 47597 invoked by uid 500); 14 Apr 2015 07:14:48 -0000 Mailing-List: contact dev-help@mahout.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mahout.apache.org Delivered-To: mailing list dev@mahout.apache.org Received: (qmail 47586 invoked by uid 99); 14 Apr 2015 07:14:48 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Apr 2015 07:14:48 +0000 Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3693B1A0113 for ; Tue, 14 Apr 2015 07:14:47 +0000 (UTC) Received: by wizk4 with SMTP id k4so101290973wiz.1 for ; Tue, 14 Apr 2015 00:14:46 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.77.230 with SMTP id v6mr36669958wjw.25.1428995686246; Tue, 14 Apr 2015 00:14:46 -0700 (PDT) Received: by 10.27.127.84 with HTTP; Tue, 14 Apr 2015 00:14:46 -0700 (PDT) In-Reply-To: References: Date: Tue, 14 Apr 2015 03:14:46 -0400 Message-ID: Subject: Re: Next version From: Suneel Marthi To: mahout Content-Type: multipart/alternative; boundary=047d7bfd028c43bc080513a9fcc5 --047d7bfd028c43bc080513a9fcc5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Tue, Apr 14, 2015 at 3:11 AM, Ted Dunning wrote: > On Tue, Apr 14, 2015 at 8:49 AM, Stevo Slavi=C4=87 wr= ote: > > > I'm not sure but I doubt there's anything in Apache way of doing things= , > > that's preventing us from having both 0.10.1 and 0.11.0 releases planne= d > > and worked on in parallel with dedicated branches e.g. master for next > > major.minor/non-bug-fix release, and branches for bug fix supported > > versions like 0.10 or 0.10.x. One can create a 0.10.x branch from 0.10.= 0 > > release tag. Changes there have to be regularly merged to master. > > > > This is entirely up to the project from the Apache view point. > > (and speaking as a project member, it sounds like a good idea) > And projects like Flink do this today, having multiple revision branches in tandem. --047d7bfd028c43bc080513a9fcc5--