Created issues related building ODBC module, running C++ suites and
removing VS project files

1. https://issues.apache.org/jira/browse/IGNITE-15637
2.https://issues.apache.org/jira/browse/IGNITE-15636

вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky <ivanda...@gmail.com>:

> +1
>
> Let's consider building odbc driver using Visual C++ 2017?
>
> 2015, 2017 and 2019 share the same redistributable package and it is the
> default one in Windows 10.
>
> Also, let's remove vs project files, since the most of you all agree that
> it is redundant.
>
> If both suggestions are ok, I will create ticketa soon.
>
> вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn <ptupit...@apache.org>:
>
>> +1
>>
>> On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov <mmu...@apache.org>
>> wrote:
>>
>> > Hello Nikita,
>> >
>> > +1 if you will lead this release.
>> >
>> >
>> > I'd suggest including into the release scope this one issue too:
>> >
>> > Snapshot restore must support restoring with indexes rebuild
>> > https://issues.apache.org/jira/browse/IGNITE-14744
>> >
>> > Hopefully, it will be completed by the end of October.
>> >
>> > On Fri, 24 Sept 2021 at 19:48, Nikita Amelchev <namelc...@apache.org>
>> > wrote:
>> > >
>> > > Dear Ignite Community!
>> > >
>> > > I suggest starting Apache Ignite 2.12 release activities.
>> > >
>> > > For now, we've accumulated a hundred resolved issues with new features
>> > > and bug fixes which are waiting for their release date. For example,
>> > >
>> > > CDC Application
>> > > Index Query API
>> > > Utility for analyzing indexes
>> > > Java compute tasks for C++
>> > > SQL commands statistics
>> > > etc.
>> > >
>> > > I want to propose myself to be the release manager of the planning
>> > release.
>> > >
>> > > I propose the following timeline:
>> > >
>> > > Scope Freeze: October 15, 2021
>> > > Code Freeze: October 29, 2021
>> > > Voting Date: November 15, 2021
>> > > Release Date: November 22, 2021
>> > >
>> > > WDYT?
>> > >
>> > > --
>> > > Best wishes,
>> > > Amelchev Nikita
>> >
>>
>

-- 
Sincerely yours, Ivan Daschinskiy

Reply via email to