What's about releasing Ignite 2.5 a bit earlier?

[dmagda]

Igniters,

According to our regular schedule, every new Ignite version usually goes
public once in 3 months. As you remember, the latest 2.4 release, which
took us 5 months to improve and roll out, was based on the version of the
source code dated by January.

Since that time the master branch went far ahead and already incorporates
many valuable fixes and capabilities such as:

   - Fixes provided as a part of "Gree Team City" activity.
   - Persistence: page replacement algorithm and throttling optimizations,
   out of memory in checkpointing buffer corrections, etc. Alex G and Ivan can
   shed more light here.
   - Data loading optimizations for SQL: streaming for JDBC thin driver and
   copy command
   - Genetic Algorithms Grid Contribution!
   - Java Thin Client developed by Alexey Kukushkin


   - the list goes on and on... Please share the contributions you are
   ready to release.

So, why don't we go ahead and release the current master and possibly extra
tickets that are in the review state earlier? What's about April 30 as the
next release date?

--
Densi

[vveider]

Will there be a major new feature or this release will concentrate on stability and optimisations?

Also, I guess, we will have to include into 2.5 release full support for Java 9 and Java 10 (that WILL require some developers time).
And RPM / DEB packages stage II phase will require lots of testing and infrastructure preparations: place to store package, RPM / DEB build inclusion into release process and so on.

Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all those activities are not finished in time.

> On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
>
> Igniters,
>
> According to our regular schedule, every new Ignite version usually goes
> public once in 3 months. As you remember, the latest 2.4 release, which
> took us 5 months to improve and roll out, was based on the version of the
> source code dated by January.
>
> Since that time the master branch went far ahead and already incorporates
> many valuable fixes and capabilities such as:
>
>   - Fixes provided as a part of "Gree Team City" activity.
>   - Persistence: page replacement algorithm and throttling optimizations,
>   out of memory in checkpointing buffer corrections, etc. Alex G and Ivan can
>   shed more light here.
>   - Data loading optimizations for SQL: streaming for JDBC thin driver and
>   copy command
>   - Genetic Algorithms Grid Contribution!
>   - Java Thin Client developed by Alexey Kukushkin
>
>
>   - the list goes on and on... Please share the contributions you are
>   ready to release.
>
> So, why don't we go ahead and release the current master and possibly extra
> tickets that are in the review state earlier? What's about April 30 as the
> next release date?
>
> --
> Densi

[dmagda]

Petr,

Java Thin client, GA Grid, COPY command are the most significant additions
to the release (if to talk about the features). Aside from that, I see many
valuable optimizations and fixes that have been sitting in the master for a
while (some of them were merged in January). It's preferable to release
them.

As for Java 10 and DEB, if you feel you can't make them to the release,
then it can wait till 2.6.

Speaking of Java 9, what's left? I thought it's already fully supported.

--
Denis

On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <[hidden email]> wrote:

> Will there be a major new feature or this release will concentrate on
> stability and optimisations?
>
> Also, I guess, we will have to include into 2.5 release full support for
> Java 9 and Java 10 (that WILL require some developers time).
> And RPM / DEB packages stage II phase will require lots of testing and
> infrastructure preparations: place to store package, RPM / DEB build
> inclusion into release process and so on.
>
> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all those
> activities are not finished in time.
>
>
>
> > On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
> >
> > Igniters,
> >
> > According to our regular schedule, every new Ignite version usually goes
> > public once in 3 months. As you remember, the latest 2.4 release, which
> > took us 5 months to improve and roll out, was based on the version of the
> > source code dated by January.
> >
> > Since that time the master branch went far ahead and already incorporates
> > many valuable fixes and capabilities such as:
> >
> >   - Fixes provided as a part of "Gree Team City" activity.
> >   - Persistence: page replacement algorithm and throttling optimizations,
> >   out of memory in checkpointing buffer corrections, etc. Alex G and
> Ivan can
> >   shed more light here.
> >   - Data loading optimizations for SQL: streaming for JDBC thin driver
> and
> >   copy command
> >   - Genetic Algorithms Grid Contribution!
> >   - Java Thin Client developed by Alexey Kukushkin
> >
> >
> >   - the list goes on and on... Please share the contributions you are
> >   ready to release.
> >
> > So, why don't we go ahead and release the current master and possibly
> extra
> > tickets that are in the review state earlier? What's about April 30 as
> the
> > next release date?
> >
> > --
> > Densi
>
>

[Nikolay Izhikov-2]

Hello, guys

I agree with earlier release.

I propose to include my task IGNITE-7077 to 2.5 release.

Valentin, do you have a time slot to review my implementation?

В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:

> Igniters,
>
> According to our regular schedule, every new Ignite version usually goes
> public once in 3 months. As you remember, the latest 2.4 release, which
> took us 5 months to improve and roll out, was based on the version of the
> source code dated by January.
>
> Since that time the master branch went far ahead and already incorporates
> many valuable fixes and capabilities such as:
>
>    - Fixes provided as a part of "Gree Team City" activity.
>    - Persistence: page replacement algorithm and throttling optimizations,
>    out of memory in checkpointing buffer corrections, etc. Alex G and Ivan can
>    shed more light here.
>    - Data loading optimizations for SQL: streaming for JDBC thin driver and
>    copy command
>    - Genetic Algorithms Grid Contribution!
>    - Java Thin Client developed by Alexey Kukushkin
>
>
>    - the list goes on and on... Please share the contributions you are
>    ready to release.
>
> So, why don't we go ahead and release the current master and possibly extra
> tickets that are in the review state earlier? What's about April 30 as the
> next release date?
>
> --
> Densi

[Nikolay Izhikov-2]

Also, we has new API - ContinuousQueryWithTransformer merged for 2.5 release - [IGNITE-425]

В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет:

> Hello, guys
>
> I agree with earlier release.
>
> I propose to include my task IGNITE-7077 to 2.5 release.
>
> Valentin, do you have a time slot to review my implementation?
>
> В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:
> > Igniters,
> >
> > According to our regular schedule, every new Ignite version usually goes
> > public once in 3 months. As you remember, the latest 2.4 release, which
> > took us 5 months to improve and roll out, was based on the version of the
> > source code dated by January.
> >
> > Since that time the master branch went far ahead and already incorporates
> > many valuable fixes and capabilities such as:
> >
> >    - Fixes provided as a part of "Gree Team City" activity.
> >    - Persistence: page replacement algorithm and throttling optimizations,
> >    out of memory in checkpointing buffer corrections, etc. Alex G and Ivan can
> >    shed more light here.
> >    - Data loading optimizations for SQL: streaming for JDBC thin driver and
> >    copy command
> >    - Genetic Algorithms Grid Contribution!
> >    - Java Thin Client developed by Alexey Kukushkin
> >
> >
> >    - the list goes on and on... Please share the contributions you are
> >    ready to release.
> >
> > So, why don't we go ahead and release the current master and possibly extra
> > tickets that are in the review state earlier? What's about April 30 as the
> > next release date?
> >
> > --
> > Densi

[Dmitriy Pavlov]

Hi Igniters,

Why not? Let's release it a bit earlier.

I think it would be good if Ivan will prepare fix for WAL LOG_ONLY:
http://apache-ignite-developers.2346864.n4.nabble.com/Reconsider-default-WAL-mode-we-need-something-between-LOG-ONLY-and-FSYNC-td28165.html
 Ivan, what do you think?

Also it would be great if we can complete as much MTCGA tickets as we can.
Let's do this release with green TC.

Sincerely,
Dmitriy Pavlov

чт, 22 мар. 2018 г. в 22:08, Nikolay Izhikov <[hidden email]>:

> Also, we has new API - ContinuousQueryWithTransformer merged for 2.5
> release - [IGNITE-425]
>
> В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет:
> > Hello, guys
> >
> > I agree with earlier release.
> >
> > I propose to include my task IGNITE-7077 to 2.5 release.
> >
> > Valentin, do you have a time slot to review my implementation?
> >
> > В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:
> > > Igniters,
> > >
> > > According to our regular schedule, every new Ignite version usually
> goes
> > > public once in 3 months. As you remember, the latest 2.4 release, which
> > > took us 5 months to improve and roll out, was based on the version of
> the
> > > source code dated by January.
> > >
> > > Since that time the master branch went far ahead and already
> incorporates
> > > many valuable fixes and capabilities such as:
> > >
> > >    - Fixes provided as a part of "Gree Team City" activity.
> > >    - Persistence: page replacement algorithm and throttling
> optimizations,
> > >    out of memory in checkpointing buffer corrections, etc. Alex G and
> Ivan can
> > >    shed more light here.
> > >    - Data loading optimizations for SQL: streaming for JDBC thin
> driver and
> > >    copy command
> > >    - Genetic Algorithms Grid Contribution!
> > >    - Java Thin Client developed by Alexey Kukushkin
> > >
> > >
> > >    - the list goes on and on... Please share the contributions you are
> > >    ready to release.
> > >
> > > So, why don't we go ahead and release the current master and possibly
> extra
> > > tickets that are in the review state earlier? What's about April 30 as
> the
> > > next release date?
> > >
> > > --
> > > Densi

[Valentin Kulichenko]

Nikolay,

Sounds like a good idea. I will do my best to speed up the process and
review asap.

-Val

On Thu, Mar 22, 2018 at 11:37 AM, Nikolay Izhikov <[hidden email]>
wrote:

> Hello, guys
>
> I agree with earlier release.
>
> I propose to include my task IGNITE-7077 to 2.5 release.
>
> Valentin, do you have a time slot to review my implementation?
>
> В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:
> > Igniters,
> >
> > According to our regular schedule, every new Ignite version usually goes
> > public once in 3 months. As you remember, the latest 2.4 release, which
> > took us 5 months to improve and roll out, was based on the version of the
> > source code dated by January.
> >
> > Since that time the master branch went far ahead and already incorporates
> > many valuable fixes and capabilities such as:
> >
> >    - Fixes provided as a part of "Gree Team City" activity.
> >    - Persistence: page replacement algorithm and throttling
> optimizations,
> >    out of memory in checkpointing buffer corrections, etc. Alex G and
> Ivan can
> >    shed more light here.
> >    - Data loading optimizations for SQL: streaming for JDBC thin driver
> and
> >    copy command
> >    - Genetic Algorithms Grid Contribution!
> >    - Java Thin Client developed by Alexey Kukushkin
> >
> >
> >    - the list goes on and on... Please share the contributions you are
> >    ready to release.
> >
> > So, why don't we go ahead and release the current master and possibly
> extra
> > tickets that are in the review state earlier? What's about April 30 as
> the
> > next release date?
> >
> > --
> > Densi
>

[vveider]

I’ll do my best to deliver packages in time.


Concerning Java 9/10 — AFAIK there are limitations how do we support it:
* compilation is supported with scala_2.10 modules switched off (due to scala support Java 9 itself starting from 2.12.x+ versions);
* also compilation and run is possible only with lots of ‘--add-modules’ hacks — I think that to say we support Java 9 we have to add modules info to every package;
* tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention, because there are some problems with theirs run.

> On 22 Mar 2018, at 21:09, Denis Magda <[hidden email]> wrote:
>
> Petr,
>
> Java Thin client, GA Grid, COPY command are the most significant additions
> to the release (if to talk about the features). Aside from that, I see many
> valuable optimizations and fixes that have been sitting in the master for a
> while (some of them were merged in January). It's preferable to release
> them.
>
> As for Java 10 and DEB, if you feel you can't make them to the release,
> then it can wait till 2.6.
>
> Speaking of Java 9, what's left? I thought it's already fully supported.
>
> --
> Denis
>
> On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <[hidden email]> wrote:
>
>> Will there be a major new feature or this release will concentrate on
>> stability and optimisations?
>>
>> Also, I guess, we will have to include into 2.5 release full support for
>> Java 9 and Java 10 (that WILL require some developers time).
>> And RPM / DEB packages stage II phase will require lots of testing and
>> infrastructure preparations: place to store package, RPM / DEB build
>> inclusion into release process and so on.
>>
>> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all those
>> activities are not finished in time.
>>
>>
>>
>>> On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
>>>
>>> Igniters,
>>>
>>> According to our regular schedule, every new Ignite version usually goes
>>> public once in 3 months. As you remember, the latest 2.4 release, which
>>> took us 5 months to improve and roll out, was based on the version of the
>>> source code dated by January.
>>>
>>> Since that time the master branch went far ahead and already incorporates
>>> many valuable fixes and capabilities such as:
>>>
>>>  - Fixes provided as a part of "Gree Team City" activity.
>>>  - Persistence: page replacement algorithm and throttling optimizations,
>>>  out of memory in checkpointing buffer corrections, etc. Alex G and
>> Ivan can
>>>  shed more light here.
>>>  - Data loading optimizations for SQL: streaming for JDBC thin driver
>> and
>>>  copy command
>>>  - Genetic Algorithms Grid Contribution!
>>>  - Java Thin Client developed by Alexey Kukushkin
>>>
>>>
>>>  - the list goes on and on... Please share the contributions you are
>>>  ready to release.
>>>
>>> So, why don't we go ahead and release the current master and possibly
>> extra
>>> tickets that are in the review state earlier? What's about April 30 as
>> the
>>> next release date?
>>>
>>> --
>>> Densi
>>
>>

[Alexey Kukushkin]

Denis,

Java thin client is in the final review stage - I expect it will go to
master sometime next week. April 30 release date seems to have enough
contingency for this component.

Thanks!

[Ivan Rakov]

I agree.
Fix of LOG_ONLY is critical for Ignite durability and can be done quickly.
Another reason to release 2.5 earlier is fix of
https://issues.apache.org/jira/browse/IGNITE-7751. It's another critical
bug that possibly can lead to checkpoint buffer overflow and corruption
of internal data structures even with Pages Write Throttling enabled.

Best Regards,
Ivan Rakov

On 22.03.2018 23:20, Dmitry Pavlov wrote:

> Hi Igniters,
>
> Why not? Let's release it a bit earlier.
>
> I think it would be good if Ivan will prepare fix for WAL LOG_ONLY:
> http://apache-ignite-developers.2346864.n4.nabble.com/Reconsider-default-WAL-mode-we-need-something-between-LOG-ONLY-and-FSYNC-td28165.html 
>  Ivan, what do you think?
>
> Also it would be great if we can complete as much MTCGA tickets as we
> can. Let's do this release with green TC.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 22 мар. 2018 г. в 22:08, Nikolay Izhikov <[hidden email]
> <mailto:[hidden email]>>:
>
>     Also, we has new API - ContinuousQueryWithTransformer merged for
>     2.5 release - [IGNITE-425]
>
>     В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет:
>     > Hello, guys
>     >
>     > I agree with earlier release.
>     >
>     > I propose to include my task IGNITE-7077 to 2.5 release.
>     >
>     > Valentin, do you have a time slot to review my implementation?
>     >
>     > В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:
>     > > Igniters,
>     > >
>     > > According to our regular schedule, every new Ignite version
>     usually goes
>     > > public once in 3 months. As you remember, the latest 2.4
>     release, which
>     > > took us 5 months to improve and roll out, was based on the
>     version of the
>     > > source code dated by January.
>     > >
>     > > Since that time the master branch went far ahead and already
>     incorporates
>     > > many valuable fixes and capabilities such as:
>     > >
>     > >    - Fixes provided as a part of "Gree Team City" activity.
>     > >    - Persistence: page replacement algorithm and throttling
>     optimizations,
>     > >    out of memory in checkpointing buffer corrections, etc.
>     Alex G and Ivan can
>     > >    shed more light here.
>     > >    - Data loading optimizations for SQL: streaming for JDBC
>     thin driver and
>     > >    copy command
>     > >    - Genetic Algorithms Grid Contribution!
>     > >    - Java Thin Client developed by Alexey Kukushkin
>     > >
>     > >
>     > >    - the list goes on and on... Please share the contributions
>     you are
>     > >    ready to release.
>     > >
>     > > So, why don't we go ahead and release the current master and
>     possibly extra
>     > > tickets that are in the review state earlier? What's about
>     April 30 as the
>     > > next release date?
>     > >
>     > > --
>     > > Densi
>

[Dmitriy Pavlov]

Hi Igniters,

There are two tickets I forgot to mention, it is optimisation of Native
Persistence:

Performing data pages IO outside locks
- https://issues.apache.org/jira/browse/IGNITE-7606  - Write removed dirty
page during replacement without holding segment write lock
- https://issues.apache.org/jira/browse/IGNITE-7698  - Page read during
replacement should be outside of segment write lock

Both are resovled, so no delays from their side.

Sincerely,
Dmitriy Pavlov

пт, 23 мар. 2018 г. в 12:06, Ivan Rakov <[hidden email]>:

> I agree.
> Fix of LOG_ONLY is critical for Ignite durability and can be done quickly.
> Another reason to release 2.5 earlier is fix of
> https://issues.apache.org/jira/browse/IGNITE-7751. It's another critical
> bug that possibly can lead to checkpoint buffer overflow and corruption of
> internal data structures even with Pages Write Throttling enabled.
>
> Best Regards,
> Ivan Rakov
>
> On 22.03.2018 23:20, Dmitry Pavlov wrote:
>
> Hi Igniters,
>
> Why not? Let's release it a bit earlier.
>
> I think it would be good if Ivan will prepare fix for WAL LOG_ONLY:
> http://apache-ignite-developers.2346864.n4.nabble.com/Reconsider-default-WAL-mode-we-need-something-between-LOG-ONLY-and-FSYNC-td28165.html
>  Ivan, what do you think?
>
> Also it would be great if we can complete as much MTCGA tickets as we can.
> Let's do this release with green TC.
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 22 мар. 2018 г. в 22:08, Nikolay Izhikov <[hidden email]>:
>
>> Also, we has new API - ContinuousQueryWithTransformer merged for 2.5
>> release - [IGNITE-425]
>>
>> В Чт, 22/03/2018 в 21:37 +0300, Nikolay Izhikov пишет:
>> > Hello, guys
>> >
>> > I agree with earlier release.
>> >
>> > I propose to include my task IGNITE-7077 to 2.5 release.
>> >
>> > Valentin, do you have a time slot to review my implementation?
>> >
>> > В Чт, 22/03/2018 в 10:39 -0700, Denis Magda пишет:
>> > > Igniters,
>> > >
>> > > According to our regular schedule, every new Ignite version usually
>> goes
>> > > public once in 3 months. As you remember, the latest 2.4 release,
>> which
>> > > took us 5 months to improve and roll out, was based on the version of
>> the
>> > > source code dated by January.
>> > >
>> > > Since that time the master branch went far ahead and already
>> incorporates
>> > > many valuable fixes and capabilities such as:
>> > >
>> > >    - Fixes provided as a part of "Gree Team City" activity.
>> > >    - Persistence: page replacement algorithm and throttling
>> optimizations,
>> > >    out of memory in checkpointing buffer corrections, etc. Alex G and
>> Ivan can
>> > >    shed more light here.
>> > >    - Data loading optimizations for SQL: streaming for JDBC thin
>> driver and
>> > >    copy command
>> > >    - Genetic Algorithms Grid Contribution!
>> > >    - Java Thin Client developed by Alexey Kukushkin
>> > >
>> > >
>> > >    - the list goes on and on... Please share the contributions you are
>> > >    ready to release.
>> > >
>> > > So, why don't we go ahead and release the current master and possibly
>> extra
>> > > tickets that are in the review state earlier? What's about April 30
>> as the
>> > > next release date?
>> > >
>> > > --
>> > > Densi
>
>
>

[dmagda]

Petr,

I guess we would need much more time to handle all Java 9/10 tasks. Since
none of them looks like a blocker to me, I would suggest us not to rush and
target the tasks for 2.4 release.

Overall, I see that we're in an agreement in regards the earlier date of
2.5 release. I'll let the rest of the community to speak out until the
beginning of the next week.

--
Denis



On Thu, Mar 22, 2018 at 8:24 PM, Petr Ivanov <[hidden email]> wrote:

> I’ll do my best to deliver packages in time.
>
>
> Concerning Java 9/10 — AFAIK there are limitations how do we support it:
> * compilation is supported with scala_2.10 modules switched off (due to
> scala support Java 9 itself starting from 2.12.x+ versions);
> * also compilation and run is possible only with lots of ‘--add-modules’
> hacks — I think that to say we support Java 9 we have to add modules info
> to every package;
> * tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention,
> because there are some problems with theirs run.
>
>
>
> > On 22 Mar 2018, at 21:09, Denis Magda <[hidden email]> wrote:
> >
> > Petr,
> >
> > Java Thin client, GA Grid, COPY command are the most significant
> additions
> > to the release (if to talk about the features). Aside from that, I see
> many
> > valuable optimizations and fixes that have been sitting in the master
> for a
> > while (some of them were merged in January). It's preferable to release
> > them.
> >
> > As for Java 10 and DEB, if you feel you can't make them to the release,
> > then it can wait till 2.6.
> >
> > Speaking of Java 9, what's left? I thought it's already fully supported.
> >
> > --
> > Denis
> >
> > On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <[hidden email]>
> wrote:
> >
> >> Will there be a major new feature or this release will concentrate on
> >> stability and optimisations?
> >>
> >> Also, I guess, we will have to include into 2.5 release full support for
> >> Java 9 and Java 10 (that WILL require some developers time).
> >> And RPM / DEB packages stage II phase will require lots of testing and
> >> infrastructure preparations: place to store package, RPM / DEB build
> >> inclusion into release process and so on.
> >>
> >> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all
> those
> >> activities are not finished in time.
> >>
> >>
> >>
> >>> On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
> >>>
> >>> Igniters,
> >>>
> >>> According to our regular schedule, every new Ignite version usually
> goes
> >>> public once in 3 months. As you remember, the latest 2.4 release, which
> >>> took us 5 months to improve and roll out, was based on the version of
> the
> >>> source code dated by January.
> >>>
> >>> Since that time the master branch went far ahead and already
> incorporates
> >>> many valuable fixes and capabilities such as:
> >>>
> >>>  - Fixes provided as a part of "Gree Team City" activity.
> >>>  - Persistence: page replacement algorithm and throttling
> optimizations,
> >>>  out of memory in checkpointing buffer corrections, etc. Alex G and
> >> Ivan can
> >>>  shed more light here.
> >>>  - Data loading optimizations for SQL: streaming for JDBC thin driver
> >> and
> >>>  copy command
> >>>  - Genetic Algorithms Grid Contribution!
> >>>  - Java Thin Client developed by Alexey Kukushkin
> >>>
> >>>
> >>>  - the list goes on and on... Please share the contributions you are
> >>>  ready to release.
> >>>
> >>> So, why don't we go ahead and release the current master and possibly
> >> extra
> >>> tickets that are in the review state earlier? What's about April 30 as
> >> the
> >>> next release date?
> >>>
> >>> --
> >>> Densi
> >>
> >>
>
>

[vveider]

Agree with no blocker.

Then as developers we just have to send a clear message that "we making it towards Java9/10 honest support, but do not use it yet on prod environments” :)

> On 23 Mar 2018, at 22:41, Denis Magda <[hidden email]> wrote:
>
> Petr,
>
> I guess we would need much more time to handle all Java 9/10 tasks. Since
> none of them looks like a blocker to me, I would suggest us not to rush and
> target the tasks for 2.4 release.
>
> Overall, I see that we're in an agreement in regards the earlier date of
> 2.5 release. I'll let the rest of the community to speak out until the
> beginning of the next week.
>
> --
> Denis
>
>
>
> On Thu, Mar 22, 2018 at 8:24 PM, Petr Ivanov <[hidden email]> wrote:
>
>> I’ll do my best to deliver packages in time.
>>
>>
>> Concerning Java 9/10 — AFAIK there are limitations how do we support it:
>> * compilation is supported with scala_2.10 modules switched off (due to
>> scala support Java 9 itself starting from 2.12.x+ versions);
>> * also compilation and run is possible only with lots of ‘--add-modules’
>> hacks — I think that to say we support Java 9 we have to add modules info
>> to every package;
>> * tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention,
>> because there are some problems with theirs run.
>>
>>
>>
>>> On 22 Mar 2018, at 21:09, Denis Magda <[hidden email]> wrote:
>>>
>>> Petr,
>>>
>>> Java Thin client, GA Grid, COPY command are the most significant
>> additions
>>> to the release (if to talk about the features). Aside from that, I see
>> many
>>> valuable optimizations and fixes that have been sitting in the master
>> for a
>>> while (some of them were merged in January). It's preferable to release
>>> them.
>>>
>>> As for Java 10 and DEB, if you feel you can't make them to the release,
>>> then it can wait till 2.6.
>>>
>>> Speaking of Java 9, what's left? I thought it's already fully supported.
>>>
>>> --
>>> Denis
>>>
>>> On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <[hidden email]>
>> wrote:
>>>
>>>> Will there be a major new feature or this release will concentrate on
>>>> stability and optimisations?
>>>>
>>>> Also, I guess, we will have to include into 2.5 release full support for
>>>> Java 9 and Java 10 (that WILL require some developers time).
>>>> And RPM / DEB packages stage II phase will require lots of testing and
>>>> infrastructure preparations: place to store package, RPM / DEB build
>>>> inclusion into release process and so on.
>>>>
>>>> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all
>> those
>>>> activities are not finished in time.
>>>>
>>>>
>>>>
>>>>> On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
>>>>>
>>>>> Igniters,
>>>>>
>>>>> According to our regular schedule, every new Ignite version usually
>> goes
>>>>> public once in 3 months. As you remember, the latest 2.4 release, which
>>>>> took us 5 months to improve and roll out, was based on the version of
>> the
>>>>> source code dated by January.
>>>>>
>>>>> Since that time the master branch went far ahead and already
>> incorporates
>>>>> many valuable fixes and capabilities such as:
>>>>>
>>>>> - Fixes provided as a part of "Gree Team City" activity.
>>>>> - Persistence: page replacement algorithm and throttling
>> optimizations,
>>>>> out of memory in checkpointing buffer corrections, etc. Alex G and
>>>> Ivan can
>>>>> shed more light here.
>>>>> - Data loading optimizations for SQL: streaming for JDBC thin driver
>>>> and
>>>>> copy command
>>>>> - Genetic Algorithms Grid Contribution!
>>>>> - Java Thin Client developed by Alexey Kukushkin
>>>>>
>>>>>
>>>>> - the list goes on and on... Please share the contributions you are
>>>>> ready to release.
>>>>>
>>>>> So, why don't we go ahead and release the current master and possibly
>>>> extra
>>>>> tickets that are in the review state earlier? What's about April 30 as
>>>> the
>>>>> next release date?
>>>>>
>>>>> --
>>>>> Densi
>>>>
>>>>
>>
>>

[dmagda]

Petr,

I think your statement in regards the non-readiness for the production
usage is too strong :) The issue you listed treated as usability ones by
me. Agree that it's inconvenient to inject ‘--add-modules’ here and there
but it doesn't lead to failures at runtime.

If I'm still missing something and there are the bugs that might affect the
stability of the clusters at runtime, then please share them with us.
You're more aware than anyone else.

--
Denis

On Fri, Mar 23, 2018 at 8:50 PM, Petr Ivanov <[hidden email]> wrote:

> Agree with no blocker.
>
> Then as developers we just have to send a clear message that "we making it
> towards Java9/10 honest support, but do not use it yet on prod
> environments” :)
>
>
> > On 23 Mar 2018, at 22:41, Denis Magda <[hidden email]> wrote:
> >
> > Petr,
> >
> > I guess we would need much more time to handle all Java 9/10 tasks. Since
> > none of them looks like a blocker to me, I would suggest us not to rush
> and
> > target the tasks for 2.4 release.
> >
> > Overall, I see that we're in an agreement in regards the earlier date of
> > 2.5 release. I'll let the rest of the community to speak out until the
> > beginning of the next week.
> >
> > --
> > Denis
> >
> >
> >
> > On Thu, Mar 22, 2018 at 8:24 PM, Petr Ivanov <[hidden email]>
> wrote:
> >
> >> I’ll do my best to deliver packages in time.
> >>
> >>
> >> Concerning Java 9/10 — AFAIK there are limitations how do we support it:
> >> * compilation is supported with scala_2.10 modules switched off (due to
> >> scala support Java 9 itself starting from 2.12.x+ versions);
> >> * also compilation and run is possible only with lots of ‘--add-modules’
> >> hacks — I think that to say we support Java 9 we have to add modules
> info
> >> to every package;
> >> * tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention,
> >> because there are some problems with theirs run.
> >>
> >>
> >>
> >>> On 22 Mar 2018, at 21:09, Denis Magda <[hidden email]> wrote:
> >>>
> >>> Petr,
> >>>
> >>> Java Thin client, GA Grid, COPY command are the most significant
> >> additions
> >>> to the release (if to talk about the features). Aside from that, I see
> >> many
> >>> valuable optimizations and fixes that have been sitting in the master
> >> for a
> >>> while (some of them were merged in January). It's preferable to release
> >>> them.
> >>>
> >>> As for Java 10 and DEB, if you feel you can't make them to the release,
> >>> then it can wait till 2.6.
> >>>
> >>> Speaking of Java 9, what's left? I thought it's already fully
> supported.
> >>>
> >>> --
> >>> Denis
> >>>
> >>> On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <[hidden email]>
> >> wrote:
> >>>
> >>>> Will there be a major new feature or this release will concentrate on
> >>>> stability and optimisations?
> >>>>
> >>>> Also, I guess, we will have to include into 2.5 release full support
> for
> >>>> Java 9 and Java 10 (that WILL require some developers time).
> >>>> And RPM / DEB packages stage II phase will require lots of testing and
> >>>> infrastructure preparations: place to store package, RPM / DEB build
> >>>> inclusion into release process and so on.
> >>>>
> >>>> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all
> >> those
> >>>> activities are not finished in time.
> >>>>
> >>>>
> >>>>
> >>>>> On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
> >>>>>
> >>>>> Igniters,
> >>>>>
> >>>>> According to our regular schedule, every new Ignite version usually
> >> goes
> >>>>> public once in 3 months. As you remember, the latest 2.4 release,
> which
> >>>>> took us 5 months to improve and roll out, was based on the version of
> >> the
> >>>>> source code dated by January.
> >>>>>
> >>>>> Since that time the master branch went far ahead and already
> >> incorporates
> >>>>> many valuable fixes and capabilities such as:
> >>>>>
> >>>>> - Fixes provided as a part of "Gree Team City" activity.
> >>>>> - Persistence: page replacement algorithm and throttling
> >> optimizations,
> >>>>> out of memory in checkpointing buffer corrections, etc. Alex G and
> >>>> Ivan can
> >>>>> shed more light here.
> >>>>> - Data loading optimizations for SQL: streaming for JDBC thin driver
> >>>> and
> >>>>> copy command
> >>>>> - Genetic Algorithms Grid Contribution!
> >>>>> - Java Thin Client developed by Alexey Kukushkin
> >>>>>
> >>>>>
> >>>>> - the list goes on and on... Please share the contributions you are
> >>>>> ready to release.
> >>>>>
> >>>>> So, why don't we go ahead and release the current master and possibly
> >>>> extra
> >>>>> tickets that are in the review state earlier? What's about April 30
> as
> >>>> the
> >>>>> next release date?
> >>>>>
> >>>>> --
> >>>>> Densi
> >>>>
> >>>>
> >>
> >>
>
>

[vveider]

My concern is only in fact, that Ignite is currently not tested under
Java9/10 as thorough as it is under Java8.

As I mentioned before - I agree with no blocker on this matter and have no
other problems to report for now. I guess I’ll start a new thread about the
scheme of supporting future Java versions.


On Sat, 24 Mar 2018 at 07:29, Denis Magda <[hidden email]> wrote:

> Petr,
>
> I think your statement in regards the non-readiness for the production
> usage is too strong :) The issue you listed treated as usability ones by
> me. Agree that it's inconvenient to inject ‘--add-modules’ here and there
> but it doesn't lead to failures at runtime.
>
> If I'm still missing something and there are the bugs that might affect the
> stability of the clusters at runtime, then please share them with us.
> You're more aware than anyone else.
>
> --
> Denis
>
> On Fri, Mar 23, 2018 at 8:50 PM, Petr Ivanov <[hidden email]> wrote:
>
> > Agree with no blocker.
> >
> > Then as developers we just have to send a clear message that "we making
> it
> > towards Java9/10 honest support, but do not use it yet on prod
> > environments” :)
> >
> >
> > > On 23 Mar 2018, at 22:41, Denis Magda <[hidden email]> wrote:
> > >
> > > Petr,
> > >
> > > I guess we would need much more time to handle all Java 9/10 tasks.
> Since
> > > none of them looks like a blocker to me, I would suggest us not to rush
> > and
> > > target the tasks for 2.4 release.
> > >
> > > Overall, I see that we're in an agreement in regards the earlier date
> of
> > > 2.5 release. I'll let the rest of the community to speak out until the
> > > beginning of the next week.
> > >
> > > --
> > > Denis
> > >
> > >
> > >
> > > On Thu, Mar 22, 2018 at 8:24 PM, Petr Ivanov <[hidden email]>
> > wrote:
> > >
> > >> I’ll do my best to deliver packages in time.
> > >>
> > >>
> > >> Concerning Java 9/10 — AFAIK there are limitations how do we support
> it:
> > >> * compilation is supported with scala_2.10 modules switched off (due
> to
> > >> scala support Java 9 itself starting from 2.12.x+ versions);
> > >> * also compilation and run is possible only with lots of
> ‘--add-modules’
> > >> hacks — I think that to say we support Java 9 we have to add modules
> > info
> > >> to every package;
> > >> * tests (project ‘Ignite Tests 2.4+ (Java 9)’) also require attention,
> > >> because there are some problems with theirs run.
> > >>
> > >>
> > >>
> > >>> On 22 Mar 2018, at 21:09, Denis Magda <[hidden email]> wrote:
> > >>>
> > >>> Petr,
> > >>>
> > >>> Java Thin client, GA Grid, COPY command are the most significant
> > >> additions
> > >>> to the release (if to talk about the features). Aside from that, I
> see
> > >> many
> > >>> valuable optimizations and fixes that have been sitting in the master
> > >> for a
> > >>> while (some of them were merged in January). It's preferable to
> release
> > >>> them.
> > >>>
> > >>> As for Java 10 and DEB, if you feel you can't make them to the
> release,
> > >>> then it can wait till 2.6.
> > >>>
> > >>> Speaking of Java 9, what's left? I thought it's already fully
> > supported.
> > >>>
> > >>> --
> > >>> Denis
> > >>>
> > >>> On Thu, Mar 22, 2018 at 10:47 AM, Petr Ivanov <[hidden email]>
> > >> wrote:
> > >>>
> > >>>> Will there be a major new feature or this release will concentrate
> on
> > >>>> stability and optimisations?
> > >>>>
> > >>>> Also, I guess, we will have to include into 2.5 release full support
> > for
> > >>>> Java 9 and Java 10 (that WILL require some developers time).
> > >>>> And RPM / DEB packages stage II phase will require lots of testing
> and
> > >>>> infrastructure preparations: place to store package, RPM / DEB build
> > >>>> inclusion into release process and so on.
> > >>>>
> > >>>> Apr 30 sounds good, but I’d have a “place for manoeuvre” in case all
> > >> those
> > >>>> activities are not finished in time.
> > >>>>
> > >>>>
> > >>>>
> > >>>>> On 22 Mar 2018, at 20:39, Denis Magda <[hidden email]> wrote:
> > >>>>>
> > >>>>> Igniters,
> > >>>>>
> > >>>>> According to our regular schedule, every new Ignite version usually
> > >> goes
> > >>>>> public once in 3 months. As you remember, the latest 2.4 release,
> > which
> > >>>>> took us 5 months to improve and roll out, was based on the version
> of
> > >> the
> > >>>>> source code dated by January.
> > >>>>>
> > >>>>> Since that time the master branch went far ahead and already
> > >> incorporates
> > >>>>> many valuable fixes and capabilities such as:
> > >>>>>
> > >>>>> - Fixes provided as a part of "Gree Team City" activity.
> > >>>>> - Persistence: page replacement algorithm and throttling
> > >> optimizations,
> > >>>>> out of memory in checkpointing buffer corrections, etc. Alex G and
> > >>>> Ivan can
> > >>>>> shed more light here.
> > >>>>> - Data loading optimizations for SQL: streaming for JDBC thin
> driver
> > >>>> and
> > >>>>> copy command
> > >>>>> - Genetic Algorithms Grid Contribution!
> > >>>>> - Java Thin Client developed by Alexey Kukushkin
> > >>>>>
> > >>>>>
> > >>>>> - the list goes on and on... Please share the contributions you are
> > >>>>> ready to release.
> > >>>>>
> > >>>>> So, why don't we go ahead and release the current master and
> possibly
> > >>>> extra
> > >>>>> tickets that are in the review state earlier? What's about April 30
> > as
> > >>>> the
> > >>>>> next release date?
> > >>>>>
> > >>>>> --
> > >>>>> Densi
> > >>>>
> > >>>>
> > >>
> > >>
> >
> >
>

[Yuriy Babak]

Hi,

We already implemented LSQR for linear regression and SVM(support vector
machine) algorithms. Also we implement new distributed Datasets.

And we want to adapt all our algorithms to this new dataset API. So from my
point of view we have enough time for those tasks.

So I think that we could release Apache Ignite 2.5 at 30 Apr.

Regards,
Yury



--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[dmagda]

Good, hope that everyone interested has enough time to share an opinion.

As a summary of this discussion, the community decided to release Ignite
2.5 on April 30. Most of the changes and features are already in the master.

Who is ready to become a release manager of 2.5? We need to prepare a
respective wiki page and outline the milestones (code freeze, QA, vote,
release).

--
Denis

On Sat, Mar 24, 2018 at 4:38 PM, Yury Babak <[hidden email]> wrote:

> Hi,
>
> We already implemented LSQR for linear regression and SVM(support vector
> machine) algorithms. Also we implement new distributed Datasets.
>
> And we want to adapt all our algorithms to this new dataset API. So from my
> point of view we have enough time for those tasks.
>
> So I think that we could release Apache Ignite 2.5 at 30 Apr.
>
> Regards,
> Yury
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>

[agura]

Igniters,

I'm ready to take care of Apache Ignite 2.5 release.

I've started preparing wiki pages. There are many fixes in master
branch so I think that we should limit scope of the release soon (e.g.
next week) because stabilization and QA activities will also require
time.
I'll keep the community informed about all release preparation steps.


On Tue, Mar 27, 2018 at 3:07 AM, Denis Magda <[hidden email]> wrote:

> Good, hope that everyone interested has enough time to share an opinion.
>
> As a summary of this discussion, the community decided to release Ignite
> 2.5 on April 30. Most of the changes and features are already in the master.
>
> Who is ready to become a release manager of 2.5? We need to prepare a
> respective wiki page and outline the milestones (code freeze, QA, vote,
> release).
>
> --
> Denis
>
> On Sat, Mar 24, 2018 at 4:38 PM, Yury Babak <[hidden email]> wrote:
>
>> Hi,
>>
>> We already implemented LSQR for linear regression and SVM(support vector
>> machine) algorithms. Also we implement new distributed Datasets.
>>
>> And we want to adapt all our algorithms to this new dataset API. So from my
>> point of view we have enough time for those tasks.
>>
>> So I think that we could release Apache Ignite 2.5 at 30 Apr.
>>
>> Regards,
>> Yury
>>
>>
>>
>> --
>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>

[dmagda]

Andrey, it's great to see you in a role of 2.5 release engineer! Thanks for
stepping in.

--
Denis



On Tue, Mar 27, 2018 at 8:42 AM, Andrey Gura <[hidden email]> wrote:

> Igniters,
>
> I'm ready to take care of Apache Ignite 2.5 release.
>
> I've started preparing wiki pages. There are many fixes in master
> branch so I think that we should limit scope of the release soon (e.g.
> next week) because stabilization and QA activities will also require
> time.
> I'll keep the community informed about all release preparation steps.
>
>
> On Tue, Mar 27, 2018 at 3:07 AM, Denis Magda <[hidden email]> wrote:
> > Good, hope that everyone interested has enough time to share an opinion.
> >
> > As a summary of this discussion, the community decided to release Ignite
> > 2.5 on April 30. Most of the changes and features are already in the
> master.
> >
> > Who is ready to become a release manager of 2.5? We need to prepare a
> > respective wiki page and outline the milestones (code freeze, QA, vote,
> > release).
> >
> > --
> > Denis
> >
> > On Sat, Mar 24, 2018 at 4:38 PM, Yury Babak <[hidden email]> wrote:
> >
> >> Hi,
> >>
> >> We already implemented LSQR for linear regression and SVM(support vector
> >> machine) algorithms. Also we implement new distributed Datasets.
> >>
> >> And we want to adapt all our algorithms to this new dataset API. So
> from my
> >> point of view we have enough time for those tasks.
> >>
> >> So I think that we could release Apache Ignite 2.5 at 30 Apr.
> >>
> >> Regards,
> >> Yury
> >>
> >>
> >>
> >> --
> >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >>
>