Why not just have the discussion here? It seems integral to the matter of having more maintenance releases on those versions.
On Wed, Jul 15, 2015 at 11:39 AM, Karthik Kambatla <ka...@cloudera.com> wrote: > I believe there was general consensus to do more maintenance releases, as > witnessed in the other thread. > > There have been discussions on what should go into 2.x.1, 2.x.2, etc., but > I don't think we have a clear proposal. It would be nice to put that > together, so committers know where all to commit patches to. Otherwise, > release managers will have to look through branch-2 and pull in the fixes. > Either approach is fine by me, but would be nice to start a [DISCUSS] > thread on how to go about this. > > Any takers? > > On Wed, Jul 15, 2015 at 8:57 AM, Sangjin Lee <sjl...@gmail.com> wrote: > > > Strong +1 for having a 2.6.1 release. I understand Vinod has been trying > to > > get that effort going but it's been stalled a little bit. It would be > good > > to rekindle that effort. > > > > Companies with big hadoop 2.x deployments (including mine) have always > > tried to stabilize a 2.x release by testing/collecting/researching > critical > > issues on the release. Each would come up with its own set of fixes to > > backport. We would also communicate it via offline channels. During the > > hadoop summit, we thought it would be great if we all came together and > > create a public stability/bugfix release on top of 2.x (2.6.1 for 2.6 for > > example) with all the critical issues fixed. > > > > Thanks, > > Sangjin > > > > > > On Tue, Jul 14, 2015 at 10:42 PM, Tsuyoshi Ozawa <oz...@apache.org> > wrote: > > > > > Thank you for the notification. Trying to back port bug fixes. > > > > > > - Tsuyoshi > > > > > > On Wed, Jul 15, 2015 at 3:45 AM, Sean Busbey <bus...@cloudera.com> > > wrote: > > > > Hi Hadoopers! > > > > > > > > Over in HBase we've been discussing the impact of our dependencies on > > our > > > > downstream users. As our most fundamental dependency, Hadoop plays a > > big > > > > role in the operational cost of running an HBase instance. > > > > > > > > Currently the HBase 1.y release line supports Hadoop 2.4, 2.5, and > > > 2.6[1]. > > > > We don't drop Hadoop minor release lines in minor releases so we are > > > > unlikely remove anything from this set until HBase 2.0, probably at > the > > > end > > > > of 2015 / start of 2016 (and currently we plan to continue supporting > > at > > > > least 2.4 for HBase 2.0 [2]). Lately we've been discussing updating > our > > > > shipped binaries to Hadoop 2.6, following some stability testing by > > part > > > of > > > > our community[3]. Unfortunately, 2.6.0 in particular has a couple of > > bugs > > > > that could destroy HBase clusters should users decide to turn on HDFS > > > > encryption[4]. Our installation instructions tell folks to replace > > these > > > > jars with the version of Hadoop they are actually running, but not > all > > > > users follow those instructions so we want to minimize the pain for > > them. > > > > > > > > Regular maintenance releases are key to keeping operational burdens > low > > > for > > > > our downstream users; we don't want them to be forced to choose > between > > > > living with broken systems and stomaching the risk of upgrades across > > > > minor/major version numbers. Looking back over the three > aforementioned > > > > Hadoop versions, 2.6 hasn't had a patch release since 2.6.0 came out > in > > > Nov > > > > 2014, when 2.5 had its last patch release as well. Hadoop 2.4 looks > to > > > be a > > > > year without a release[5]. On our discussion of shipping Hadoop 2.6 > > > > binaries, one of your PMC members mentioned that with continued work > on > > > the > > > > 2.7 line y'all weren't planning any additional releases of the > earlier > > > > minor versions[6]. > > > > > > > > The HBase community requests that Hadoop pick up making bug-fix-only > > > patch > > > > releases again on a regular schedule[7]. Preferably on the 2.6 line > and > > > > preferably monthly. We realize that given the time gap since 2.6.0 it > > > will > > > > likely take a big to get 2.6.1 together, but after that it should > take > > > much > > > > less effort to continue. > > > > > > > > [1]: http://hbase.apache.org/book.html#hadoop > > > > [2]: http://s.apache.org/ReP > > > > [3]: HBASE-13339 > > > > [4]: HADOOP-11674 and HADOOP-11710 > > > > [5]: http://hadoop.apache.org/releases.html > > > > [6]: http://s.apache.org/MTY > > > > [7]: http://s.apache.org/ViP > > > > > > > > -- > > > > Sean > > > > > > > > > -- > Karthik Kambatla > Software Engineer, Cloudera Inc. > -------------------------------------------- > http://five.sentenc.es > -- Sean
