Denis, All the stuff you've mentioned is merged into H2 master. In Ignite we do some related work though.
In addition I work on H2 result set generation improvements and will merge them soon as well. After that we'll try to release H2. Sergi 2017-03-23 6:12 GMT+03:00 Denis Magda <dma...@apache.org>: > Refreshed a list of “Required tickets” that, personally, have to be > released under 2.0: > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0 > > Most of them are related to the new memory architecture, SQL improvements, > Hibernate 5 support and general API cleanup. > > Some of SQL tickets require a release of the latest H2 version: > > - Enums support: https://issues.apache.org/jira/browse/IGNITE-3595 > - _key and _val removal from general result set: > https://issues.apache.org/jira/browse/IGNITE-3487 > - SQL hints: https://issues.apache.org/jira/browse/IGNITE-4594 > > *The owners of the tickets*, how close we’re to the H2 release? We have to > consider it, otherwise it will be a bar for Ignite 2.0. > > — > Denis > > > On Mar 22, 2017, at 10:19 AM, Dmitriy Setrakyan <dsetrak...@apache.org> > wrote: > > > > Thanks, Denis! Looks reasonable to me. > > > > On Wed, Mar 22, 2017 at 10:18 AM, Denis Magda <dma...@apache.org> wrote: > > > >> Igniters, > >> > >> Branch ignite-2.0 was merged to master and removed after that. > >> > >> All the commits must go to master. AI 2.0 release branch will be created > >> in a matter of 1-2 weeks based on final code freeze dates which we need > to > >> define together. > >> > >> I propose the timeline below: > >> > >> Code Freeze: April 14th, 2017 > >> QA and Final Benchmarking: April 14th - April 24th, 2017 > >> Voting Date: April 24th, 2017. > >> Release Date: April 28th, 2017. > >> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0 > >> > >> Does anyone have any concerns? > >> > >> > >> — > >> Denis > >
