Ilya,
I think we must accept only blocker issues to the release branch. My previous experience tells me that even a small change which seems absolutely easy and clear can break everything. So, let's move this issue [1] to the next release. Currently, it doesn't look like a blocker. [1] https://issues.apache.org/jira/browse/IGNITE-12672 On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <mmu...@apache.org> wrote: > > Igniters, > > > I've prepared the issue [1] and PR [2] with removing @deprecate > annotation on DataRegionMetrics and adding @IgniteExperimental to the > new metrics API. > Can anyone review my changes? > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690 > [2] https://github.com/apache/ignite/pull/7440 > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <ilya.kasnach...@gmail.com> > wrote: > > > > Hello! > > > > I have just merged a fix for embarrassing issue where you could UPDATE > > entries with Spring Data, but not "Update" or "update" them. > > > > I suggest adding this fix to the scope of 2.8, since Spring Data is popular > > and it does not in any way affect code outside of its modules. > > > > https://issues.apache.org/jira/browse/IGNITE-12672 > > > > WDYT? > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <mmu...@apache.org>: > > > > > Alexey, > > > > > > > > > Yes. I will remove @deprecation according to the vote results and will > > > go further with the release steps [1] since there no blockers left. > > > > > > > > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk > > > <alexey.goncha...@gmail.com> wrote: > > > > > > > > Folks, > > > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master and > > > > ignite-2.8. What's left? Should we remove deprecation from the old > > > metrics > > > > and start the vote? > > >
