Sorry that I was busy last week unfortunately. So the voting was delayed..
I finally posted it today.

For the release note, I'm writing a draft here:
https://docs.google.com/document/d/1Oee3VPIPJ90uOM5VStcNYt1qEH5-T6F61U5_GM4YHF0/edit?usp=sharing
This release has 700+ JIRAs. I try to write short bullet points and
ignore trivial JIRAs. However, due to my limitation, I may have missed some
work. So I wish every contributor can write down his/her remarkable work
there with some (optional) short description. Thanks!

BTW, some JIRAs are marked as fixed in 4.0.0 but actually should be 4.1.0.
Please use 4.1.0 as the fixed version in new JIRAs.

Thanks,
Quanlong

On Sun, Jul 4, 2021 at 6:27 AM Jim Apple <apa...@jbapple.com> wrote:

> What's the latest on this? Those two bugs are fixed now, thankfully.
>
> On Mon, Jun 21, 2021 at 12:28 AM Quanlong Huang <huangquanl...@gmail.com>
> wrote:
>
> > Hi all,
> >
> > I'm still working on starting a RC vote for Impala 4.0.0. It's delayed
> > unfortunately since we continually found brokers.
> >
> > One blocker is we found that some machines don't support AVX2 which will
> be
> > broken by the previous change in IMPALA-9690. We finally added a new
> > flag enable_legacy_avx_support to support machines that only support AVX
> > but not AVX2. Thank Joe McDonnell for working on this!
> >
> > Another blocker is a correctness bug:
> > https://issues.apache.org/jira/browse/IMPALA-10755
> > Aman Sinha is currently working on it. Thank Aman!
> >
> > There is also a bug fix that I'd like to take in 4.0.0:
> > https://gerrit.cloudera.org/c/17604/ (IMPALA-9763). Hopefully, after
> these
> > two issues are resolved, we can start the RC vote.
> >
> > On the other hand, I'm thinking about how to improve the readability of
> our
> > release notes. Previously we just group all the JIRAs into different
> types.
> > But this release has >700 JIRAs. It'd be better to have something like
> Kudu
> > does: https://kudu.apache.org/docs/release_notes.html
> > This would require lots of work. I'm going to create a google doc to
> > consolidate the major changes and invite contributors to edit it
> together.
> > Please let me know if you have any suggestions.
> >
> > Thanks,
> > Quanlong
> >
>

Reply via email to