I was also a bit puzzled by this. It seems that John did use the tag 0.96.1 as a branch to put the commits on top to create another tag. I think in svn there is no difference between tags and branches (just convention), but I though we should not have changed the tag (0.96.1). Did not check whether svn-git integration did the right thing while picking up this tag. Should we have created a branch named 0.96.1, do the commits there, and do the tag from there. Just trying to understand for future processes.
Enis On Fri, Dec 20, 2013 at 11:35 AM, Sergey Shelukhin <[email protected]>wrote: > Interesting question - is there code representing this version somewhere in > git, without the intervening commits between when 0.96.1 happened and this > patch happened? Or is it only svn tag (and I am just assuming that works > alright wrt not including 0.96.2 patches). > > > On Thu, Dec 19, 2013 at 1:29 PM, Jonathan Hsieh <[email protected]> wrote: > > > The HBase Team is pleased to announce the immediate release of HBase > > 0.96.1.1. > > > > You should be able to download it from you favorite apache mirrors[1]. > It > > has also been pushed to apache's maven repository. > > > > Note that hbase-0.96.1.1 comes in two flavors; a build that includes and > > runs on hadoop-1.x and another for hadoop-2.x. You must chose the hbase > > that suits your hadoop context. > > > > Upgrades from 0.92.x/0.94.x can requires shutdown and then an upgrade > > procedure [2]. Upgrades from 0.96.x can be done via rolling upgrade > > without downtime. > > > > This was a quick fix release with only 1 bug fix [3] that addressed an > api > > compatibility problem introduced between 0.96.0 ad 0.96.1. We will be > > removing 0.96.1. > > > > Thanks! > > Your HBase Team > > > > [1] http://www.apache.org/dyn/closer.cgi/hbase/ > > [2] http://hbase.apache.org/book.html#upgrade0.96 > > [3] http://goo.gl/q4S94X > > > > > > -- > > // Jonathan Hsieh (shay) > > // Software Engineer, Cloudera > > // [email protected] > > > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
