> - Distributed environment tests [2] (Nikolay Izhikov, Anton > Vinogradov, Ivan Daschinskiy) > Will all related issues be included in the 2.10? We're at the final preparations phase. Going to start the merge discussion soon.
On Wed, Nov 11, 2020 at 4:48 PM Alexey Zinoviev <zaleslaw....@gmail.com> wrote: > Yes, Model Export/Import for ML will be finished, now it's ready, but under > testing on my side. > > ср, 11 нояб. 2020 г. в 16:08, Nikolay Izhikov <nizhi...@apache.org>: > > > I suggest to include CDC feature to the 2.10 scope. > > > > > 11 нояб. 2020 г., в 16:06, Maxim Muzafarov <mmu...@apache.org> > > написал(а): > > > > > > Igniters, > > > > > > > > > Can you clarify the issue statuses according to the Apache Ignite > > > Roadmap [1] and the 2.10 Apache Ignite Release? Here are some major > > > issues which are expected to be included in 2.10 with the unknown > > > status: > > > > > > - Distributed environment tests [2] (Nikolay Izhikov, Anton > > > Vinogradov, Ivan Daschinskiy) > > > Will all related issues be included in the 2.10? > > > > > > - Native persistence defragmentation [6][7] (Anton Kalashnikov, Sergey > > Chugunov) > > > Are we on the last mile with this for 2.10? > > > > > > - Consistency-related improvements for atomic caches [3] (Alexey > > Scherbakov) > > > Do we have the JIRA issue? Will the issue be included in 2.10? > > > > > > - Tombstone objects during rebalancing [4] (Alexey Scherbakov) > > > The issue [4] is in progress state. Will it be finished prior to code > > freeze? > > > > > > - SQL runtime statistics (Konstantin Orlov) > > > Do we have an IEP for this or JIRA issue? > > > > > > - ML Model export/import [5] (Alexey Zinoviev) > > > - Will the issue be finished? > > > > > > > > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Roadmap > > > [2] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-56%3A+Distributed+environment+tests > > > [3] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-12+Make+ATOMIC+Caches+Consistent+Again > > > [4] https://issues.apache.org/jira/browse/IGNITE-11704 > > > [5] https://issues.apache.org/jira/browse/IGNITE-6642 > > > [6] https://issues.apache.org/jira/browse/IGNITE-13143 > > > [7] > > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation > > > > > > On Tue, 10 Nov 2020 at 15:58, Maxim Muzafarov <mmu...@apache.org> > wrote: > > >> > > >> Folks, > > >> > > >> I've created the release page on the Confluence. Feel free to mail in > > >> case of any errors. > > >> > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.10 > > >> > > >> On Fri, 6 Nov 2020 at 17:56, Maxim Muzafarov <mmu...@apache.org> > wrote: > > >>> > > >>> Igniters, > > >>> > > >>> > > >>> Let's finalize the discussion [1] about the next upcoming major > Apache > > >>> Ignite 2.10 release. The major improvements related to the proposed > > >>> release: > > >>> - Improvements for partition clearing related parts > > >>> - Add tracing of SQL queries. > > >>> - CPP: Implement Cluster API > > >>> - .NET: Thin client: Transactions > > >>> - .NET: Thin Client: Continuous Query > > >>> - Java Thin client Kubernetes discovery > > >>> > > >>> etc. > > >>> Total: 166 RESOLVED issues [2]. > > >>> > > >>> > > >>> Let's start the discussion about Time and Scope, and also I propose > > >>> myself as the release manager of the Apache Ignite 2.10. If you'd > like > > >>> to lead this release, please, let us know, I see no problems to chose > > >>> a better candidate. > > >>> > > >>> > > >>> Proposed release timeline: > > >>> > > >>> Scope Freeze: December 10, 2020 > > >>> Code Freeze: December 24, 2020 > > >>> Voting Date: January 18, 2021 > > >>> Release Date: January 25, 2021 > > >>> > > >>> > > >>> Proposed release scope: > > >>> [2] > > >>> > > >>> > > >>> WDYT? > > >>> > > >>> > > >>> [1] > > > http://apache-ignite-developers.2346864.n4.nabble.com/2-9-1-release-proposal-tp49769p49867.html > > >>> [2] > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.10%20and%20status%20in%20(Resolved%2C%20Closed)%20and%20resolution%20%3D%20Fixed%20order%20by%20priority%20 > > > > >
