falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Balu Vellanki Bala <bvella...@hortonworks.com>
Subject [DISCUSS] : Apache Falcon minor release schedule
Date Wed, 06 Apr 2016 18:39:11 GMT
Hello Team,

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

Approach 1 : Minor release should be feature based.
In this approach, the release manager will coordinate with the Falcon community and come up
with an short wish-list of features that should go into next release. The list should be achievable
in the timelines proposed. Once the list is decided upon, the release will happen only after
the features are complete (including full testing).  The advantage is that minor releases
will be feature complete and stable. Community will spend less time on debugging incomplete
features.  The disadvantage is that the release timeline becomes 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 proposed to be once
a month. Every month, if we have a single complete feature 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 advertised. The advantage is that falcon will have faster and predictable
release cycles. The disadvantage is that there could be incomplete features going into Falcon,
leading to customers trying out and struggling with these features.

Thank you
Balu Vellanki

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message