Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Subject: Re: continuing releases on Apache Hadoop 2.6.x
MIME-Version: 1.0
From: Vinod Vavilapalli <vinodkv@hortonworks.com>
To: "common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
CC: "hdfs-dev@hadoop.apache.org" <hdfs-dev@hadoop.apache.org>,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"mapreduce-dev@hadoop.apache.org" <mapreduce-dev@hadoop.apache.org>
Thread-Topic: continuing releases on Apache Hadoop 2.6.x
Thread-Index: AQHRFaTp9NcPtMbgFk+bFIal2my0cp6JqOCA
Date: Mon, 2 Nov 2015 19:45:30 +0000
Message-ID: <72DE0DA1-0846-48BA-B5CB-7394CD2F77CE@hortonworks.com>
References: 
 <CADbBEnuKvw2tg7CgFzC1gcFpfH__yk67n6EQwHdHZjkst2T-1A@mail.gmail.com>
In-Reply-To: 
 <CADbBEnuKvw2tg7CgFzC1gcFpfH__yk67n6EQwHdHZjkst2T-1A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5643BF9E9C00AF4A8437A38A9626C055@exch080.serverpod.net>
Content-Transfer-Encoding: quoted-printable

Just to stress on the following, it is very important that any critical bug=
-fixes that we push into 2.8.0 or even trunk, we should consider them for 2=
.6.3 and 2.7.3 if it makes sense. This is the only way we can avoid extreme=
ly long release cycles like that of 2.6.1.

Also, to clarify a little, use Target-version if you want a discussion of t=
he backport, but if you do end up backporting patches after that, you shoul=
d set the fix-version to be 2.6.1.

Thanks
+Vinod


> On Nov 2, 2015, at 11:29 AM, Sangjin Lee <sjlee@apache.org> wrote:
>=20
> As you may have seen, 2.6.2 is out
> <http://markmail.org/thread/yw53xgz6wzpqnclt>. I have also retargeted all
> open issues that were targeted for 2.6.2 to 2.6.3.
>=20
> Continuing the discussion in the email thread here
> <http://markmail.org/thread/ofjlzurok223bzyi>, I'd like us to maintain th=
e
> cadence of monthly point releases in the 2.6.x line. It would be great if
> we can have 2.6.3 released before the year-end holidays.
>=20
> If you have any bugfixes and improvements that are targeted for 2.7.x (or
> 2.8) that you think are applicable to 2.6.x, please *set the target versi=
on
> to 2.6.3* and merge them to branch-2.6. Please use your judgment in terms
> of the applicability and quality of the changes so that we can ensure eac=
h
> point release is consistently better quality than the previous one. Thank=
s
> everyone!
>=20
> Regards,
> Sangjin