You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@impala.apache.org by Jim Apple <jb...@cloudera.com> on 2017/01/04 22:09:02 UTC
[DISCUSS] Release 2.8.0 soon?
This is not a [VOTE] thread. Everyone is encourage to participate.
I am volunteering to be a release manager for 2.8.0. I am provisionally testing
https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=4fa9270e647b9c097295dcc13d97136cca3139ad;hb=4fa9270e647b9c097295dcc13d97136cca3139ad
to branch from.
Are there any objections to releasing 2.8.0 soon? Keep in mind this is
not your last chance to speak - there will be at least two votes one
for PPMC releasing and one for IPMC releasing. See
https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Marcel Kornacker <ma...@cloudera.com>.
Also +1 for doing a 2.8.0 release.
On Wed, Jan 4, 2017 at 2:29 PM, Henry Robinson <he...@apache.org> wrote:
> +1 to releasing 2.8.0 - it's been a long time since 2.7.0 and a lot has
> been done.
>
> I'd also like to release 2.7.1 in the near future, and will try to find
> time to be the RM for that.
>
> On 4 January 2017 at 14:15, Jim Apple <jb...@cloudera.com> wrote:
>
>> Oh, and a specific topic for discussion:
>>
>> Should we include the docs in the source tarball? My feeling is yes,
>> but they are not really cleaned up yet, and so contain a lot of
>> Cloudera-specific info.
>>
>> Pros of including the docs in the tarball: Users get a docs tarball
>> from which they can build the hundreds of pages of usable
>> documentation.
>>
>> Cons: 1. Confused users about who runs the project. (Correct answer:
>> Apache Impala PPMC. Confused answer: Cloudera), 2. Possible failed
>> IPMC release vote that slows down the release.
>>
>
> 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.
>
>
>
>>
>> On Wed, Jan 4, 2017 at 2:09 PM, Jim Apple <jb...@cloudera.com> wrote:
>> > This is not a [VOTE] thread. Everyone is encourage to participate.
>> >
>> > I am volunteering to be a release manager for 2.8.0. I am provisionally
>> testing
>> >
>> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=
>> 4fa9270e647b9c097295dcc13d97136cca3139ad;hb=4fa9270e647b9c097295dcc13d9713
>> 6cca3139ad
>> >
>> > to branch from.
>> >
>> > Are there any objections to releasing 2.8.0 soon? Keep in mind this is
>> > not your last chance to speak - there will be at least two votes one
>> > for PPMC releasing and one for IPMC releasing. See
>> >
>> > https://cwiki.apache.org/confluence/display/IMPALA/
>> DRAFT%3A+How+to+Release
>>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by John Russell <jr...@cloudera.com>.
I’ll investigate the “every page” aspect. There is some boilerplate content in shared/ImpalaVariables.xml, in the <foreign> tag, that’s displayed on every HTML page in the downstream docs. That may rely on some tooling that’s not part of the core DITA Open Toolkit, or there might be a build-time switch that would make it work for the Apache build.
John
> On Jan 4, 2017, at 7:17 PM, Jim Apple <jb...@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?
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Tim Armstrong <ta...@cloudera.com>.
Here are the open blockers:
https://issues.cloudera.org/issues/?jql=project%20%3D%20IMPALA%20AND%20status%20in%20(Open%2C%20Reopened)%20AND%20priority%20%3D%20Blocker
There seem to be a bunch of other blockers, but I think the remaining ones
are all pre-existing issues, testing, or flaky tests that we can move out
to the next release.
On Thu, Jan 5, 2017 at 11:55 AM, Tim Armstrong <ta...@cloudera.com>
wrote:
> +1 for reverting it. It doesn't add any new functionality so I don't see
> the value in including it in the release.
>
> On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com>
> wrote:
>
>> +1 for reverting it. It's a recent, major change and it's still settling.
>>
>> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
>>
>> > Yes, that is in the branch:
>> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
>> > git;a=shortlog;h=refs/heads/branch-2.8.0
>> >
>> > Here are some options:
>> >
>> > 1. Burn this branch, make a new one without the commit but with
>> > everything else. Pros: no blocker. Cons: cherry-picking hell.
>> >
>> > 2. Take the branch before this commit. Pros: no blocker. Cons: missing
>> > other bug fixes
>> >
>> > 3. Wait for a fix. Pros: no blocker. Cons: delay
>> >
>> > 4. Commit to master a git revert of that patch. Pros: no blocker;
>> > fixes blocker on branch and master. Cons: add noise to commit history
>> >
>> > I'd like to git revert it. What do you all think?
>> >
>> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <tarmstrong@cloudera.com
>> >
>> > wrote:
>> > > This one:
>> > >
>> > > http://gerrit.cloudera.org:8080/4418
>> > >
>> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>> > >
>> > >> Which commit introduced it?
>> > >>
>> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
>> tarmstrong@cloudera.com
>> > >
>> > >> wrote:
>> > >> > I think we have some open blockers for 2.8. Or at least one that
>> was
>> > >> > introduced in a recent commit .
>> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to
>> > include a
>> > >> fix
>> > >> > or just exclude the commit that introduced it?
>> > >> >
>> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>> > >> >
>> > >> > I have now also tested the docs build:
>> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
>> > >> >
>> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com>
>> > wrote:
>> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
>> > 6cca3139ad)
>> > >> >> 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 <jb...@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?
>> > >>
>> >
>>
>>
>>
>> --
>> Henry Robinson
>> Software Engineer
>> Cloudera
>> 415-994-6679
>>
>
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
Since this patch is failing in pre-merge testing at the moment, I'm
planning on going with option #2: take the branch before the big
commit that caused this bug in the first place. It has passed our
usual pre-commit testing, so I'm going to clobber branch-2.8.0 in
order to rewind it to
https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=commit;h=48792eb92f010af99246a14d5a3570dfed662dfd
Keep in mind that if you want to test this with LZO, you need
https://github.com/cloudera/impala-lzo/commit/41aeaa4ca1451419f52e8cffbd4264436a6f3db9
On Thu, Jan 5, 2017 at 2:14 PM, Tim Armstrong <ta...@cloudera.com> wrote:
> In any case, here's the CR for the bugfix
> https://gerrit.cloudera.org/#/c/5615/
>
> On Thu, Jan 5, 2017 at 1:10 PM, Henry Robinson <he...@cloudera.com> wrote:
>
>> Same deal with me - I don't support reverting in master.
>>
>> I think it's fine to branch from before that change and cherry pick what
>> you can. As the RM you decide what goes in and what doesn't - if the cherry
>> picks are too hard, it's fine to skip them. Patching is also fine.
>>
>> On Thu, Jan 5, 2017 at 12:12 PM Tim Armstrong <ta...@cloudera.com>
>> wrote:
>>
>> > Oh yes my reading comprehension was bad. I don't think it makes sense to
>> >
>> > revert it on master - I thought you meant reverting it on the branch.
>> >
>> >
>> >
>> > The bugfix is small and straightforward - maybe it's easiest if I just
>> put
>> >
>> > that together and put it up for review.
>> >
>> >
>> >
>> > - Tim
>> >
>> >
>> >
>> > On Thu, Jan 5, 2017 at 12:02 PM, Jim Apple <jb...@cloudera.com> wrote:
>> >
>> >
>> >
>> > > Just to clarify: when I said reverting it, I meant reverting it in
>> >
>> > > master, too, then chery picking that change to the branch. I'd rather
>> >
>> > > keep the branch free from as many non-master commits as possible.
>> >
>> > >
>> >
>> > > On Thu, Jan 5, 2017 at 11:55 AM, Tim Armstrong <
>> tarmstrong@cloudera.com>
>> >
>> > > wrote:
>> >
>> > > > +1 for reverting it. It doesn't add any new functionality so I don't
>> > see
>> >
>> > > > the value in including it in the release.
>> >
>> > > >
>> >
>> > > > On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com>
>> >
>> > > wrote:
>> >
>> > > >
>> >
>> > > >> +1 for reverting it. It's a recent, major change and it's still
>> >
>> > > settling.
>> >
>> > > >>
>> >
>> > > >> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
>> >
>> > > >>
>> >
>> > > >> > Yes, that is in the branch:
>> >
>> > > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
>> >
>> > > >> > git;a=shortlog;h=refs/heads/branch-2.8.0
>> >
>> > > >> >
>> >
>> > > >> > Here are some options:
>> >
>> > > >> >
>> >
>> > > >> > 1. Burn this branch, make a new one without the commit but with
>> >
>> > > >> > everything else. Pros: no blocker. Cons: cherry-picking hell.
>> >
>> > > >> >
>> >
>> > > >> > 2. Take the branch before this commit. Pros: no blocker. Cons:
>> > missing
>> >
>> > > >> > other bug fixes
>> >
>> > > >> >
>> >
>> > > >> > 3. Wait for a fix. Pros: no blocker. Cons: delay
>> >
>> > > >> >
>> >
>> > > >> > 4. Commit to master a git revert of that patch. Pros: no blocker;
>> >
>> > > >> > fixes blocker on branch and master. Cons: add noise to commit
>> > history
>> >
>> > > >> >
>> >
>> > > >> > I'd like to git revert it. What do you all think?
>> >
>> > > >> >
>> >
>> > > >> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <
>> >
>> > > tarmstrong@cloudera.com>
>> >
>> > > >> > wrote:
>> >
>> > > >> > > This one:
>> >
>> > > >> > >
>> >
>> > > >> > > http://gerrit.cloudera.org:8080/4418
>> >
>> > > >> > >
>> >
>> > > >> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com>
>> wrote:
>> >
>> > > >> > >
>> >
>> > > >> > >> Which commit introduced it?
>> >
>> > > >> > >>
>> >
>> > > >> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
>> >
>> > > >> tarmstrong@cloudera.com
>> >
>> > > >> > >
>> >
>> > > >> > >> wrote:
>> >
>> > > >> > >> > I think we have some open blockers for 2.8. Or at least one
>> > that
>> >
>> > > was
>> >
>> > > >> > >> > introduced in a recent commit .
>> >
>> > > >> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan
>> to
>> >
>> > > >> > include a
>> >
>> > > >> > >> fix
>> >
>> > > >> > >> > or just exclude the commit that introduced it?
>> >
>> > > >> > >> >
>> >
>> > > >> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com>
>> > wrote:
>> >
>> > > >> > >> >
>> >
>> > > >> > >> > I have now also tested the docs build:
>> >
>> > > >> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/
>> 92/
>> >
>> > > >> > >> >
>> >
>> > > >> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <
>> > jbapple@cloudera.com>
>> >
>> > > >> > wrote:
>> >
>> > > >> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
>> >
>> > > >> > 6cca3139ad)
>> >
>> > > >> > >> >> 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?
>> >
>> > > >> > >>
>> >
>> > > >> >
>> >
>> > > >>
>> >
>> > > >>
>> >
>> > > >>
>> >
>> > > >> --
>> >
>> > > >> Henry Robinson
>> >
>> > > >> Software Engineer
>> >
>> > > >> Cloudera
>> >
>> > > >> 415-994-6679
>> >
>> > > >>
>> >
>> > >
>> >
>> >
>>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Tim Armstrong <ta...@cloudera.com>.
In any case, here's the CR for the bugfix
https://gerrit.cloudera.org/#/c/5615/
On Thu, Jan 5, 2017 at 1:10 PM, Henry Robinson <he...@cloudera.com> wrote:
> Same deal with me - I don't support reverting in master.
>
> I think it's fine to branch from before that change and cherry pick what
> you can. As the RM you decide what goes in and what doesn't - if the cherry
> picks are too hard, it's fine to skip them. Patching is also fine.
>
> On Thu, Jan 5, 2017 at 12:12 PM Tim Armstrong <ta...@cloudera.com>
> wrote:
>
> > Oh yes my reading comprehension was bad. I don't think it makes sense to
> >
> > revert it on master - I thought you meant reverting it on the branch.
> >
> >
> >
> > The bugfix is small and straightforward - maybe it's easiest if I just
> put
> >
> > that together and put it up for review.
> >
> >
> >
> > - Tim
> >
> >
> >
> > On Thu, Jan 5, 2017 at 12:02 PM, Jim Apple <jb...@cloudera.com> wrote:
> >
> >
> >
> > > Just to clarify: when I said reverting it, I meant reverting it in
> >
> > > master, too, then chery picking that change to the branch. I'd rather
> >
> > > keep the branch free from as many non-master commits as possible.
> >
> > >
> >
> > > On Thu, Jan 5, 2017 at 11:55 AM, Tim Armstrong <
> tarmstrong@cloudera.com>
> >
> > > wrote:
> >
> > > > +1 for reverting it. It doesn't add any new functionality so I don't
> > see
> >
> > > > the value in including it in the release.
> >
> > > >
> >
> > > > On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com>
> >
> > > wrote:
> >
> > > >
> >
> > > >> +1 for reverting it. It's a recent, major change and it's still
> >
> > > settling.
> >
> > > >>
> >
> > > >> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
> >
> > > >>
> >
> > > >> > Yes, that is in the branch:
> >
> > > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> >
> > > >> > git;a=shortlog;h=refs/heads/branch-2.8.0
> >
> > > >> >
> >
> > > >> > Here are some options:
> >
> > > >> >
> >
> > > >> > 1. Burn this branch, make a new one without the commit but with
> >
> > > >> > everything else. Pros: no blocker. Cons: cherry-picking hell.
> >
> > > >> >
> >
> > > >> > 2. Take the branch before this commit. Pros: no blocker. Cons:
> > missing
> >
> > > >> > other bug fixes
> >
> > > >> >
> >
> > > >> > 3. Wait for a fix. Pros: no blocker. Cons: delay
> >
> > > >> >
> >
> > > >> > 4. Commit to master a git revert of that patch. Pros: no blocker;
> >
> > > >> > fixes blocker on branch and master. Cons: add noise to commit
> > history
> >
> > > >> >
> >
> > > >> > I'd like to git revert it. What do you all think?
> >
> > > >> >
> >
> > > >> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <
> >
> > > tarmstrong@cloudera.com>
> >
> > > >> > wrote:
> >
> > > >> > > This one:
> >
> > > >> > >
> >
> > > >> > > http://gerrit.cloudera.org:8080/4418
> >
> > > >> > >
> >
> > > >> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com>
> wrote:
> >
> > > >> > >
> >
> > > >> > >> Which commit introduced it?
> >
> > > >> > >>
> >
> > > >> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
> >
> > > >> tarmstrong@cloudera.com
> >
> > > >> > >
> >
> > > >> > >> wrote:
> >
> > > >> > >> > I think we have some open blockers for 2.8. Or at least one
> > that
> >
> > > was
> >
> > > >> > >> > introduced in a recent commit .
> >
> > > >> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan
> to
> >
> > > >> > include a
> >
> > > >> > >> fix
> >
> > > >> > >> > or just exclude the commit that introduced it?
> >
> > > >> > >> >
> >
> > > >> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com>
> > wrote:
> >
> > > >> > >> >
> >
> > > >> > >> > I have now also tested the docs build:
> >
> > > >> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/
> 92/
> >
> > > >> > >> >
> >
> > > >> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <
> > jbapple@cloudera.com>
> >
> > > >> > wrote:
> >
> > > >> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
> >
> > > >> > 6cca3139ad)
> >
> > > >> > >> >> 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?
> >
> > > >> > >>
> >
> > > >> >
> >
> > > >>
> >
> > > >>
> >
> > > >>
> >
> > > >> --
> >
> > > >> Henry Robinson
> >
> > > >> Software Engineer
> >
> > > >> Cloudera
> >
> > > >> 415-994-6679
> >
> > > >>
> >
> > >
> >
> >
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Henry Robinson <he...@cloudera.com>.
Same deal with me - I don't support reverting in master.
I think it's fine to branch from before that change and cherry pick what
you can. As the RM you decide what goes in and what doesn't - if the cherry
picks are too hard, it's fine to skip them. Patching is also fine.
On Thu, Jan 5, 2017 at 12:12 PM Tim Armstrong <ta...@cloudera.com>
wrote:
> Oh yes my reading comprehension was bad. I don't think it makes sense to
>
> revert it on master - I thought you meant reverting it on the branch.
>
>
>
> The bugfix is small and straightforward - maybe it's easiest if I just put
>
> that together and put it up for review.
>
>
>
> - Tim
>
>
>
> On Thu, Jan 5, 2017 at 12:02 PM, Jim Apple <jb...@cloudera.com> wrote:
>
>
>
> > Just to clarify: when I said reverting it, I meant reverting it in
>
> > master, too, then chery picking that change to the branch. I'd rather
>
> > keep the branch free from as many non-master commits as possible.
>
> >
>
> > On Thu, Jan 5, 2017 at 11:55 AM, Tim Armstrong <ta...@cloudera.com>
>
> > wrote:
>
> > > +1 for reverting it. It doesn't add any new functionality so I don't
> see
>
> > > the value in including it in the release.
>
> > >
>
> > > On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com>
>
> > wrote:
>
> > >
>
> > >> +1 for reverting it. It's a recent, major change and it's still
>
> > settling.
>
> > >>
>
> > >> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
>
> > >>
>
> > >> > Yes, that is in the branch:
>
> > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
>
> > >> > git;a=shortlog;h=refs/heads/branch-2.8.0
>
> > >> >
>
> > >> > Here are some options:
>
> > >> >
>
> > >> > 1. Burn this branch, make a new one without the commit but with
>
> > >> > everything else. Pros: no blocker. Cons: cherry-picking hell.
>
> > >> >
>
> > >> > 2. Take the branch before this commit. Pros: no blocker. Cons:
> missing
>
> > >> > other bug fixes
>
> > >> >
>
> > >> > 3. Wait for a fix. Pros: no blocker. Cons: delay
>
> > >> >
>
> > >> > 4. Commit to master a git revert of that patch. Pros: no blocker;
>
> > >> > fixes blocker on branch and master. Cons: add noise to commit
> history
>
> > >> >
>
> > >> > I'd like to git revert it. What do you all think?
>
> > >> >
>
> > >> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <
>
> > tarmstrong@cloudera.com>
>
> > >> > wrote:
>
> > >> > > This one:
>
> > >> > >
>
> > >> > > http://gerrit.cloudera.org:8080/4418
>
> > >> > >
>
> > >> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>
> > >> > >
>
> > >> > >> Which commit introduced it?
>
> > >> > >>
>
> > >> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
>
> > >> tarmstrong@cloudera.com
>
> > >> > >
>
> > >> > >> wrote:
>
> > >> > >> > I think we have some open blockers for 2.8. Or at least one
> that
>
> > was
>
> > >> > >> > introduced in a recent commit .
>
> > >> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to
>
> > >> > include a
>
> > >> > >> fix
>
> > >> > >> > or just exclude the commit that introduced it?
>
> > >> > >> >
>
> > >> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com>
> wrote:
>
> > >> > >> >
>
> > >> > >> > I have now also tested the docs build:
>
> > >> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
>
> > >> > >> >
>
> > >> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <
> jbapple@cloudera.com>
>
> > >> > wrote:
>
> > >> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
>
> > >> > 6cca3139ad)
>
> > >> > >> >> 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?
>
> > >> > >>
>
> > >> >
>
> > >>
>
> > >>
>
> > >>
>
> > >> --
>
> > >> Henry Robinson
>
> > >> Software Engineer
>
> > >> Cloudera
>
> > >> 415-994-6679
>
> > >>
>
> >
>
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Tim Armstrong <ta...@cloudera.com>.
Oh yes my reading comprehension was bad. I don't think it makes sense to
revert it on master - I thought you meant reverting it on the branch.
The bugfix is small and straightforward - maybe it's easiest if I just put
that together and put it up for review.
- Tim
On Thu, Jan 5, 2017 at 12:02 PM, Jim Apple <jb...@cloudera.com> wrote:
> Just to clarify: when I said reverting it, I meant reverting it in
> master, too, then chery picking that change to the branch. I'd rather
> keep the branch free from as many non-master commits as possible.
>
> On Thu, Jan 5, 2017 at 11:55 AM, Tim Armstrong <ta...@cloudera.com>
> wrote:
> > +1 for reverting it. It doesn't add any new functionality so I don't see
> > the value in including it in the release.
> >
> > On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com>
> wrote:
> >
> >> +1 for reverting it. It's a recent, major change and it's still
> settling.
> >>
> >> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
> >>
> >> > Yes, that is in the branch:
> >> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> >> > git;a=shortlog;h=refs/heads/branch-2.8.0
> >> >
> >> > Here are some options:
> >> >
> >> > 1. Burn this branch, make a new one without the commit but with
> >> > everything else. Pros: no blocker. Cons: cherry-picking hell.
> >> >
> >> > 2. Take the branch before this commit. Pros: no blocker. Cons: missing
> >> > other bug fixes
> >> >
> >> > 3. Wait for a fix. Pros: no blocker. Cons: delay
> >> >
> >> > 4. Commit to master a git revert of that patch. Pros: no blocker;
> >> > fixes blocker on branch and master. Cons: add noise to commit history
> >> >
> >> > I'd like to git revert it. What do you all think?
> >> >
> >> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <
> tarmstrong@cloudera.com>
> >> > wrote:
> >> > > This one:
> >> > >
> >> > > http://gerrit.cloudera.org:8080/4418
> >> > >
> >> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> >> > >
> >> > >> Which commit introduced it?
> >> > >>
> >> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
> >> tarmstrong@cloudera.com
> >> > >
> >> > >> wrote:
> >> > >> > I think we have some open blockers for 2.8. Or at least one that
> was
> >> > >> > introduced in a recent commit .
> >> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to
> >> > include a
> >> > >> fix
> >> > >> > or just exclude the commit that introduced it?
> >> > >> >
> >> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> >> > >> >
> >> > >> > I have now also tested the docs build:
> >> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
> >> > >> >
> >> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com>
> >> > wrote:
> >> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
> >> > 6cca3139ad)
> >> > >> >> 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?
> >> > >>
> >> >
> >>
> >>
> >>
> >> --
> >> Henry Robinson
> >> Software Engineer
> >> Cloudera
> >> 415-994-6679
> >>
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
Just to clarify: when I said reverting it, I meant reverting it in
master, too, then chery picking that change to the branch. I'd rather
keep the branch free from as many non-master commits as possible.
On Thu, Jan 5, 2017 at 11:55 AM, Tim Armstrong <ta...@cloudera.com> wrote:
> +1 for reverting it. It doesn't add any new functionality so I don't see
> the value in including it in the release.
>
> On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com> wrote:
>
>> +1 for reverting it. It's a recent, major change and it's still settling.
>>
>> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
>>
>> > Yes, that is in the branch:
>> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
>> > git;a=shortlog;h=refs/heads/branch-2.8.0
>> >
>> > Here are some options:
>> >
>> > 1. Burn this branch, make a new one without the commit but with
>> > everything else. Pros: no blocker. Cons: cherry-picking hell.
>> >
>> > 2. Take the branch before this commit. Pros: no blocker. Cons: missing
>> > other bug fixes
>> >
>> > 3. Wait for a fix. Pros: no blocker. Cons: delay
>> >
>> > 4. Commit to master a git revert of that patch. Pros: no blocker;
>> > fixes blocker on branch and master. Cons: add noise to commit history
>> >
>> > I'd like to git revert it. What do you all think?
>> >
>> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <ta...@cloudera.com>
>> > wrote:
>> > > This one:
>> > >
>> > > http://gerrit.cloudera.org:8080/4418
>> > >
>> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>> > >
>> > >> Which commit introduced it?
>> > >>
>> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
>> tarmstrong@cloudera.com
>> > >
>> > >> wrote:
>> > >> > I think we have some open blockers for 2.8. Or at least one that was
>> > >> > introduced in a recent commit .
>> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to
>> > include a
>> > >> fix
>> > >> > or just exclude the commit that introduced it?
>> > >> >
>> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>> > >> >
>> > >> > I have now also tested the docs build:
>> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
>> > >> >
>> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com>
>> > wrote:
>> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
>> > 6cca3139ad)
>> > >> >> 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 <jb...@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?
>> > >>
>> >
>>
>>
>>
>> --
>> Henry Robinson
>> Software Engineer
>> Cloudera
>> 415-994-6679
>>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Tim Armstrong <ta...@cloudera.com>.
+1 for reverting it. It doesn't add any new functionality so I don't see
the value in including it in the release.
On Thu, Jan 5, 2017 at 10:58 AM, Henry Robinson <he...@cloudera.com> wrote:
> +1 for reverting it. It's a recent, major change and it's still settling.
>
> On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
>
> > Yes, that is in the branch:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> > git;a=shortlog;h=refs/heads/branch-2.8.0
> >
> > Here are some options:
> >
> > 1. Burn this branch, make a new one without the commit but with
> > everything else. Pros: no blocker. Cons: cherry-picking hell.
> >
> > 2. Take the branch before this commit. Pros: no blocker. Cons: missing
> > other bug fixes
> >
> > 3. Wait for a fix. Pros: no blocker. Cons: delay
> >
> > 4. Commit to master a git revert of that patch. Pros: no blocker;
> > fixes blocker on branch and master. Cons: add noise to commit history
> >
> > I'd like to git revert it. What do you all think?
> >
> > On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <ta...@cloudera.com>
> > wrote:
> > > This one:
> > >
> > > http://gerrit.cloudera.org:8080/4418
> > >
> > > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> > >
> > >> Which commit introduced it?
> > >>
> > >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <
> tarmstrong@cloudera.com
> > >
> > >> wrote:
> > >> > I think we have some open blockers for 2.8. Or at least one that was
> > >> > introduced in a recent commit .
> > >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to
> > include a
> > >> fix
> > >> > or just exclude the commit that introduced it?
> > >> >
> > >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> > >> >
> > >> > I have now also tested the docs build:
> > >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
> > >> >
> > >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com>
> > wrote:
> > >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
> > 6cca3139ad)
> > >> >> 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 <jb...@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?
> > >>
> >
>
>
>
> --
> Henry Robinson
> Software Engineer
> Cloudera
> 415-994-6679
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Henry Robinson <he...@cloudera.com>.
+1 for reverting it. It's a recent, major change and it's still settling.
On 5 January 2017 at 10:49, Jim Apple <jb...@cloudera.com> wrote:
> Yes, that is in the branch:
> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.
> git;a=shortlog;h=refs/heads/branch-2.8.0
>
> Here are some options:
>
> 1. Burn this branch, make a new one without the commit but with
> everything else. Pros: no blocker. Cons: cherry-picking hell.
>
> 2. Take the branch before this commit. Pros: no blocker. Cons: missing
> other bug fixes
>
> 3. Wait for a fix. Pros: no blocker. Cons: delay
>
> 4. Commit to master a git revert of that patch. Pros: no blocker;
> fixes blocker on branch and master. Cons: add noise to commit history
>
> I'd like to git revert it. What do you all think?
>
> On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <ta...@cloudera.com>
> wrote:
> > This one:
> >
> > http://gerrit.cloudera.org:8080/4418
> >
> > On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> >
> >> Which commit introduced it?
> >>
> >> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <tarmstrong@cloudera.com
> >
> >> wrote:
> >> > I think we have some open blockers for 2.8. Or at least one that was
> >> > introduced in a recent commit .
> >> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to
> include a
> >> fix
> >> > or just exclude the commit that introduced it?
> >> >
> >> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> >> >
> >> > I have now also tested the docs build:
> >> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
> >> >
> >> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com>
> wrote:
> >> >> I have now tested this hash (4fa9270e647b9c097295dcc13d9713
> 6cca3139ad)
> >> >> 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 <jb...@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?
> >>
>
--
Henry Robinson
Software Engineer
Cloudera
415-994-6679
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
Yes, that is in the branch:
https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=shortlog;h=refs/heads/branch-2.8.0
Here are some options:
1. Burn this branch, make a new one without the commit but with
everything else. Pros: no blocker. Cons: cherry-picking hell.
2. Take the branch before this commit. Pros: no blocker. Cons: missing
other bug fixes
3. Wait for a fix. Pros: no blocker. Cons: delay
4. Commit to master a git revert of that patch. Pros: no blocker;
fixes blocker on branch and master. Cons: add noise to commit history
I'd like to git revert it. What do you all think?
On Thu, Jan 5, 2017 at 10:39 AM, Tim Armstrong <ta...@cloudera.com> wrote:
> This one:
>
> http://gerrit.cloudera.org:8080/4418
>
> On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>
>> Which commit introduced it?
>>
>> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <ta...@cloudera.com>
>> wrote:
>> > I think we have some open blockers for 2.8. Or at least one that was
>> > introduced in a recent commit .
>> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to include a
>> fix
>> > or just exclude the commit that introduced it?
>> >
>> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>> >
>> > I have now also tested the docs build:
>> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
>> >
>> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com> wrote:
>> >> 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 <jb...@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?
>>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Tim Armstrong <ta...@cloudera.com>.
This one:
http://gerrit.cloudera.org:8080/4418
On 5 Jan 2017 10:15 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> Which commit introduced it?
>
> On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <ta...@cloudera.com>
> wrote:
> > I think we have some open blockers for 2.8. Or at least one that was
> > introduced in a recent commit .
> > https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to include a
> fix
> > or just exclude the commit that introduced it?
> >
> > On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
> >
> > I have now also tested the docs build:
> > http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
> >
> > On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com> wrote:
> >> 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 <jb...@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?
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
Which commit introduced it?
On Thu, Jan 5, 2017 at 10:12 AM, Tim Armstrong <ta...@cloudera.com> wrote:
> I think we have some open blockers for 2.8. Or at least one that was
> introduced in a recent commit .
> https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to include a fix
> or just exclude the commit that introduced it?
>
> On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
>
> I have now also tested the docs build:
> http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
>
> On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com> wrote:
>> 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 <jb...@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?
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Tim Armstrong <ta...@cloudera.com>.
I think we have some open blockers for 2.8. Or at least one that was
introduced in a recent commit .
https://issues.cloudera.org/browse/IMPALA-4707. Do we plan to include a fix
or just exclude the commit that introduced it?
On 5 Jan 2017 9:09 AM, "Jim Apple" <jb...@cloudera.com> wrote:
I have now also tested the docs build:
http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com> wrote:
> 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 <jb...@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?
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
I have now also tested the docs build:
http://jenkins.impala.io:8080/view/Utility/job/docs-build/92/
On Thu, Jan 5, 2017 at 8:28 AM, Jim Apple <jb...@cloudera.com> wrote:
> 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 <jb...@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?
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
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 <jb...@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?
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
> 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?
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Henry Robinson <he...@apache.org>.
+1 to releasing 2.8.0 - it's been a long time since 2.7.0 and a lot has
been done.
I'd also like to release 2.7.1 in the near future, and will try to find
time to be the RM for that.
On 4 January 2017 at 14:15, Jim Apple <jb...@cloudera.com> wrote:
> Oh, and a specific topic for discussion:
>
> Should we include the docs in the source tarball? My feeling is yes,
> but they are not really cleaned up yet, and so contain a lot of
> Cloudera-specific info.
>
> Pros of including the docs in the tarball: Users get a docs tarball
> from which they can build the hundreds of pages of usable
> documentation.
>
> Cons: 1. Confused users about who runs the project. (Correct answer:
> Apache Impala PPMC. Confused answer: Cloudera), 2. Possible failed
> IPMC release vote that slows down the release.
>
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.
>
> On Wed, Jan 4, 2017 at 2:09 PM, Jim Apple <jb...@cloudera.com> wrote:
> > This is not a [VOTE] thread. Everyone is encourage to participate.
> >
> > I am volunteering to be a release manager for 2.8.0. I am provisionally
> testing
> >
> > https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=
> 4fa9270e647b9c097295dcc13d97136cca3139ad;hb=4fa9270e647b9c097295dcc13d9713
> 6cca3139ad
> >
> > to branch from.
> >
> > Are there any objections to releasing 2.8.0 soon? Keep in mind this is
> > not your last chance to speak - there will be at least two votes one
> > for PPMC releasing and one for IPMC releasing. See
> >
> > https://cwiki.apache.org/confluence/display/IMPALA/
> DRAFT%3A+How+to+Release
>
Re: [DISCUSS] Release 2.8.0 soon?
Posted by Jim Apple <jb...@cloudera.com>.
Oh, and a specific topic for discussion:
Should we include the docs in the source tarball? My feeling is yes,
but they are not really cleaned up yet, and so contain a lot of
Cloudera-specific info.
Pros of including the docs in the tarball: Users get a docs tarball
from which they can build the hundreds of pages of usable
documentation.
Cons: 1. Confused users about who runs the project. (Correct answer:
Apache Impala PPMC. Confused answer: Cloudera), 2. Possible failed
IPMC release vote that slows down the release.
On Wed, Jan 4, 2017 at 2:09 PM, Jim Apple <jb...@cloudera.com> wrote:
> This is not a [VOTE] thread. Everyone is encourage to participate.
>
> I am volunteering to be a release manager for 2.8.0. I am provisionally testing
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-impala.git;a=tree;h=4fa9270e647b9c097295dcc13d97136cca3139ad;hb=4fa9270e647b9c097295dcc13d97136cca3139ad
>
> to branch from.
>
> Are there any objections to releasing 2.8.0 soon? Keep in mind this is
> not your last chance to speak - there will be at least two votes one
> for PPMC releasing and one for IPMC releasing. See
>
> https://cwiki.apache.org/confluence/display/IMPALA/DRAFT%3A+How+to+Release