Return-Path: 
 <hdfs-dev-return-6197-apmail-hadoop-hdfs-dev-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-hdfs-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id E0B7391FD
	for <apmail-hadoop-hdfs-dev-archive@minotaur.apache.org>;
 Wed, 28 Mar 2012 19:25:23 +0000 (UTC)
Received: (qmail 30390 invoked by uid 500); 28 Mar 2012 19:25:20 -0000
Delivered-To: apmail-hadoop-hdfs-dev-archive@hadoop.apache.org
Received: (qmail 30234 invoked by uid 500); 28 Mar 2012 19:25:20 -0000
Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:hdfs-dev-help@hadoop.apache.org>
List-Unsubscribe: <mailto:hdfs-dev-unsubscribe@hadoop.apache.org>
List-Post: <mailto:hdfs-dev@hadoop.apache.org>
List-Id: <hdfs-dev.hadoop.apache.org>
Reply-To: hdfs-dev@hadoop.apache.org
Delivered-To: mailing list hdfs-dev@hadoop.apache.org
Received: (qmail 30207 invoked by uid 99); 28 Mar 2012 19:25:20 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2012 19:25:20 +0000
Received: from localhost (HELO mail-bk0-f48.google.com) (127.0.0.1)
  (smtp-auth username omalley, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Wed, 28 Mar 2012 19:25:20 +0000
Received: by bkcji17 with SMTP id ji17so1934683bkc.35
        for <multiple recipients>; Wed, 28 Mar 2012 12:25:18 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.102.173 with SMTP id fp13mr24148874lab.38.1332962718069;
 Wed, 28 Mar 2012 12:25:18 -0700 (PDT)
Received: by 10.112.38.72 with HTTP; Wed, 28 Mar 2012 12:25:17 -0700 (PDT)
In-Reply-To: 
 <CADY20s7ZXOkZge8ecTO-h1K7z1jDKeBjuDTeGF9M8z4VMDvRfQ@mail.gmail.com>
References: <C2180ED3-51B8-407C-96BA-6A59E37E39B4@hortonworks.com>
	<8EB84C43-6949-4715-A77D-1B6F5EC3913A@hortonworks.com>
	<94AFEFD4-DEC8-4750-A1C6-CE4268E333B4@hortonworks.com>
	<CA+4052nMGB-b+dqMs=vFRw0X1z8s34WzFaZN-P3aP5YFxePUBA@mail.gmail.com>
	<4CA90D06-4BBE-499E-98ED-F8A2B9236793@hortonworks.com>
	<CADY20s4mLKa5xrcgmQPA-DOyUptQ=Fch85cE2VGfTNePqSk61A@mail.gmail.com>
	<CA+4052mzKsqXhFVLChGKUVH=Fn3qLccz9-0nJMGw4KDRM4UpqQ@mail.gmail.com>
	<CADY20s7ZXOkZge8ecTO-h1K7z1jDKeBjuDTeGF9M8z4VMDvRfQ@mail.gmail.com>
Date: Wed, 28 Mar 2012 12:25:17 -0700
Message-ID: 
 <CAHfHakHndB=ruQ-e3cELJgZg0MvoD5-_u1QfZWrmPO1y==ZjBw@mail.gmail.com>
Subject: Re: [RESULT] - [VOTE] Rename hadoop branches post hadoop-1.x
From: "Owen O'Malley" <omalley@apache.org>
To: hdfs-dev@hadoop.apache.org
Cc: common-dev@hadoop.apache.org, mapreduce-dev@hadoop.apache.org
Content-Type: multipart/alternative; boundary=f46d040716c74f345104bc529100

--f46d040716c74f345104bc529100
Content-Type: text/plain; charset=UTF-8

I disagree. Trunk should become branch-3 once someone wants to start
stabilizing it. Arun is going to need the minor versions for when he adds
features.

X.Y.Z

Z = bug fixes
Y = minor release (compatible, adds features)
X = major release (incompatible)

So from branch-2 will come branch-2.0 with tags for 2.0.0, 2.0.1. New
features will go into branch-2, which will become branch-2.1, branch-2.2,
and so on.

-- Owen

--f46d040716c74f345104bc529100--