Igniters,

I just did a search on 1.6 issues and looks like we have 293 unresolved
issues for 1.6. Obviously we are not going to be fixing all of them and
most of them will have to be moved to 1.7.

Yakov, given that you have most experience with Jira and have been managing
it before, do you mind moving the tickets? Here is the link to the filter:

http://bit.ly/24Mrddg

Also, if anything needs to be addressed in 1.6, please list these tickets
here, in this thread.

Thanks,
D.

On Tue, May 10, 2016 at 6:00 AM, Pavel Tupitsyn <ptupit...@gridgain.com>
wrote:

> Dmitriy, yes, many of them do. I'll create 1.6 version on
> apacheignite-net.readme.io and document them this week (task:
> IGNITE-3101).
>
> Pavel.
>
> On Tue, May 10, 2016 at 3:52 PM, Dmitriy Setrakyan <dsetrak...@apache.org>
> wrote:
>
> > Thanks Pavel, do any of these features require new documentation?
> >
> > On Tue, May 10, 2016 at 5:16 AM, Pavel Tupitsyn <ptupit...@gridgain.com>
> > wrote:
> >
> > > Hi, here is a list of major .NET features included in 1.6 (all closed
> and
> > > merged):
> > >
> > > * LINQ Provider for SQL queries (IGNITE-1630)
> > > * NuGet distribution (IGNITE-1626)
> > > * C#, app.config and web.config configuration (instead of Spring XML)
> > > (IGNITE-1906, IGNITE-2380)
> > > * Atomic data structures (IGNITE-1563)
> > > * Universal AnyCPU binaries (instead of separate x64/x86) (IGNITE-2694)
> > > * Call Java services (IGNITE-2686)
> > > * Java-based continuous query filters (IGNITE-2977)
> > > * Mixed-cluster Compute (IGNITE-2621)
> > > * Compute task cancellation (IGNITE-2228)
> > > * Binary format compact footers (IGNITE-2702)
> > > * Raw mode reflective serialization (IGNITE-1419)
> > > * Automatic Java detection: no need for JAVA_HOME (IGNITE-2866)
> > >
> > > Thanks,
> > > Pavel.
> > >
> > >
> > > On Thu, May 5, 2016 at 5:01 PM, Igor Sapego <isap...@gridgain.com>
> > wrote:
> > >
> > > > Hello,
> > > >
> > > > IGNITE-1786 is fully merged to master.
> > > >
> > > > Best Regards,
> > > > Igor
> > > >
> > > > On Wed, May 4, 2016 at 6:59 PM, Dmitriy Setrakyan <
> > dsetrak...@apache.org
> > > >
> > > > wrote:
> > > >
> > > > > Resending (fixed links)
> > > > >
> > > > > On Wed, May 4, 2016 at 8:46 AM, Dmitriy Setrakyan <
> > > dsetrak...@apache.org
> > > > >
> > > > > wrote:
> > > > >
> > > > > > Igniters,
> > > > > >
> > > > > > Looks like we are almost done with the outstanding issues, mainly
> > > ODBC
> > > > > > support and cache concurrent map changes. As far as the
> concurrent
> > > map,
> > > > > we
> > > > > > had a performance drop, and I think it is pretty important that
> we
> > > > > address
> > > > > > it prior to the release.
> > > > > >
> > > > > > Can we please get an update for these tickets?
> > > > > >
> > > > > > IGNITE-2948 <https://issues.apache.org/jira/browse/IGNITE-2948>
> -
> > > > > > Optimize usage of GridCacheConcurrentMap
> > > > > > IGNITE-1786 <https://issues.apache.org/jira/browse/IGNITE-1786>
> -
> > > Need
> > > > > to
> > > > > > implement ODBC driver for Ignite
> > > > > >
> > > > > > Once these issues are resolved, we can move to the testing phase
> > > > > (probably
> > > > > > a week), and then send it for the vote.
> > > > > >
> > > > > > D.
> > > > > >
> > > > > > On Fri, Apr 29, 2016 at 3:12 AM, Yakov Zhdanov <
> > yzhda...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > >> I think we are almost done with odbc support and I hope that we
> > can
> > > > > >> release
> > > > > >> about mid or second half of May.
> > > > > >>
> > > > > >> --Yakov
> > > > > >>
> > > > > >> 2016-04-27 11:13 GMT+03:00 sssow <ss...@hotmail.com>:
> > > > > >>
> > > > > >> > Hi,
> > > > > >> > When will you release 1.6?
> > > > > >> > Thank you,
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> >
> > > > > >> > --
> > > > > >> > View this message in context:
> > > > > >> >
> > > > > >>
> > > > >
> > > >
> > >
> >
> http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-1-6-release-timelines-tp7388p8618.html
> > > > > >> > Sent from the Apache Ignite Developers mailing list archive at
> > > > > >> Nabble.com.
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to