It is actually an ASF infra bug; see
https://github.com/apache/infrastructure-puppet/pull/623
On Thu, Dec 14, 2017 at 8:33 AM, Jim Apple wrote:
> This might be PMC only. I pushed it. I'll update
> https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release
>
> On Tue,
This might be PMC only. I pushed it. I'll update
https://cwiki.apache.org/confluence/display/IMPALA/How+to+Release
On Tue, Dec 12, 2017 at 10:35 AM, Thomas Tauber-Marshall <
tmarsh...@cloudera.com> wrote:
> I don't appear to have the permission to create the branch:
>
> Total 0 (delta 0), reused
sgtm
On Mon, Dec 11, 2017 at 1:49 PM, Thomas Tauber-Marshall <
tmarsh...@cloudera.com> wrote:
> Now that the issues that were brought up here have gone in, I propose that
> we branch 2.11 at:
>
> commit b4cf5f2174b338c097e42d43c32b494a6e0b46c0
> Author: Thomas Tauber-Marshall
So now that https://issues.apache.org/jira/browse/IMPALA-6292 has gone in,
and with https://issues.apache.org/jira/browse/IMPALA-6286 in GVO, I think
the last currently known blocker is https://gerrit.cloudera.org/#/c/8802/.
Once that goes in I think we're good.
On Thu, Dec 7, 2017 at 5:07 PM Tim
Actually it looks like we have a new blocker that Taras filed:
https://issues.apache.org/jira/browse/IMPALA-6292
On Thu, Dec 7, 2017 at 10:03 AM, Tim Armstrong
wrote:
> I think that makes sense. We'll have to go through the fix versions of
> recent JIRAs and make sure
Would also be great to include IMPALA-6286 which is wrong-results bug with
runtime filters.
On Thu, Dec 7, 2017 at 10:50 AM, Thomas Tauber-Marshall <
tmarsh...@cloudera.com> wrote:
> On Thu, Dec 7, 2017 at 10:37 AM Jim Apple wrote:
>
> > I think it would be great to get a
It looks like https://issues.apache.org/jira/browse/IMPALA-5017 caused
https://issues.apache.org/jira/browse/IMPALA-6284, so maybe we should not
include IMPALA-5017 in the 2.11 release also.
On Thu, Dec 7, 2017 at 9:43 AM, Jim Apple wrote:
> I think it would be great to
I think it would be great to get a fix for
https://issues.apache.org/jira/browse/IMPALA-6285 in 2.11.0 if possible. It
apparently could create a large performance boost.
It's marked as a Blocker with affects version 2.11, but no target version.
There are a few other tickets like this:
+1
Thanks, Thomas!
On Thu, Nov 30, 2017 at 1:50 PM Michael Brown wrote:
> +1
>
> On Thu, Nov 30, 2017 at 12:46 PM, Thomas Tauber-Marshall <
> tmarsh...@cloudera.com> wrote:
>
> > Folks,
> >
> > It has been over 2 months since we released Apache Impala 2.10.0 and
> there
> >
+1
On Thu, Nov 30, 2017 at 12:46 PM, Thomas Tauber-Marshall <
tmarsh...@cloudera.com> wrote:
> Folks,
>
> It has been over 2 months since we released Apache Impala 2.10.0 and there
> have been new feature improvements and a good number of bug fixes checked
> in since then.
>
> I propose that we
+1
Thank you for stepping up, Thomas! It'll be great to have a new release so
close after our graduation.
On Thu, Nov 30, 2017 at 1:32 PM, Taras Bobrovytsky
wrote:
> +1
>
> I agree. This is a good time to release. Thanks for volunteering!
>
> On Thu, Nov 30, 2017 at 1:22
+1
Thanks for volunteering.
On Thu, Nov 30, 2017 at 1:02 PM, Jim Apple wrote:
> +1
>
> On Thu, Nov 30, 2017 at 12:46 PM, Thomas Tauber-Marshall <
> tmarsh...@cloudera.com> wrote:
>
> > Folks,
> >
> > It has been over 2 months since we released Apache Impala 2.10.0 and
>
+1
On Thu, Nov 30, 2017 at 12:46 PM, Thomas Tauber-Marshall <
tmarsh...@cloudera.com> wrote:
> Folks,
>
> It has been over 2 months since we released Apache Impala 2.10.0 and there
> have been new feature improvements and a good number of bug fixes checked
> in since then.
>
> I propose that we
Folks,
It has been over 2 months since we released Apache Impala 2.10.0 and there
have been new feature improvements and a good number of bug fixes checked
in since then.
I propose that we release 2.11.0 soon and I volunteer to be its release
manager. Please speak up and let the community know
14 matches
Mail list logo