Ivan, > Should not we state in release notes what new experimental API was added?
I think we should. Will do. Just not to miss anything that we should mark with @IgniteExperimental: Consistency Check [1], Monitoring [2] anything else? > As Flink integration was moved to external repository how Ignite 2.8 users > will be able to use that integration? Since ignite-extension has a separate release cycle (right?), it is better to release ignite-extension rather than cherry-pick this change back to 2.8. I also think it is not a blocker for the release, but we should do our best make the first ignite-extension release as earlier as possible. [1] https://issues.apache.org/jira/browse/IGNITE-10663 [2] https://issues.apache.org/jira/browse/IGNITE-11848 On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <vololo...@gmail.com> wrote: > > Maxim, > > A couple of questions: > 1. We added an annotation to designate experimental API. Should not we > state in release notes what new experimental API was added? Perhaps in > a separate block. > 2. As Flink integration was moved to external repository how Ignite > 2.8 users will be able to use that integration? > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <mmu...@apache.org>: > > > > Igniters, > > > > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8 release. > > > > Currently, IEP-35 monitoring issues are not included in this PR. Will > > do it soon. > > Please, take a look. > > > > > > [1] https://github.com/apache/ignite/pull/7367/files > > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <mmu...@apache.org> wrote: > > > > > > Igniters, > > > > > > > > > Let me share the current status of the release. > > > > > > 1. > > > Waiting for the issues [1] [2] (discussed previously this thread) to > > > be tested by TC.Bot and merged to the 2.8 release branch. > > > > > > 2. > > > Only 2 release BLOCKER issues left. I'm planning to move these issues > > > to 2.8.1 release. > > > The issue [4] (Error during purges by expiration: Unknown page type) > > > will be covered by [1] [2]. > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes > > > getting down) probably require additional info to reproduce the issue. > > > > > > 3. > > > A potential performance drop on `putAll` operations on an in-memory > > > cluster (see [5] for details). > > > I'll try to reproduce in another test environment. > > > > > > > > > Will keep you posted. > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593 > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594 > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398 > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489 > > > [5] > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST) > > > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk > > > <alexey.goncha...@gmail.com> wrote: > > > > > > > > Sounds good, will do! > > > > -- > Best regards, > Ivan Pavlukhin
