Is it ok for me, but please move IGFS dropping ticket to the next release, I have no capacity to finish in time the blocker ticket related to Tensorflow-Ignite integration and as a result we shouldn't remove the IGFS yet but please mark it as a deprecated and ready for removal in 3.0
чт, 28 нояб. 2019 г. в 16:03, Maxim Muzafarov <mmu...@apache.org>: > Denis, > > What kind of additional checks do we need? Maybe I'm missing something > but all issues currently merged to the master branch will be present > in the 2.8 release branch too. > I see that this issue has been closed a long time ago, so it > definitely comes in. > > On Thu, 28 Nov 2019 at 01:33, Denis Magda <dma...@apache.org> wrote: > > > > Hi Maxim, > > > > Sounds good, thanks for branching. Could you double-check that the > > following issue was added to the release? > > https://issues.apache.org/jira/browse/IGNITE-10577 > > > > - > > Denis > > > > > > On Wed, Nov 27, 2019 at 7:50 AM Maxim Muzafarov <mmu...@apache.org> > wrote: > > > > > Igniters, > > > > > > > > > I think we are ready to create the 2.8 release branch since features > > > [1] which we are waiting for are almost completed. > > > > > > 4 December 2019, the 2.8 release branch will be created. All related > > > issues with a priority less than `critical` will be excluded from the > > > 2.8 release (fix version will be changed to 2.9). > > > > > > > > > Any objections? > > > > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Awatingfeaturescompletion > > > >
