This is more than about bugs. In the past, incompatibilities are what bit us more than bugs. If we find such bad incompatibilities in 2.7.0 release, calling it "not-stable yet" (or "alpha" or whatever) leaves us with the ability to fix any incompatibilities in a final "public-ready" release.
Thanks +Vinod On Apr 20, 2015, at 2:03 PM, Karthik Kambatla <ka...@cloudera.com<mailto:ka...@cloudera.com>> wrote: How about we skip this all entirely? If the HDFS issues reported aren't going to render the cluster unusable, we could just release 2.7.0 and mark it current/latest. We can move the stable tag to 2.7.1 or 2.7.2 whichever version deserves the bit.
