Folks, Thanks to everyone responded.
@Alexey Zinoviev <zaleslaw....@gmail.com>, @Alexey Scherbakov <ascherba...@gridgain.com>, @Nikolay Izhikov <nizhi...@apache.org>, @Maxim Muzafarov <mmu...@apache.org>, @Anton Vinogradov <a...@apache.org>, @Andrey Gura <ag...@apache.org> could you guys please also join this thread and share your intentions for this year? What I want to do next, once the majority responds, is to create an Ignite Roadmap wiki page and put together a table with all the initiatives. The table will have an "expected readiness" column with contributors best guess/estimate on when an improvement is to be ready (you would need to fill it once the page exists). The last column will be for a target release - once we see that many improvements converge around some date, then we'll know when Ignite 2.9, 2.10, etc. need to be released. Hope you guys are fine with such an approach for the roadmap and release schedule creation. - Denis On Fri, Apr 10, 2020 at 7:44 AM Igor Sapego <isap...@apache.org> wrote: > My plan includes: > * Cluster API for C++ thick client > * Moving Python, Node.js and PHP thin clients in separate repositories and > separate release cycles. > * Partition Awareness for Python and Node.js thin clients > * SQL for C++ thin client. > > Steven, > > There are some third-party golang clients AFAIK, for example [1]. Though > I'm not aware of their current > status. > > [1] - https://github.com/amsokol/ignite-go-client > > > Best Regards, > Igor > > > On Fri, Apr 10, 2020 at 5:26 PM smeadows-abb <steven.mead...@us.abb.com> > wrote: > > > My company is initiating major project using Golang, Ignite and need > native > > Golang client support. What is the status of support for Golang? > > > > > > > > -- > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >
