Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+4kjVtb_vJsNWhVFD1wve5ap9YQ=k-_FnLBsPqmcy07rtsyXw@mail.gmail.com>
References: 
 <CA+RK=_CwOBBokkNCHNn8=-SMgcmUT=KMLq5fWtf4_hBNbG+EKw@mail.gmail.com>
	<CA+4kjVtb_vJsNWhVFD1wve5ap9YQ=k-_FnLBsPqmcy07rtsyXw@mail.gmail.com>
Date: Wed, 29 Jan 2014 09:55:25 -0800
Message-ID: 
 <CA+RK=_Brc=Lv3d0wHRaY1+FE0BOw6Oo1gJ=qZrDwq7C146_PwA@mail.gmail.com>
Subject: Re: Tagging 0.98.0 RC1 tomorrow
From: Andrew Purtell <apurtell@apache.org>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary=047d7bb04c2639b93404f11fa588

--047d7bb04c2639b93404f11fa588
Content-Type: text/plain; charset=ISO-8859-1

Thanks, aware of that. Those status reports are spotty and for example
there's been no mention of these recent JIRA outages while they are
happening. I really can't complain about the availability of a volunteered
resource but it is worth an email in explanation why a delay.

On Wednesday, January 29, 2014, Steve Loughran <stevel@hortonworks.com>
wrote:

> there's a twitter a/c purely for Infrastrucure announcements: @infrabot
> which gives status on things like this...
>
>
> On 29 January 2014 01:54, Andrew Purtell <apurtell@apache.org<javascript:;>>
> wrote:
>
> > We seem to be experiencing another extended JIRA outage in the middle of
> > the workday in my timezone. As far as I can tell there is at least one
> > unresolved critical issue (HBASE-10436). Also, I have several commits I
> > can't finish because as of now I can't pull patches from JIRA to apply.
> > Hopefully we can wrap this all up, and I can tag RC1 and generate the
> > artifacts tomorrow.
> >
> > --
> > Best regards,
> >
> >    - Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
> --
> 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.
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

--047d7bb04c2639b93404f11fa588--