Hi Everyone, I agree that it is time to release the new features. Since they also introduced a lot of breaking changes, this is a good opportunity to release them in a major version. I volunteer to be the release manager for Impala 5.0.0.
Currently, the following issues are tracked with "Target Version": "Impala 5.0.0": https://issues.apache.org/jira/issues?jql=project%20%3D%20IMPALA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20%22Target%20Version%22%20%3D%20%22Impala%205.0.0%22%20ORDER%20BY%20priority%20ASC If any critical fix or breaking change must be included in Impala 5, please add it to the list. I would like to propose a release candidate in 1-2 weeks. Please assess the documentation impact of your changes since Impala 4.5.0 and update the documentation if needed. Thank you, Noémi On Thu, Jan 22, 2026 at 3:23 PM Zoltán Borók-Nagy <[email protected]> wrote: > Hey Everyone, > > It's been a while since we released Impala 4.5.0. > > Since then lots of great improvements and features accumulated on the > master branch. It would be nice if we could release them in a new major > version: Impala 5. > > First, let's collect all the required items for the release, especially the > breaking changes. > Please, if you want any of your tickets to be included in Impala 5, set the > "Target Version" to "Impala 5.0.0" and "Priority" to "Blocker" or > "Critical". > > Currently we have these items: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IMPALA%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20%22Target%20Version%22%20%3D%20%22Impala%205.0.0%22%20ORDER%20BY%20priority%20ASC > > Please also let us know if you volunteer to be the release manager. > > Cheers, > Zoltan >
