Mailing-List: contact dev-help@falcon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@falcon.apache.org
Subject: [DISCUSS] : Apache Falcon minor release schedule
MIME-Version: 1.0
From: Balu Vellanki Bala <bvellanki@hortonworks.com>
To: "dev@falcon.apache.org" <dev@falcon.apache.org>
Thread-Topic: [DISCUSS] : Apache Falcon minor release schedule 
Thread-Index: AQHRkDOcto0WWSrTC0yjMwRTZvaDhQ==
Date: Wed, 6 Apr 2016 18:39:11 +0000
Message-ID: <D32AA5DE.30611%bvellanki@hortonworks.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.175.27.10]
x-source-routing-agent: Processed
Content-Type: multipart/alternative;
	boundary="_000_D32AA5DE30611bvellankihortonworkscom_"

--_000_D32AA5DE30611bvellankihortonworkscom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello Team,

We had a discussion on the scope and schedule of Apache Falcon minor releas=
es during the Falcon bi-weekly meeting. There were two approaches suggested=
. I request you to provide your feedback/opinion on what is the preferred w=
ay.

Approach 1 : Minor release should be feature based.
In this approach, the release manager will coordinate with the Falcon commu=
nity and come up with an short wish-list of features that should go into ne=
xt release. The list should be achievable in the timelines proposed. Once t=
he list is decided upon, the release will happen only after the features ar=
e complete (including full testing).  The advantage is that minor releases =
will be feature complete and stable. Community will spend less time on debu=
gging incomplete features.  The disadvantage is that the release timeline b=
ecomes unpredictable due to unforeseen feature delays.

Approach 2 : Minor release should be time bound.
In this approach, minor releases will be done on a regular time interval pr=
oposed to be once a month. Every month, if we have a single complete featur=
e committed to Falcon, a new branch will be cut and a minor release will be=
 made. Incomplete features can go into the release, but they will not be ad=
vertised. The advantage is that falcon will have faster and predictable rel=
ease cycles. The disadvantage is that there could be incomplete features go=
ing into Falcon, leading to customers trying out and struggling with these =
features.

Thank you
Balu Vellanki

--_000_D32AA5DE30611bvellankihortonworkscom_--