Mailing-List: contact dev-help@impala.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@impala.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <CAC-pSX1nF2h-wm6W=dg2A+Ka3qmxgZ_HL-M7k6Jj=3-24UgVjg@mail.gmail.com>
References: <CAC-pSX3u+VBFXF_=oe51UfwvTVRSS2cH4weDVZeLvQJebLqr-g@mail.gmail.com>
 <CAC-pSX1vsJXm3d-qLeP2OpGHCwsPp5jQRFo+kNGU7SuQGbiQhQ@mail.gmail.com>
 <CADZba-SYA=L_VqmMY7nRJveVqS9UPDSERxKK0VVMd7ynBBHqHA@mail.gmail.com> <CAC-pSX1nF2h-wm6W=dg2A+Ka3qmxgZ_HL-M7k6Jj=3-24UgVjg@mail.gmail.com>
From: Jim Apple <jbapple@cloudera.com>
Date: Thu, 5 Jan 2017 08:28:57 -0800
Message-ID: <CAC-pSX2L0J8sh0XLQ75Ct8Go0nW9qG+Zs20fp5QDTa8jZz8VLw@mail.gmail.com>
Subject: Re: [DISCUSS] Release 2.8.0 soon?
To: "dev@impala" <dev@impala.incubator.apache.org>
Cc: John Russell <jrussell@cloudera.com>, Laurel Hale <laurel@cloudera.com>
Content-Type: text/plain; charset=UTF-8
archived-at: Thu, 05 Jan 2017 16:29:44 -0000

I have now tested this hash (4fa9270e647b9c097295dcc13d97136cca3139ad)
on public Jenkins:

http://jenkins.impala.io:8080/view/Utility/job/parallel-all-tests/130/
http://jenkins.impala.io:8080/view/Utility/job/ubuntu-14.04-from-scratch/434/
http://jenkins.impala.io:8080/view/Utility/job/ubuntu-14.04-from-scratch/435/
http://jenkins.impala.io:8080/view/Utility/job/ubuntu-14.04-from-scratch/436/

That covers RAT (the tool for checking copyright compliance), various
build options (including ninja, release, asan, shared libs), loading
the data from scratch and running all tests in core and in exhaustive,
clang-tidy, and the build we instruct IPMC release testers to run
(bin/bootstrap_build.sh).

I have also created a git branch:
https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=shortlog;h=refs/heads/branch-2.8.0

I am working on a commit to add a disclaimer to the docs
(https://gerrit.cloudera.org/#/c/5610/) and then I will upload a
release candidate tarball.

Please prepare yourself to vote. Instructions are here:

https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release#DRAFT:HowtoRelease-HowtoVoteonaReleaseCandidate

On Wed, Jan 4, 2017 at 7:17 PM, Jim Apple <jbapple@cloudera.com> wrote:
>> I'd figure out a way to add a big caveat to the docs. Maybe on the landing
>> page? Even better if there's a template we can add a caveat to that appears
>> on every page.
>
> I like this idea. I'll prepare a patch for the landing page.
>
> I don't think there is a simple way to do it on every page. John,
> Laurel, am I wrong abut that?