Nikita, Thank you for starting this thread. +1 for these dates, but I think it's better to start the code freeze date when the Calcite engine will be actually merged to the master branch.
On Tue, 8 Feb 2022 at 13:10, Nikita Amelchev <namelc...@apache.org> wrote: > > Dear Ignite Community! > > I suggest starting Apache Ignite 2.13 release activities. > > There is a plan to merge the new Calcite SQL engine. [1] I think that > 2.13 is a good candidate for it. > > Moreover, we've accumulated a hundred resolved [2] issues with new > features and bug fixes which are waiting for their release date. For > example, > > BinaryArray introduced, > Read Repair strategies implemented, > CPP Thin: asynchronous network events handling, > NUMA-aware allocator for data regions > etc. > > I want to propose myself to be the release manager of the planning release. > > I propose the following timeline: > > Scope Freeze: February 21, 2022 > Code Freeze: March 7, 2022 > Voting Date: March 21, 2022 > Release Date: March 28, 2022 > > WDYT? > > [1] https://issues.apache.org/jira/browse/IGNITE-15436 > [2] > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority > > -- > Best wishes, > Amelchev Nikita
