Re: Apache Ignite 2.18.0 RELEASE [Time, Scope, Manager]

[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
>