Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of jon@cloudera.com designates
 209.85.212.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAMUu0w8FU8JN-vA0AEfqFRXiJW51Gp3VVEYwQpBbzfP4J-YNZg@mail.gmail.com>
References: 
 <CAAha9a00BNunN-gC3yvewi-wVd_yrrXx4uA0deLuFq+dm+MN4g@mail.gmail.com>
 <CAHXxaiBRUzavHAHeDLxu4LA=X6C5VnqPrCM2gpJo7YCRwpyu+g@mail.gmail.com>
 <CAMUu0w8FU8JN-vA0AEfqFRXiJW51Gp3VVEYwQpBbzfP4J-YNZg@mail.gmail.com>
From: Jonathan Hsieh <jon@cloudera.com>
Date: Fri, 20 Dec 2013 12:42:49 -0800
Message-ID: 
 <CAAha9a02AXyDfqq+EgsFV4g1JUOiNCuO7EK2=5=+QYUqNTJomA@mail.gmail.com>
Subject: Re: ANNOUNCE: hbase-0.96.1.1 available for download.
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=bcaec51b9d177868db04edfd532f

--bcaec51b9d177868db04edfd532f
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

When cutting the release, I made a the mistake of commiting to the 0.96.1
tag and then creating the 0.96.1.1 svn tag when when I was satisfied.  I
ended up deleting the messed up 0.96.1 tag and creating a new 0.96.1 that
is essentially equivalent to the one stack created on monday.

To get the 0.96.1.1 branch, you need to do a
'git fetch --all --tags ....'
to get the branches tagged in svn.

I think the attempt to restore the proper 0.96.1 wasn't liked by svn-git.

In any case, I'll be updating the instructions for properly tagging these
point releases.

Jon.


On Fri, Dec 20, 2013 at 11:40 AM, Enis S=F6ztutar <enis@apache.org> wrote:

> 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 t=
he
> right thing while picking up this tag.
> Should we have created a branch named 0.96.1, do the commits there, and d=
o
> the tag from there. Just trying to understand for future processes.
>
> Enis
>
>
> On Fri, Dec 20, 2013 at 11:35 AM, Sergey Shelukhin
> <sergey@hortonworks.com>wrote:
>
> > Interesting question - is there code representing this version somewher=
e
> 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 wor=
ks
> > alright wrt not including 0.96.2 patches).
> >
> >
> > On Thu, Dec 19, 2013 at 1:29 PM, Jonathan Hsieh <jon@cloudera.com>
> 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 hba=
se
> > > 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 a=
n
> > api
> > > compatibility problem introduced between 0.96.0 ad 0.96.1.  We will b=
e
> > > 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
> > > // jon@cloudera.com
> > >
> >
> > --
> > CONFIDENTIALITY NOTICE
> > NOTICE: This message is intended for the use of the individual or entit=
y
> to
> > which it is addressed and may contain information that is confidential,
> > privileged and exempt from disclosure under applicable law. If the read=
er
> > 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.
> >
>


--=20
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// jon@cloudera.com

--bcaec51b9d177868db04edfd532f--