Guys, We are in code-freeze phase now. I've moved almost all non-blocker unresolved tickets from 2.9 to the next release. If you think that some ticket is a blocker and should be included into 2.9 release, please write a note in this thread.
There are some tickets with "blocker" priority targeted to 2.9, some of them in "open" state and still unassigned, and I'm not sure we need all of these tickets in 2.9: IGNITE-13006 [1] (Apache Ignite spring libs upgrade from version 4x to spring 5.2 version or later) - Is it really a blocker for 2.9 release? If yes, can somebody help with resolving this ticket? IGNITE-11942 [2] (IGFS and Hadoop Accelerator Discontinuation) - ticket in "Patch available" state. There is a thread on dev-list related to this ticket ([6]), but as far as I understand we still don't have consensus about version for this patch (2.9, 2.10, 3.0). IGNITE-12489 [3] (Error during purges by expiration: Unknown page type) - perhaps issue is already resolved by some related tickets, there is still no reproducer, no additional details and no work in progress. I propose to move this ticket to the next release. IGNITE-12911 [4] (B+Tree Corrupted exception when using a key extracted from a BinaryObject value object --- and SQL enabled) - ticket in "Patch available" state, but there is no activity since May 2020. Anton Kalashnikov, Ilya Kasnacheev, do we have any updates on this ticket? Is it still in progress? IGNITE-12553 [5] ([IEP-35] public Java metric API) - since the new metrics framework is already released in 2.8 and it's still marked with @IgniteExperemental annotation, I think this ticket is not a blocker. I propose to change the ticket priority and move it to the next release. [1]: https://issues.apache.org/jira/browse/IGNITE-13006 [2]: https://issues.apache.org/jira/browse/IGNITE-11942 [3]: https://issues.apache.org/jira/browse/IGNITE-12489 [4]: https://issues.apache.org/jira/browse/IGNITE-12911 [5]: https://issues.apache.org/jira/browse/IGNITE-12553 [6]: http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Complete-Discontinuation-of-IGFS-and-Hadoop-Accelerator-td42282.html пт, 17 июл. 2020 г. в 11:50, Alex Plehanov <plehanov.a...@gmail.com>: > Ivan, > > Merged to 2.9. > > Thanks > > пт, 17 июл. 2020 г. в 01:35, Ivan Rakov <ivan.glu...@gmail.com>: > >> Alex, >> >> Tracing is merged to master: >> https://issues.apache.org/jira/browse/IGNITE-13060 >> >> Can you please port it to 2.9? >> For you convenience, there's PR versus 2.9 with conflicts resolved: >> https://github.com/apache/ignite/pull/8046/files >> >> -- >> Best Regards, >> Ivan Rakov >> >> On Wed, Jul 15, 2020 at 5:33 PM Alex Plehanov <plehanov.a...@gmail.com> >> wrote: >> >>> Ivan, >>> >>> Looks like master is broken after IGNITE-13246 (but everything is ok in >>> 2.9 >>> branch) >>> >>> ср, 15 июл. 2020 г. в 18:54, Alex Plehanov <plehanov.a...@gmail.com>: >>> >>> > Zhenya, Ivan, >>> > >>> > I've cherry-picked IGNITE-13229 and IGNITE-13246 to ignite-2.9 branch. >>> > Thank you. >>> > >>> > ср, 15 июл. 2020 г. в 18:31, Ivan Bessonov <bessonov...@gmail.com>: >>> > >>> >> Guys, >>> >> >>> >> can you please backport >>> >> https://issues.apache.org/jira/browse/IGNITE-13246 >>> >> to ignite-2.9? Me and Alexey Kuznetsov really want these new events in >>> >> release. >>> >> >>> >> This time I prepared PR with resolved conflicts: >>> >> https://github.com/apache/ignite/pull/8042 >>> >> >>> >> Thank you! >>> >> >>> >> вт, 14 июл. 2020 г. в 19:39, Zhenya Stanilovsky >>> >> <arzamas...@mail.ru.invalid >>> >> >: >>> >> >>> >> > >>> >> > >>> >> > >>> >> > Alex, i also suggest to merge this >>> >> > https://issues.apache.org/jira/browse/IGNITE-13229 too, GridClient >>> >> > leakage and further TC OOM preventing. >>> >> > >>> >> > >Ivan, >>> >> > > >>> >> > >It was already in release scope as discussed in this thread. >>> >> > > >>> >> > >вт, 14 июл. 2020 г. в 14:31, Ivan Rakov < ivan.glu...@gmail.com >: >>> >> > > >>> >> > >> Hi, >>> >> > >> >>> >> > >> We are still waiting for a final review of Tracing functionality >>> [1] >>> >> > until >>> >> > >> the end of tomorrow (July 15). >>> >> > >> We anticipate that it will be merged to Ignite master no later >>> than >>> >> July >>> >> > >> 16. >>> >> > >> >>> >> > >> Sorry for being a bit late here. Alex P., can you include [1] to >>> the >>> >> > >> release scope? >>> >> > >> >>> >> > >> [1]: https://issues.apache.org/jira/browse/IGNITE-13060 >>> >> > >> >>> >> > >> -- >>> >> > >> Best Regards, >>> >> > >> Ivan Rakov >>> >> > >> >>> >> > >> On Tue, Jul 14, 2020 at 6:16 AM Alexey Kuznetsov < >>> >> > akuznet...@gridgain.com > >>> >> > >> wrote: >>> >> > >> >>> >> > >>> Alex, >>> >> > >>> >>> >> > >>> Can you cherry-pick to Ignite 2.9 this issue: >>> >> > >>> https://issues.apache.org/jira/browse/IGNITE-13246 ? >>> >> > >>> >>> >> > >>> This issue is about BASELINE events and it is very useful for >>> >> > notification >>> >> > >>> external tools about changes in baseline. >>> >> > >>> >>> >> > >>> Thank you! >>> >> > >>> >>> >> > >>> --- >>> >> > >>> Alexey Kuznetsov >>> >> > >>> >>> >> > >> >>> >> > >>> >> > >>> >> > >>> >> > >>> >> >>> >> >>> >> >>> >> -- >>> >> Sincerely yours, >>> >> Ivan Bessonov >>> >> >>> > >>> >>