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: <77cbd79b-ebe3-37b0-7bff-55052d575376@apache.org>
References: <CA+RK=_D77_9q_+F7voKxWAGYs6-L_bmbOFEwFetUzz0uWkZH+g@mail.gmail.com>
 <77cbd79b-ebe3-37b0-7bff-55052d575376@apache.org>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Mon, 4 Dec 2017 20:52:03 -0800
Message-ID: <CANZa=GtcxD-Te+C9c_EhFf72fs5CHqvWdokPLrswbpssAoEoXQ@mail.gmail.com>
Subject: Re: branch-1 policy for builds against Hadoop 3.0.0
To: hbase-dev <dev@hbase.apache.org>
Content-Type: multipart/alternative; boundary="f403045cf718ced104055f909965"
archived-at: Tue, 05 Dec 2017 04:52:30 -0000

--f403045cf718ced104055f909965
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 4, 2017 at 3:30 PM, Josh Elser <elserj@apache.org> wrote:

> +1 not release blockers
>
> This stems from this line of thinking:
>
> * Hadoop does not dictate HBase's release schedule (except in extenuating
> circumstances)
> * HBase can't ensure compatibility against something that does not yet
> exist


Agreed.

On 12/4/17 3:43 PM, Andrew Purtell wrote:
>
>> Does anyone view compilation problems against Hadoop 3.0.0 in branch-1 a=
s
>> a
>> release blocker? See HBASE-19421.
>>
>> In my view
>> =E2=80=8B, use of Hadoop 3 with branch-1 HBase is not something we are g=
oing to
>> recommend for production use for some time, and Hadoop 3.0.0 is not even
>> GA
>> yet. (I know it may be close.) Therefore, builds that work with it are
>> nice
>> to have, but not essential. Compilation problems found for e.g. 1.4.0 ca=
n
>> be fixed for subsequent release 1.4.1.
>>
>> =E2=80=8BPlease speak up if you disagree.  Let's discuss this before we =
have a RC
>> vote where it may come up.
>>
>> --
>> Best regards,
>> Andrew
>>
>> Words like orphans lost among the crosstalk, meaning torn from truth's
>> decrepit hands
>>     - A23, Crosstalk
>>
>>

--f403045cf718ced104055f909965--