Hi Nikita, Is it possible to add the following ticket to the scope of the release as well? https://issues.apache.org/jira/browse/IGNITE-21032 GitHub issue: https://github.com/apache/ignite/issues/11045
Thanks, S. пн, 4 дек. 2023 г. в 21:13, Nikita Amelchev <namelc...@apache.org>: > Hello, Igniters. > > I had a private conversation with Nikolay Izhikov and Maksim Timonin. > I propose to include the realtime CDC back into the 2.16 scope [1]. > And also a couple of important tickets related to the cache dumps > [2-4]. > > They need an extra week of time to merge it. > > Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-17700 > [2] https://issues.apache.org/jira/browse/IGNITE-21013 > [3] https://issues.apache.org/jira/browse/IGNITE-20890 > [4] https://issues.apache.org/jira/browse/IGNITE-20614 > > пн, 27 нояб. 2023 г. в 17:18, Nikita Amelchev <namelc...@apache.org>: > > > > Hello, Igniters. > > > > The release branch has been stabilized. I'm waiting for load tests. > > > > The RC will be prepared in the coming days. > > > > пн, 20 нояб. 2023 г. в 22:28, Nikita Amelchev <namelc...@apache.org>: > > > > > > Hello, Igniters. > > > > > > I'm announcing a code freeze for the 2.16 release. Only blockers are > > > accepted to the release since this moment. > > > > > > пн, 13 нояб. 2023 г. в 19:13, Nikita Amelchev <namelc...@apache.org>: > > > > > > > > Hello, Igniters. > > > > > > > > I suggest moving the code freeze date to +1 week. > > > > > > > > We have several bug fixes ready to be merged [1], for example: > > > > > > > > IGNITE-19239 Checkpoint read lock acquisition timeouts during > snapshot restore > > > > IGNITE-20816 In-memory server node is crashed by > > > > TcpIgniteClient.putAllConflict() if cache objects transformation > > > > applied > > > > > > > > Updated dates: > > > > > > > > Code Freeze: November 20, 2023 > > > > Voting Date: November 27, 2023 > > > > Release Date: December 4, 2023 > > > > > > > > [1] > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority > > > > > > > > пн, 6 нояб. 2023 г. в 12:36, Nikita Amelchev <namelc...@apache.org>: > > > > > > > > > > Hi, > > > > > > > > > > Yes, they are marked with the 2.16 fix version. According to the > > > > > release process they will be cherry-picked to the release branch if > > > > > merged before code freeze. > > > > > > > > > > Documentation issues can be cherry-picked regardless of these > dates. > > > > > > > > > > пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>: > > > > > > > > > > > > Hi, > > > > > > > > > > > > Can the following PR be included in the scope of 2.16.0 version? > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-10268 > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-18038 > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-18572 > > > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-19436 > > > > > > > > > > > > > > > > > > 在 2023/11/6 16:21, Nikita Amelchev 写道: > > > > > > > Igniters, > > > > > > > > > > > > > > I have cut the release branch: 'ignite-2.16'. Please, > cherry-pick new > > > > > > > issues if needed. > > > > > > > > > > > > > > The 2.16 scope is frozen. Unresolved not-blocking issues will > be moved > > > > > > > on the code freeze stage. > > > > > > > > > > > > > > Code freeze is planned for November 13, 2023. Please, feel > free to > > > > > > > write if some issues are critical to be in the 2.16. > > > > > > > > > > > > > > ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev< > namelc...@apache.org>: > > > > > > >> Hello Igniters, > > > > > > >> > > > > > > >> I have created the 2.16 release page [1]. > > > > > > >> > > > > > > >> Also, I propose to cut the release branch on the scope freeze > day > > > > > > >> (November 6, 2023). > > > > > > >> > > > > > > >> [1] > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16 > > > > > > >> > > > > > > >> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov< > dpav...@apache.org>: > > > > > > >>> +1, fully support Nikita to be RM > > > > > > >>> > > > > > > >>> > > > > > > >>> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn< > ptupit...@apache.org>: > > > > > > >>> > > > > > > >>>> Sounds good, new JDK support seems to be in demand. > > > > > > >>>> > > > > > > >>>> On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov< > a...@apache.org> wrote: > > > > > > >>>> > > > > > > >>>>> +1 > > > > > > >>>>> > > > > > > >>>>> On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev< > namelc...@apache.org> > > > > > > >>>>> wrote: > > > > > > >>>>> > > > > > > >>>>>> Dear Ignite Community! > > > > > > >>>>>> > > > > > > >>>>>> I suggest starting Apache Ignite 2.16 release activities. > > > > > > >>>>>> > > > > > > >>>>>> We've accumulated a hundred resolved [1] issues with new > features and > > > > > > >>>>>> bug fixes which are waiting for their release date. For > example: > > > > > > >>>>>> > > > > > > >>>>>> Calcite engine: added hints, became more stable, covered > with > > > > > > >>>> diagnostic > > > > > > >>>>>> tools; > > > > > > >>>>>> Cluster Management API (IEP-81); > > > > > > >>>>>> Realtime CDC (IEP-104, ready to be merged); > > > > > > >>>>>> Fixes to support JDK 14-21; > > > > > > >>>>>> Several critical issues; > > > > > > >>>>>> etc. > > > > > > >>>>>> > > > > > > >>>>>> I want to propose myself to be the release manager of the > planning > > > > > > >>>>> release. > > > > > > >>>>>> I propose the following timeline: > > > > > > >>>>>> > > > > > > >>>>>> Scope Freeze: November 6, 2023 > > > > > > >>>>>> Code Freeze: November 13, 2022 > > > > > > >>>>>> Voting Date: November 20, 2022 > > > > > > >>>>>> Release Date: November 27, 2022 > > > > > > >>>>>> > > > > > > >>>>>> WDYT? > > > > > > >>>>>> > > > > > > >>>>>> [1] > > > > > > >>>>>> > > > > > > >>>> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%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, > > > > > > >>>>>> Amelchev Nikita > > > > > > >>>>>> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> Best wishes, > > > > > > >> Amelchev Nikita > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best wishes, > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > -- > > > > Best wishes, > > > > Amelchev Nikita > > > > > > > > > > > > -- > > > Best wishes, > > > Amelchev Nikita > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > > > > -- > Best wishes, > Amelchev Nikita >
