Thank you for clarification, Karthik. I'd also like to work on stable release management with community.
I'm thinking of speedy release against <next version - 1> branch for making community feedback faster (e.g. current next version is 2.8, so cherry-picking to 2.7 and releasing it are useful work for users). I know that code base of 2.7.1 is now freezing currently, I'd love to work from 2.7.2 release if possible. Cheers, - Tsuyoshi On Tue, Jun 23, 2015 at 5:02 AM, Colin P. McCabe <cmcc...@apache.org> wrote: > +1 for creating a maintenance release with a more rapid release > cadence and more effort put into stability backports. I think this > would really be great for the project. > > Colin > > On Mon, Jun 22, 2015 at 2:43 AM, 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
