You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by zstan <zs...@apache.org> on 2026/01/19 12:36:10 UTC
Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Dear Ignite Community!
I suggest starting Apache Ignite 2.18.0 release activities.
It's been almost eleven months since our last release (14 Feb 2025) and
there are a lot of new commits [1] (since
c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good time
to
start the discussion for 2.18.0.
List of fixed issues [2] which are waiting for their release date. For
example:
https://issues.apache.org/jira/browse/IGNITE-24130 Ability to configure
persitence folder for DataRegion
https://issues.apache.org/jira/browse/IGNITE-24777 Performance statistics:
wrong number of SQL query executions
https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins number
to commute in planning
https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
Numerous IEP-119 related issues
https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
HeavyQueriesTracker
.. and so on
Are there any other must have items that we want to include in the release?
I would like to be the release manager. Proposed timeline:
Scope Freeze: January 30, 2026
Code Freeze: February 16, 2026
Voting Date: February 23, 2026
Release Date: March 02, 2026
[1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
c257a369d84b1ccfde7242664143e4d43fa --count
[2]
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
--
Best wishes,
Stanilovskiy Evgeniy
Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by zstan <zs...@apache.org>.
Hello, Igniters.
I'm announcing a code freeze for the 2.18 release. All important for
release issues have been resolved. Only blockers are accepted since this
moment. The release branch has been
cut off (ignite-2.18).
--
Best wishes,
Evgeniy Stanilovskiy
>
> Dear Ignite Community!
>
>
> I suggest starting Apache Ignite 2.18.0 release activities.
>
> It's been almost eleven months since our last release (14 Feb 2025) and
> there are a lot of new commits [1] (since
> c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good
> time to
> start the discussion for 2.18.0.
>
> List of fixed issues [2] which are waiting for their release date. For
> example:
>
> https://issues.apache.org/jira/browse/IGNITE-24130 Ability to configure
> persitence folder for DataRegion
> https://issues.apache.org/jira/browse/IGNITE-24777 Performance
> statistics: wrong number of SQL query executions
> https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
> number to commute in planning
> https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
> Numerous IEP-119 related issues
> https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
> HeavyQueriesTracker
>
> .. and so on
>
>
> Are there any other must have items that we want to include in the
> release?
>
>
> I would like to be the release manager. Proposed timeline:
>
>
> Scope Freeze: January 30, 2026
>
> Code Freeze: February 16, 2026
>
> Voting Date: February 23, 2026
>
> Release Date: March 02, 2026
>
> [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
> c257a369d84b1ccfde7242664143e4d43fa --count
>
> [2]
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
>
Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by Mirza Aliev <al...@gmail.com>.
+1, thank you for starting the release process!
пн, 19 янв. 2026 г. в 16:54, Pavel Tupitsyn <pt...@apache.org>:
> +1, thank you Evgeniy
>
> On Mon, Jan 19, 2026 at 2:52 PM Dmitriy Pavlov <dp...@apache.org> wrote:
> >
> > Igniters,
> >
> > ++1 from my side.
> >
> > Evgeniy, thank you for kicking off the discussion on Apache Ignite
> 2.18.0!
> > I fully support starting the release and your candidacy as Release
> Manager.
> >
> > The list of issues looks good, and I think it’s better to release as is.
> > Does anyone in the community see any must-have items missing before the
> > Scope Freeze?
> >
> > Looking forward to a smooth and successful 2.18.0 release!
> >
> > Best regards,
> > Dmitriy Pavlov
> >
> > пн, 19 янв. 2026 г. в 15:40, zstan <zs...@apache.org>:
> >
> > >
> > > Dear Ignite Community!
> > >
> > >
> > > I suggest starting Apache Ignite 2.18.0 release activities.
> > >
> > > It's been almost eleven months since our last release (14 Feb 2025) and
> > > there are a lot of new commits [1] (since
> > > c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good
> time
> > > to
> > > start the discussion for 2.18.0.
> > >
> > > List of fixed issues [2] which are waiting for their release date. For
> > > example:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-24130 Ability to
> configure
> > > persitence folder for DataRegion
> > > https://issues.apache.org/jira/browse/IGNITE-24777 Performance
> > > statistics:
> > > wrong number of SQL query executions
> > > https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
> > > number
> > > to commute in planning
> > >
> > >
> https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
> > >
> > > Numerous IEP-119 related issues
> > > https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
> > > HeavyQueriesTracker
> > >
> > > .. and so on
> > >
> > >
> > > Are there any other must have items that we want to include in the
> release?
> > >
> > >
> > > I would like to be the release manager. Proposed timeline:
> > >
> > >
> > > Scope Freeze: January 30, 2026
> > >
> > > Code Freeze: February 16, 2026
> > >
> > > Voting Date: February 23, 2026
> > >
> > > Release Date: March 02, 2026
> > >
> > > [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
> > > c257a369d84b1ccfde7242664143e4d43fa --count
> > >
> > > [2]
> > >
> > >
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > >
> > >
> > > --
> > > Best wishes,
> > > Stanilovskiy Evgeniy
> > >
>
Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
+1, thank you Evgeniy
On Mon, Jan 19, 2026 at 2:52 PM Dmitriy Pavlov <dp...@apache.org> wrote:
>
> Igniters,
>
> ++1 from my side.
>
> Evgeniy, thank you for kicking off the discussion on Apache Ignite 2.18.0!
> I fully support starting the release and your candidacy as Release Manager.
>
> The list of issues looks good, and I think it’s better to release as is.
> Does anyone in the community see any must-have items missing before the
> Scope Freeze?
>
> Looking forward to a smooth and successful 2.18.0 release!
>
> Best regards,
> Dmitriy Pavlov
>
> пн, 19 янв. 2026 г. в 15:40, zstan <zs...@apache.org>:
>
> >
> > Dear Ignite Community!
> >
> >
> > I suggest starting Apache Ignite 2.18.0 release activities.
> >
> > It's been almost eleven months since our last release (14 Feb 2025) and
> > there are a lot of new commits [1] (since
> > c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good time
> > to
> > start the discussion for 2.18.0.
> >
> > List of fixed issues [2] which are waiting for their release date. For
> > example:
> >
> > https://issues.apache.org/jira/browse/IGNITE-24130 Ability to configure
> > persitence folder for DataRegion
> > https://issues.apache.org/jira/browse/IGNITE-24777 Performance
> > statistics:
> > wrong number of SQL query executions
> > https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
> > number
> > to commute in planning
> >
> > https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
> >
> > Numerous IEP-119 related issues
> > https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
> > HeavyQueriesTracker
> >
> > .. and so on
> >
> >
> > Are there any other must have items that we want to include in the release?
> >
> >
> > I would like to be the release manager. Proposed timeline:
> >
> >
> > Scope Freeze: January 30, 2026
> >
> > Code Freeze: February 16, 2026
> >
> > Voting Date: February 23, 2026
> >
> > Release Date: March 02, 2026
> >
> > [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
> > c257a369d84b1ccfde7242664143e4d43fa --count
> >
> > [2]
> >
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> >
> >
> > --
> > Best wishes,
> > Stanilovskiy Evgeniy
> >
Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by Dmitriy Pavlov <dp...@apache.org>.
Igniters,
++1 from my side.
Evgeniy, thank you for kicking off the discussion on Apache Ignite 2.18.0!
I fully support starting the release and your candidacy as Release Manager.
The list of issues looks good, and I think it’s better to release as is.
Does anyone in the community see any must-have items missing before the
Scope Freeze?
Looking forward to a smooth and successful 2.18.0 release!
Best regards,
Dmitriy Pavlov
пн, 19 янв. 2026 г. в 15:40, zstan <zs...@apache.org>:
>
> Dear Ignite Community!
>
>
> I suggest starting Apache Ignite 2.18.0 release activities.
>
> It's been almost eleven months since our last release (14 Feb 2025) and
> there are a lot of new commits [1] (since
> c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good time
> to
> start the discussion for 2.18.0.
>
> List of fixed issues [2] which are waiting for their release date. For
> example:
>
> https://issues.apache.org/jira/browse/IGNITE-24130 Ability to configure
> persitence folder for DataRegion
> https://issues.apache.org/jira/browse/IGNITE-24777 Performance
> statistics:
> wrong number of SQL query executions
> https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
> number
> to commute in planning
>
> https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
>
> Numerous IEP-119 related issues
> https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
> HeavyQueriesTracker
>
> .. and so on
>
>
> Are there any other must have items that we want to include in the release?
>
>
> I would like to be the release manager. Proposed timeline:
>
>
> Scope Freeze: January 30, 2026
>
> Code Freeze: February 16, 2026
>
> Voting Date: February 23, 2026
>
> Release Date: March 02, 2026
>
> [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
> c257a369d84b1ccfde7242664143e4d43fa --count
>
> [2]
>
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
>
>
> --
> Best wishes,
> Stanilovskiy Evgeniy
>
Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by zstan <zs...@apache.org>.
Pavel, honestly, thank you for this question !
We observe sufficient performance drop around this [1] issue.
But overall it`s not so obvious cause there are huge number of changes
still last release.
We do our best and seems we close to continue with release process.
[1] https://issues.apache.org/jira/browse/IGNITE-23856
> Dear Evgeniy, any update on the release date?
>
> Thanks,
> Pavel
>
> On Mon, Mar 2, 2026 at 7:01 PM zstan <zs...@apache.org> wrote:
>>
>> Dear Ignite Community!
>> Sorry, but i need to shift a bit release date, due to continued of some
>> performance tests.
>> I will announce a new date soon.
>>
>> Stay tuned.
>>
>> Evgeniy Stanilovskiy
>>
>> >
>> > Dear Ignite Community!
>> >
>> >
>> > I suggest starting Apache Ignite 2.18.0 release activities.
>> >
>> > It's been almost eleven months since our last release (14 Feb 2025)
>> and
>> > there are a lot of new commits [1] (since
>> > c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good
>> > time to
>> > start the discussion for 2.18.0.
>> >
>> > List of fixed issues [2] which are waiting for their release date. For
>> > example:
>> >
>> > https://issues.apache.org/jira/browse/IGNITE-24130 Ability to
>> configure
>> > persitence folder for DataRegion
>> > https://issues.apache.org/jira/browse/IGNITE-24777 Performance
>> > statistics: wrong number of SQL query executions
>> > https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
>> > number to commute in planning
>> >
>> https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
>> > Numerous IEP-119 related issues
>> > https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
>> > HeavyQueriesTracker
>> >
>> > .. and so on
>> >
>> >
>> > Are there any other must have items that we want to include in the
>> > release?
>> >
>> >
>> > I would like to be the release manager. Proposed timeline:
>> >
>> >
>> > Scope Freeze: January 30, 2026
>> >
>> > Code Freeze: February 16, 2026
>> >
>> > Voting Date: February 23, 2026
>> >
>> > Release Date: March 02, 2026
>> >
>> > [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
>> > c257a369d84b1ccfde7242664143e4d43fa --count
>> >
>> > [2]
>> >
>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
>> >
>> >
>>
>>
>> --
>> Using Opera's mail client: http://www.opera.com/mail/
--
Using Opera's mail client: http://www.opera.com/mail/
Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by Pavel Tupitsyn <pt...@apache.org>.
Dear Evgeniy, any update on the release date?
Thanks,
Pavel
On Mon, Mar 2, 2026 at 7:01 PM zstan <zs...@apache.org> wrote:
>
> Dear Ignite Community!
> Sorry, but i need to shift a bit release date, due to continued of some
> performance tests.
> I will announce a new date soon.
>
> Stay tuned.
>
> Evgeniy Stanilovskiy
>
> >
> > Dear Ignite Community!
> >
> >
> > I suggest starting Apache Ignite 2.18.0 release activities.
> >
> > It's been almost eleven months since our last release (14 Feb 2025) and
> > there are a lot of new commits [1] (since
> > c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good
> > time to
> > start the discussion for 2.18.0.
> >
> > List of fixed issues [2] which are waiting for their release date. For
> > example:
> >
> > https://issues.apache.org/jira/browse/IGNITE-24130 Ability to configure
> > persitence folder for DataRegion
> > https://issues.apache.org/jira/browse/IGNITE-24777 Performance
> > statistics: wrong number of SQL query executions
> > https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
> > number to commute in planning
> > https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
> > Numerous IEP-119 related issues
> > https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
> > HeavyQueriesTracker
> >
> > .. and so on
> >
> >
> > Are there any other must have items that we want to include in the
> > release?
> >
> >
> > I would like to be the release manager. Proposed timeline:
> >
> >
> > Scope Freeze: January 30, 2026
> >
> > Code Freeze: February 16, 2026
> >
> > Voting Date: February 23, 2026
> >
> > Release Date: March 02, 2026
> >
> > [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
> > c257a369d84b1ccfde7242664143e4d43fa --count
> >
> > [2]
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> >
> >
>
>
> --
> Using Opera's mail client: http://www.opera.com/mail/
Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]
Posted by zstan <zs...@apache.org>.
Dear Ignite Community!
Sorry, but i need to shift a bit release date, due to continued of some
performance tests.
I will announce a new date soon.
Stay tuned.
Evgeniy Stanilovskiy
>
> Dear Ignite Community!
>
>
> I suggest starting Apache Ignite 2.18.0 release activities.
>
> It's been almost eleven months since our last release (14 Feb 2025) and
> there are a lot of new commits [1] (since
> c257a369d84b1ccfde7242664143e4d43fa) in master. I think it is a good
> time to
> start the discussion for 2.18.0.
>
> List of fixed issues [2] which are waiting for their release date. For
> example:
>
> https://issues.apache.org/jira/browse/IGNITE-24130 Ability to configure
> persitence folder for DataRegion
> https://issues.apache.org/jira/browse/IGNITE-24777 Performance
> statistics: wrong number of SQL query executions
> https://issues.apache.org/jira/browse/IGNITE-24884 SQL. Limit joins
> number to commute in planning
> https://issues.apache.org/jira/browse/IGNITE-25680?jql=labels%20%3D%20IEP-119
> Numerous IEP-119 related issues
> https://issues.apache.org/jira/browse/IGNITE-25449 Fix Memory Leak in
> HeavyQueriesTracker
>
> .. and so on
>
>
> Are there any other must have items that we want to include in the
> release?
>
>
> I would like to be the release manager. Proposed timeline:
>
>
> Scope Freeze: January 30, 2026
>
> Code Freeze: February 16, 2026
>
> Voting Date: February 23, 2026
>
> Release Date: March 02, 2026
>
> [1] git rev-list 8acb7deb7535a52e6aa2e6d89fa166
> c257a369d84b1ccfde7242664143e4d43fa --count
>
> [2]
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(2.18))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
>
>
--
Using Opera's mail client: http://www.opera.com/mail/