Thanks for initiating the discussion, Akira. I've given similar thoughts on the possible EOL of Hadoop branch-3.0 line. IMHO, I'd love to see HDFS-13596 <https://issues.apache.org/jira/browse/HDFS-13596> fixed to make it possible to rolling upgrade from Hadoop 2 to Hadoop 3.0, and then roll another maint. release before we declare EOL.
But in all seriousness, with my Cloudera hat on, CDH will soon rebase onto branch-3.1 so it's unlikely Cloudera can sponsor another 3.0 maint release. With my Apache hat on, Apache is an all-volunteer organization and we all act individually, but I am just being realistic that there would not be much motivation to roll another release in the future. Thoughts? On Fri, May 17, 2019 at 8:31 AM Akira Ajisaka <aajis...@apache.org> wrote: > Hi folks, > > In branch-3.0, it is almost a year since 3.0.3 was released. Is there > any committer who wants to be a release manager of 3.0.4? > > If there are no users running Apache Hadoop 3.0.x in production, I'm > thinking we can stop maintaining branch-3.0. Please let me know there > are any users running Apache Hadoop 3.0.x. > > Any thoughts? > > -Akira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org > For additional commands, e-mail: common-dev-h...@hadoop.apache.org > >
