Could we please also include [1] in the release scope? The motivation is that we added some configuration just before the release, but now we realize that it should not be made a part of the public config. If we allow it to be included in the release, we'll have a confusing config for at least 1 release (and spans between releases are pretty long). The patch for [1] is trivial and there don't seem to be any concurrent changes in the affected code, so cherry picking it should be straightforward.
[1] https://issues.apache.org/jira/browse/IGNITE-26685 пн, 13 окт. 2025 г. в 01:27, Mirza Aliev <[email protected]>: > > Hello, Evgeniy! > > Could you please cherry-pick changes from this release blocker? [1] > > [1] https://issues.apache.org/jira/browse/IGNITE-26479 > > ср, 8 окт. 2025 г. в 15:59, zstan <[email protected]>: > > > Guys, as it was previously discussed - there will be a scope freeze. > > I plan to cut a branch in near time. > > > > A bit release-blocker issues are still not ready [1] i believe they will > > be complete closer to code freeze and will be cherry-picked into release > > branch. > > > > Also no performance\license violation issues have been found. > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.1.0 > > > > > +1 > > > > > > Thanks for taking this, Evgeniy. > > > > > >> Still not completed wiki page with different issue filters is available > > >> through [2], plz actualize who considers responsible for this. > > > > > > Please clarify - do you need help with this? > > > > > > On Thu, Sep 18, 2025 at 6:44 PM zstan <[email protected]> wrote: > > >> > > >> Dear Ignite Community! > > >> > > >> > > >> I suggest starting Apache Ignite 3.1.0 release activities. > > >> > > >> It's been almost seven months since our last release (10 Feb 2025) and > > >> there are about 1341 new commits (since > > 2c8d5142a02f6d609826cdec42e418) > > >> in > > >> main. I think it is a good time to > > >> start the discussion for 3.1.0. > > >> > > >> Existing issues which must be completed before code freeze [1] most of > > >> them relate to compatibility > > >> > > >> Still not completed wiki page with different issue filters is available > > >> through [2], plz actualize who considers responsible for this. > > >> > > >> Are there any other must have items that we want to include in the > > >> release? > > >> > > >> In comparison with 3.0.0: > > >> - More than 940 issues resolved [2] > > >> - Fixed b-tree corruptions > > >> - Metastorage compaction > > >> - Sql\kv performance improvements > > >> etc. > > >> > > >> > > >> I would like to be the release manager. Proposed timeline: > > >> > > >> > > >> Scope Freeze: October 20, 2025 > > >> > > >> Code Freeze: October 27, 2025 > > >> > > >> Voting Date: October 31, 2025 > > >> > > >> Release Date: November 06, 2025 > > >> > > >> > > >> > > >> WDYT? > > >> > > >> > > >> [1] > > >> https://issues.apache.org/jira/browse/IGNITE-26457 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-26095 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-26092 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-26110 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-26100 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-25311 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-25715 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-25685 > > >> > > >> https://issues.apache.org/jira/browse/IGNITE-25306 > > >> > > >> [2] > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.1.0 > > >> > > >> -- > > >> > > >> Best wishes, > > >> > > >> Evgeniy Stanilovskiy > > > > > > -- > > Using Opera's mail client: http://www.opera.com/mail/ > >
