Hi Sangjin,
I'm thinking it's time for 2.6.5 release. Now there are 51 fixed issues
in 2.6.5 and the number is more than 2.6.4 (47).
> How long do we maintain this line? What would be a sensible EOL policy?
Ideally 5 years, because most of our customers in Japan are using Hadoop
cluster without upgrading for about 5 years. However, it's probably
impossible for us to achieve the long term maintenance in the community
because the maintenance cost is too high. Therefore, my answer is
"longer is better".
By the way, I'm thinking we can reduce the maintenance cost by selecting
which branch to maintenance for a long time. An example is Ubuntu LTS.
Ubuntu Server LTS is maintained for 5 years but the other releases are not.
Regards,
Akira
On 7/20/16 12:45, Sean Busbey wrote:
The HBase community would like more 2.6.z releases.
On Wed, Jul 20, 2016 at 2:00 PM, Ravi Prakash <ravihad...@gmail.com> wrote:
We for one are not using 2.6.*
On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee <sj...@apache.org> wrote:
It's been a while since we had a release on the 2.6.x line. Is it time to
get ready for a 2.6.5 release? Are folks using and relying on releases on
2.6.x? If there is enough interest, I could take that on. Let me know.
I also want to gauge the community's interest in maintaining the 2.6.x
line. How long do we maintain this line? What would be a sensible EOL
policy? Note that as the main code lines start diverging (java version,
features, etc.), the cost of maintaining multiple release lines does go up.
I'd love to hear your thoughts.
Regards,
Sangjin
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
