Hi Akira, Thank you for starting interesting topic. +1 on the idea of More Maintenance Releases for old branches. It would be good if this activity is more coupled with Apache Yetus for users.
BTW, I don't know one of committers, who is not PMC, can be a release manager. Does anyone know about this? It's described in detail as follows: http://hadoop.apache.org/bylaws#Decision+Making > Release Manager > A Release Manager (RM) is a committer who volunteers to produce a Release > Candidate according to HowToRelease. > > Project Management Committee > Deciding what is distributed as products of the Apache Hadoop project. In > particular all releases must be approved by the PMC Thanks, - Tsuyoshi On Mon, Jun 22, 2015 at 6:43 PM, Akira AJISAKA <ajisa...@oss.nttdata.co.jp> wrote: > Hi everyone, > > In Hadoop Summit, I joined HDFS BoF and heard from Jason Lowe that Apache > Hadoop developers at Yahoo!, Twitter, and other non-distributors work very > hard to maintenance Hadoop by cherry-picking patches to their own branches. > > I want to share the work with the community. If we can cherry-pick bug fix > patches and have more maintenance releases, it'd be very happy not only for > users but also for developers who work very hard for stabilizing their own > branches. > > To have more maintenance releases, I propose two changes: > > * Major/Minor/Trivial bug fixes can be cherry-picked > * (Roughly) Monthly maintenance release > > I would like to start the work from branch-2.6. If the change will be > accepted by the community, I'm willing to work for the maintenance, as a > release manager. > > Best regards, > Akira
