subject:"Re\: Re\[4\]\: Apache Ignite 2.7.6 \(Time, Scope, and Release manager\)"

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-17 Thread Zhenya Stanilovsky

I hope there is no data loss here, but index tree corruption can be easily  
obtained.
Impact: someone believe that inline_size has been changed due to index  
recreation but that`s not so.



Hi Evgeniy,

I can't review this change. We need approve of a committer, who is  SQL
expert,  here.

What would be an impact on users if we don' include it into 2.7.6?

Is it a critical/data loss issue? If not, I agree it can wait for 2.8
release.

Sincerely,
Dmitriy Pavlov

сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :


hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
have no clue - why, but seems i can`t merge it without his visa.
thanks.

> Hi Igniters,
>
> I also suggest adding newly created critical bug into scope
> https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> since
> it was discussed before in private communication).
>
> It is not a regression but can cause data corruption, so I'd rather  
wait

> for the fix.
>
> Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first  
RC
> during the weekend, so I would be grateful if fixes can be  
cherry-piked

> to
> the branch today. Also, since narrow time limit, please trigger Run  
All
> after each commit in 2.7.6. This will allow to immediately locate  
which

> commit caused test failure.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>
>> Hi Ivan,
>>
>> yes, sure.
>>
>> If it is cherry-picked without conflicts, just push it.
>>
>>  If it contains conflicts it is better to push to 2.7.6-based branch  
and

>> start additional run-all, example
>> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
>> base: 2.7.6
>>
>> Sincerely,
>> Dmitriy Pavlov
>>
>> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
>>
>>> Dmitriy,
>>>
>>> We accomplished with
https://issues.apache.org/jira/browse/IGNITE-12068
>>>
>>> Should I cherry-pick it to release branch?
>>>
>>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>>> >
>>> > Hi Igniters,
>>> >
>>> > Yesterday was a planned date of code freeze.
>>> >
>>> > So the scope (related both to features and to bugs) is final,  
we're
>>> > entering to stabilization phase. Nothing can be included into  
scope

>>> besides
>>> > blockers approved by the release manager.
>>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>>> >  


>>> >
>>> > Unresolved tickets are:
>>> > IGNITE-12071  Eduard Shangareev
>>> > IGNITE-12068 Ivan Pavlukhin
>>> > IGNITE-9562 Eduard Shangareev
>>> > IGNITE-12057 Anton Kalashnikov
>>> > IGNITE-12061 Stanilovsky Evgeny
>>> >
>>> > Sincerely,
>>> > Dmitriy Pavlov
>>> >
>>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky  

>:
>>> >
>>> > > Dmitriy, review passed, plz proceed.
>>> > > thanks !
>>> > >
>>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
>>> until
>>> > > > nobody
>>> > > > volunteer to complete the task.
>>> > > >
>>> > > > Evgeniy, please keep me updated about IGNITE-12061.
>>> > > >
>>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
>>> > > > >> > > >> :
>>> > > >
>>> > > >> yep, i`l try to call someone who probably familiar with this
>>> problem.
>>> > > >>
>>> > > >> >
>>> > > >> >
>>> > > >> >Ok, I've removed Spark from the scope.
>>> > > >> >
>>> > > >> >What about the unassigned issue related to ODBC? It is not
>>> looking like
>>> > > >> >somebody will fix it before release.
>>> > > >> >
>>> > > >> >Evgeniy Stanilovsky, what about
>>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
>>> > > >> ><
>>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>>> > > >> >do you have someone to review the fix?
>>> > > >> >
>>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
>:
>>> > > >> >
>>> > > >> >> Dmitry,
>>> > > >> >>
>>> > > >> >> It would be better for us to put off the Spark upgrade  
until

>>> 2.8 as
>>> > > >> Nikolay
>>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to  
let

>>> roll out
>>> > > >> fixes
>>> > > >> >> for the critical issues from the scope.
>>> > > >> >>
>>> > > >> >>
>>> > > >> >> -
>>> > > >> >> Denis
>>> > > >> >>
>>> > > >> >>
>>> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
>>> dpav...@apache.org
>>> > > >
>>> > > >> wrote:
>>> > > >> >>
>>> > > >> >> > Nikolay, how long does it take to update? I will be
>>> traveling
>>> > > from
>>> > > >> 28
>>> > > >> Aug
>>> > > >> >> > till 16 Sept. We can select new dates for release if the
>>> majority
>>> > > >> of
>>> > > >> >> fixes
>>> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis,
>>> please
>>> share
>>> > > >> your
>>> > > >> >> > vision about selecting new dates.
>>> > > >> >> >
>>> > > >> >> > *Voting Date: *Sept 18, 2019
>>> > > >> >> >
>>> > > >> >> > *Release Date: *Sept 23, 2019
>>> > > >> >> >
>>> > > >> >> > Issue   
https://issues.apache.org/jira/browse/IGNITE-12032

>>> > > >> >> >

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-17 Thread Dmitriy Pavlov

Hi Evgeniy,

I can't review this change. We need approve of a committer, who is  SQL
expert,  here.

What would be an impact on users if we don' include it into 2.7.6?

Is it a critical/data loss issue? If not, I agree it can wait for 2.8
release.

Sincerely,
Dmitriy Pavlov

сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :

> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i
> have no clue - why, but seems i can`t merge it without his visa.
> thanks.
>
> > Hi Igniters,
> >
> > I also suggest adding newly created critical bug into scope
> > https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> > since
> > it was discussed before in private communication).
> >
> > It is not a regression but can cause data corruption, so I'd rather wait
> > for the fix.
> >
> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
> > during the weekend, so I would be grateful if fixes can be cherry-piked
> > to
> > the branch today. Also, since narrow time limit, please trigger Run All
> > after each commit in 2.7.6. This will allow to immediately locate which
> > commit caused test failure.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
> >
> >> Hi Ivan,
> >>
> >> yes, sure.
> >>
> >> If it is cherry-picked without conflicts, just push it.
> >>
> >>  If it contains conflicts it is better to push to 2.7.6-based branch and
> >> start additional run-all, example
> >> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> >> base: 2.7.6
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> >>
> >>> Dmitriy,
> >>>
> >>> We accomplished with
> https://issues.apache.org/jira/browse/IGNITE-12068
> >>>
> >>> Should I cherry-pick it to release branch?
> >>>
> >>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >>> >
> >>> > Hi Igniters,
> >>> >
> >>> > Yesterday was a planned date of code freeze.
> >>> >
> >>> > So the scope (related both to features and to bugs) is final, we're
> >>> > entering to stabilization phase. Nothing can be included into scope
> >>> besides
> >>> > blockers approved by the release manager.
> >>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >>> > 
> >>> >
> >>> > Unresolved tickets are:
> >>> > IGNITE-12071  Eduard Shangareev
> >>> > IGNITE-12068 Ivan Pavlukhin
> >>> > IGNITE-9562 Eduard Shangareev
> >>> > IGNITE-12057 Anton Kalashnikov
> >>> > IGNITE-12061 Stanilovsky Evgeny
> >>> >
> >>> > Sincerely,
> >>> > Dmitriy Pavlov
> >>> >
> >>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky  >:
> >>> >
> >>> > > Dmitriy, review passed, plz proceed.
> >>> > > thanks !
> >>> > >
> >>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
> >>> until
> >>> > > > nobody
> >>> > > > volunteer to complete the task.
> >>> > > >
> >>> > > > Evgeniy, please keep me updated about IGNITE-12061.
> >>> > > >
> >>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >>> > > >  >>> > > >> :
> >>> > > >
> >>> > > >> yep, i`l try to call someone who probably familiar with this
> >>> problem.
> >>> > > >>
> >>> > > >> >
> >>> > > >> >
> >>> > > >> >Ok, I've removed Spark from the scope.
> >>> > > >> >
> >>> > > >> >What about the unassigned issue related to ODBC? It is not
> >>> looking like
> >>> > > >> >somebody will fix it before release.
> >>> > > >> >
> >>> > > >> >Evgeniy Stanilovsky, what about
> >>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> >>> > > >> ><
> >>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >>> > > >> >do you have someone to review the fix?
> >>> > > >> >
> >>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
> >:
> >>> > > >> >
> >>> > > >> >> Dmitry,
> >>> > > >> >>
> >>> > > >> >> It would be better for us to put off the Spark upgrade until
> >>> 2.8 as
> >>> > > >> Nikolay
> >>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> >>> roll out
> >>> > > >> fixes
> >>> > > >> >> for the critical issues from the scope.
> >>> > > >> >>
> >>> > > >> >>
> >>> > > >> >> -
> >>> > > >> >> Denis
> >>> > > >> >>
> >>> > > >> >>
> >>> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> >>> dpav...@apache.org
> >>> > > >
> >>> > > >> wrote:
> >>> > > >> >>
> >>> > > >> >> > Nikolay, how long does it take to update? I will be
> >>> traveling
> >>> > > from
> >>> > > >> 28
> >>> > > >> Aug
> >>> > > >> >> > till 16 Sept. We can select new dates for release if the
> >>> majority
> >>> > > >> of
> >>> > > >> >> fixes
> >>> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis,
> >>> please
> >>> share
> >>> > > >> your
> >>> > > >> >> > vision about selecting new dates.
> >>> > > >> >> >
> >>> > > >> >> > *Voting Date: *Sept 18, 2019
> >>> > > >> >> >
> >>> > > >> >> > *Release Date: *Sept 23, 2019
> >>> > > >> >> >
> >>> > > >> >> > Issue

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-17 Thread Zhenya Stanilovsky

hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6, i  
have no clue - why, but seems i can`t merge it without his visa.

thanks.


Hi Igniters,

I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned  
since

it was discussed before in private communication).

It is not a regression but can cause data corruption, so I'd rather wait
for the fix.

Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
during the weekend, so I would be grateful if fixes can be cherry-piked  
to

the branch today. Also, since narrow time limit, please trigger Run All
after each commit in 2.7.6. This will allow to immediately locate which
commit caused test failure.

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :


Hi Ivan,

yes, sure.

If it is cherry-picked without conflicts, just push it.

 If it contains conflicts it is better to push to 2.7.6-based branch and
start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
base: 2.7.6

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :


Dmitriy,

We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068

Should I cherry-pick it to release branch?

пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>
> Hi Igniters,
>
> Yesterday was a planned date of code freeze.
>
> So the scope (related both to features and to bugs) is final, we're
> entering to stabilization phase. Nothing can be included into scope
besides
> blockers approved by the release manager.
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> 
>
> Unresolved tickets are:
> IGNITE-12071  Eduard Shangareev
> IGNITE-12068 Ivan Pavlukhin
> IGNITE-9562 Eduard Shangareev
> IGNITE-12057 Anton Kalashnikov
> IGNITE-12061 Stanilovsky Evgeny
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
>
> > Dmitriy, review passed, plz proceed.
> > thanks !
> >
> > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032  
until

> > > nobody
> > > volunteer to complete the task.
> > >
> > > Evgeniy, please keep me updated about IGNITE-12061.
> > >
> > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > >  > >> :
> > >
> > >> yep, i`l try to call someone who probably familiar with this
problem.
> > >>
> > >> >
> > >> >
> > >> >Ok, I've removed Spark from the scope.
> > >> >
> > >> >What about the unassigned issue related to ODBC? It is not
looking like
> > >> >somebody will fix it before release.
> > >> >
> > >> >Evgeniy Stanilovsky, what about
> > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > >> ><
https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >> >do you have someone to review the fix?
> > >> >
> > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > >> >
> > >> >> Dmitry,
> > >> >>
> > >> >> It would be better for us to put off the Spark upgrade until
2.8 as
> > >> Nikolay
> > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
roll out
> > >> fixes
> > >> >> for the critical issues from the scope.
> > >> >>
> > >> >>
> > >> >> -
> > >> >> Denis
> > >> >>
> > >> >>
> > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
dpav...@apache.org
> > >
> > >> wrote:
> > >> >>
> > >> >> > Nikolay, how long does it take to update? I will be  
traveling

> > from
> > >> 28
> > >> Aug
> > >> >> > till 16 Sept. We can select new dates for release if the
majority
> > >> of
> > >> >> fixes
> > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis,  
please

share
> > >> your
> > >> >> > vision about selecting new dates.
> > >> >> >
> > >> >> > *Voting Date: *Sept 18, 2019
> > >> >> >
> > >> >> > *Release Date: *Sept 23, 2019
> > >> >> >
> > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > >> >> > <
https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >
> > >> >
> > >> is
> > >> >> > still
> > >> >> > unassigned: Server node prints exception when ODBC driver
> > >> disconnects
> > >> >> > Igniters, who would like to pick up it? By default, I'm  
going

to
> > >> remove
> > >> >> it
> > >> >> > from release
> > >> >> >
> > >> >> >
> > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
nizhi...@apache.org
> >
> > >> >:
> > >> >> >
> > >> >> > > Hello, Igniters.
> > >> >> > >
> > >> >> > > I try to upgrade Spark version but failed.
> > >> >> > >
> > >> >> > > Seems, internal Spark API(External Catalog, SQL planner)
that
> > we
> > >> use
> > >> >> > > changed a lot.
> > >> >> > > So it will take some time to upgrade version.
> > >> >> > >
> > >> >> > > For now, I work hard to complete the second phase of  
IEP-35

so I
> > >> >> postpone
> > >> >> > > upgrade Spark version to Ignite 2.8.
> > >> >> > >
> > >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > >> >> > > > Hi Denis,
> >

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-17 Thread Dmitriy Pavlov

Hi Ivan,

Thank you so much, Ivan, for contributing this fix after hours.

We have second barrier here - 2.7.6 related to 2.7.5,
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.5

I've triggered one more run for RunAll here.

Sincerely,
Dmitriy Pavlov

сб, 17 авг. 2019 г. в 07:36, Павлухин Иван :

> Dmitriy,
>
> I cherry-picked fix for
> https://issues.apache.org/jira/browse/IGNITE-12068 to 2.7.6. Bot visa
> seems good comparing to 2.7.6 but there are some reported blockers. It
> would be great if someone can double-check it. If something is wrong
> you may consider a revert.
>
> пт, 16 авг. 2019 г. в 18:22, Dmitriy Pavlov :
> >
> > Hi Igniters,
> >
> > I also suggest adding newly created critical bug into scope
> > https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> since
> > it was discussed before in private communication).
> >
> > It is not a regression but can cause data corruption, so I'd rather wait
> > for the fix.
> >
> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
> > during the weekend, so I would be grateful if fixes can be cherry-piked
> to
> > the branch today. Also, since narrow time limit, please trigger Run All
> > after each commit in 2.7.6. This will allow to immediately locate which
> > commit caused test failure.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
> >
> > > Hi Ivan,
> > >
> > > yes, sure.
> > >
> > > If it is cherry-picked without conflicts, just push it.
> > >
> > >  If it contains conflicts it is better to push to 2.7.6-based branch
> and
> > > start additional run-all, example
> > > https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> > > base: 2.7.6
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> > >
> > >> Dmitriy,
> > >>
> > >> We accomplished with
> https://issues.apache.org/jira/browse/IGNITE-12068
> > >>
> > >> Should I cherry-pick it to release branch?
> > >>
> > >> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> > >> >
> > >> > Hi Igniters,
> > >> >
> > >> > Yesterday was a planned date of code freeze.
> > >> >
> > >> > So the scope (related both to features and to bugs) is final, we're
> > >> > entering to stabilization phase. Nothing can be included into scope
> > >> besides
> > >> > blockers approved by the release manager.
> > >> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >> >  >
> > >> >
> > >> > Unresolved tickets are:
> > >> > IGNITE-12071  Eduard Shangareev
> > >> > IGNITE-12068 Ivan Pavlukhin
> > >> > IGNITE-9562 Eduard Shangareev
> > >> > IGNITE-12057 Anton Kalashnikov
> > >> > IGNITE-12061 Stanilovsky Evgeny
> > >> >
> > >> > Sincerely,
> > >> > Dmitriy Pavlov
> > >> >
> > >> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky  >:
> > >> >
> > >> > > Dmitriy, review passed, plz proceed.
> > >> > > thanks !
> > >> > >
> > >> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032
> until
> > >> > > > nobody
> > >> > > > volunteer to complete the task.
> > >> > > >
> > >> > > > Evgeniy, please keep me updated about IGNITE-12061.
> > >> > > >
> > >> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > >> > > >  > >> > > >> :
> > >> > > >
> > >> > > >> yep, i`l try to call someone who probably familiar with this
> > >> problem.
> > >> > > >>
> > >> > > >> >
> > >> > > >> >
> > >> > > >> >Ok, I've removed Spark from the scope.
> > >> > > >> >
> > >> > > >> >What about the unassigned issue related to ODBC? It is not
> > >> looking like
> > >> > > >> >somebody will fix it before release.
> > >> > > >> >
> > >> > > >> >Evgeniy Stanilovsky, what about
> > >> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > >> > > >> ><
> > >> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >> > > >> >do you have someone to review the fix?
> > >> > > >> >
> > >> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org
> >:
> > >> > > >> >
> > >> > > >> >> Dmitry,
> > >> > > >> >>
> > >> > > >> >> It would be better for us to put off the Spark upgrade until
> > >> 2.8 as
> > >> > > >> Nikolay
> > >> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> > >> roll out
> > >> > > >> fixes
> > >> > > >> >> for the critical issues from the scope.
> > >> > > >> >>
> > >> > > >> >>
> > >> > > >> >> -
> > >> > > >> >> Denis
> > >> > > >> >>
> > >> > > >> >>
> > >> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> > >> dpav...@apache.org
> > >> > > >
> > >> > > >> wrote:
> > >> > > >> >>
> > >> > > >> >> > Nikolay, how long does it take to update? I will be
> traveling
> > >> > > from
> > >> > > >> 28
> > >> > > >> Aug
> > >> > > >> >> > till 16 Sept. We can select new dates for release if the
> > >> majority
> > >> > > >> of
> > >> > > >> >> fixes
> > >> > > >> >> > can be

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Павлухин Иван

Dmitriy,

I cherry-picked fix for
https://issues.apache.org/jira/browse/IGNITE-12068 to 2.7.6. Bot visa
seems good comparing to 2.7.6 but there are some reported blockers. It
would be great if someone can double-check it. If something is wrong
you may consider a revert.

пт, 16 авг. 2019 г. в 18:22, Dmitriy Pavlov :
>
> Hi Igniters,
>
> I also suggest adding newly created critical bug into scope
> https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned since
> it was discussed before in private communication).
>
> It is not a regression but can cause data corruption, so I'd rather wait
> for the fix.
>
> Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
> during the weekend, so I would be grateful if fixes can be cherry-piked to
> the branch today. Also, since narrow time limit, please trigger Run All
> after each commit in 2.7.6. This will allow to immediately locate which
> commit caused test failure.
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>
> > Hi Ivan,
> >
> > yes, sure.
> >
> > If it is cherry-picked without conflicts, just push it.
> >
> >  If it contains conflicts it is better to push to 2.7.6-based branch and
> > start additional run-all, example
> > https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> > base: 2.7.6
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> >
> >> Dmitriy,
> >>
> >> We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
> >>
> >> Should I cherry-pick it to release branch?
> >>
> >> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >> >
> >> > Hi Igniters,
> >> >
> >> > Yesterday was a planned date of code freeze.
> >> >
> >> > So the scope (related both to features and to bugs) is final, we're
> >> > entering to stabilization phase. Nothing can be included into scope
> >> besides
> >> > blockers approved by the release manager.
> >> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >> > 
> >> >
> >> > Unresolved tickets are:
> >> > IGNITE-12071  Eduard Shangareev
> >> > IGNITE-12068 Ivan Pavlukhin
> >> > IGNITE-9562 Eduard Shangareev
> >> > IGNITE-12057 Anton Kalashnikov
> >> > IGNITE-12061 Stanilovsky Evgeny
> >> >
> >> > Sincerely,
> >> > Dmitriy Pavlov
> >> >
> >> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
> >> >
> >> > > Dmitriy, review passed, plz proceed.
> >> > > thanks !
> >> > >
> >> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> >> > > > nobody
> >> > > > volunteer to complete the task.
> >> > > >
> >> > > > Evgeniy, please keep me updated about IGNITE-12061.
> >> > > >
> >> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >> > > >  >> > > >> :
> >> > > >
> >> > > >> yep, i`l try to call someone who probably familiar with this
> >> problem.
> >> > > >>
> >> > > >> >
> >> > > >> >
> >> > > >> >Ok, I've removed Spark from the scope.
> >> > > >> >
> >> > > >> >What about the unassigned issue related to ODBC? It is not
> >> looking like
> >> > > >> >somebody will fix it before release.
> >> > > >> >
> >> > > >> >Evgeniy Stanilovsky, what about
> >> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> >> > > >> ><
> >> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >> > > >> >do you have someone to review the fix?
> >> > > >> >
> >> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> >> > > >> >
> >> > > >> >> Dmitry,
> >> > > >> >>
> >> > > >> >> It would be better for us to put off the Spark upgrade until
> >> 2.8 as
> >> > > >> Nikolay
> >> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> >> roll out
> >> > > >> fixes
> >> > > >> >> for the critical issues from the scope.
> >> > > >> >>
> >> > > >> >>
> >> > > >> >> -
> >> > > >> >> Denis
> >> > > >> >>
> >> > > >> >>
> >> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> >> dpav...@apache.org
> >> > > >
> >> > > >> wrote:
> >> > > >> >>
> >> > > >> >> > Nikolay, how long does it take to update? I will be traveling
> >> > > from
> >> > > >> 28
> >> > > >> Aug
> >> > > >> >> > till 16 Sept. We can select new dates for release if the
> >> majority
> >> > > >> of
> >> > > >> >> fixes
> >> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please
> >> share
> >> > > >> your
> >> > > >> >> > vision about selecting new dates.
> >> > > >> >> >
> >> > > >> >> > *Voting Date: *Sept 18, 2019
> >> > > >> >> >
> >> > > >> >> > *Release Date: *Sept 23, 2019
> >> > > >> >> >
> >> > > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> >> > > >> >> > <
> >> https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >> > >
> >> > > >> >
> >> > > >> is
> >> > > >> >> > still
> >> > > >> >> > unassigned: Server node prints exception when ODBC driver
> >> > > >> disconnects
> >> > > >> >> > Igniters, who would like to pick

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Dmitriy Pavlov

Hi Igniters,

I also suggest adding newly created critical bug into scope
https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned since
it was discussed before in private communication).

It is not a regression but can cause data corruption, so I'd rather wait
for the fix.

Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the first RC
during the weekend, so I would be grateful if fixes can be cherry-piked to
the branch today. Also, since narrow time limit, please trigger Run All
after each commit in 2.7.6. This will allow to immediately locate which
commit caused test failure.

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :

> Hi Ivan,
>
> yes, sure.
>
> If it is cherry-picked without conflicts, just push it.
>
>  If it contains conflicts it is better to push to 2.7.6-based branch and
> start additional run-all, example
> https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562,
> base: 2.7.6
>
> Sincerely,
> Dmitriy Pavlov
>
> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
>
>> Dmitriy,
>>
>> We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
>>
>> Should I cherry-pick it to release branch?
>>
>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>> >
>> > Hi Igniters,
>> >
>> > Yesterday was a planned date of code freeze.
>> >
>> > So the scope (related both to features and to bugs) is final, we're
>> > entering to stabilization phase. Nothing can be included into scope
>> besides
>> > blockers approved by the release manager.
>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>> > 
>> >
>> > Unresolved tickets are:
>> > IGNITE-12071  Eduard Shangareev
>> > IGNITE-12068 Ivan Pavlukhin
>> > IGNITE-9562 Eduard Shangareev
>> > IGNITE-12057 Anton Kalashnikov
>> > IGNITE-12061 Stanilovsky Evgeny
>> >
>> > Sincerely,
>> > Dmitriy Pavlov
>> >
>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
>> >
>> > > Dmitriy, review passed, plz proceed.
>> > > thanks !
>> > >
>> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
>> > > > nobody
>> > > > volunteer to complete the task.
>> > > >
>> > > > Evgeniy, please keep me updated about IGNITE-12061.
>> > > >
>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
>> > > > > > > >> :
>> > > >
>> > > >> yep, i`l try to call someone who probably familiar with this
>> problem.
>> > > >>
>> > > >> >
>> > > >> >
>> > > >> >Ok, I've removed Spark from the scope.
>> > > >> >
>> > > >> >What about the unassigned issue related to ODBC? It is not
>> looking like
>> > > >> >somebody will fix it before release.
>> > > >> >
>> > > >> >Evgeniy Stanilovsky, what about
>> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
>> > > >> ><
>> https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>> > > >> >do you have someone to review the fix?
>> > > >> >
>> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
>> > > >> >
>> > > >> >> Dmitry,
>> > > >> >>
>> > > >> >> It would be better for us to put off the Spark upgrade until
>> 2.8 as
>> > > >> Nikolay
>> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
>> roll out
>> > > >> fixes
>> > > >> >> for the critical issues from the scope.
>> > > >> >>
>> > > >> >>
>> > > >> >> -
>> > > >> >> Denis
>> > > >> >>
>> > > >> >>
>> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
>> dpav...@apache.org
>> > > >
>> > > >> wrote:
>> > > >> >>
>> > > >> >> > Nikolay, how long does it take to update? I will be traveling
>> > > from
>> > > >> 28
>> > > >> Aug
>> > > >> >> > till 16 Sept. We can select new dates for release if the
>> majority
>> > > >> of
>> > > >> >> fixes
>> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please
>> share
>> > > >> your
>> > > >> >> > vision about selecting new dates.
>> > > >> >> >
>> > > >> >> > *Voting Date: *Sept 18, 2019
>> > > >> >> >
>> > > >> >> > *Release Date: *Sept 23, 2019
>> > > >> >> >
>> > > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
>> > > >> >> > <
>> https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
>> > >
>> > > >> >
>> > > >> is
>> > > >> >> > still
>> > > >> >> > unassigned: Server node prints exception when ODBC driver
>> > > >> disconnects
>> > > >> >> > Igniters, who would like to pick up it? By default, I'm going
>> to
>> > > >> remove
>> > > >> >> it
>> > > >> >> > from release
>> > > >> >> >
>> > > >> >> >
>> > > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
>> nizhi...@apache.org
>> > >
>> > > >> >:
>> > > >> >> >
>> > > >> >> > > Hello, Igniters.
>> > > >> >> > >
>> > > >> >> > > I try to upgrade Spark version but failed.
>> > > >> >> > >
>> > > >> >> > > Seems, internal Spark API(External Catalog, SQL planner)
>> that
>> > > we
>> > > >> use
>> > > >> >> > > changed a lot.
>> > > >> >> > > So it will take some time to upgrade version.
>> > > >> >> > >
>> > > >> >> >

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Dmitriy Pavlov

Hi Ivan,

yes, sure.

If it is cherry-picked without conflicts, just push it.

 If it contains conflicts it is better to push to 2.7.6-based branch and
start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for ignite-9562, base:
2.7.6

Sincerely,
Dmitriy Pavlov

пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :

> Dmitriy,
>
> We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068
>
> Should I cherry-pick it to release branch?
>
> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >
> > Hi Igniters,
> >
> > Yesterday was a planned date of code freeze.
> >
> > So the scope (related both to features and to bugs) is final, we're
> > entering to stabilization phase. Nothing can be included into scope
> besides
> > blockers approved by the release manager.
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > 
> >
> > Unresolved tickets are:
> > IGNITE-12071  Eduard Shangareev
> > IGNITE-12068 Ivan Pavlukhin
> > IGNITE-9562 Eduard Shangareev
> > IGNITE-12057 Anton Kalashnikov
> > IGNITE-12061 Stanilovsky Evgeny
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
> >
> > > Dmitriy, review passed, plz proceed.
> > > thanks !
> > >
> > > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> > > > nobody
> > > > volunteer to complete the task.
> > > >
> > > > Evgeniy, please keep me updated about IGNITE-12061.
> > > >
> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > > >  > > >> :
> > > >
> > > >> yep, i`l try to call someone who probably familiar with this
> problem.
> > > >>
> > > >> >
> > > >> >
> > > >> >Ok, I've removed Spark from the scope.
> > > >> >
> > > >> >What about the unassigned issue related to ODBC? It is not looking
> like
> > > >> >somebody will fix it before release.
> > > >> >
> > > >> >Evgeniy Stanilovsky, what about
> > > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > > >> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro
> >
> > > >> >do you have someone to review the fix?
> > > >> >
> > > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > > >> >
> > > >> >> Dmitry,
> > > >> >>
> > > >> >> It would be better for us to put off the Spark upgrade until 2.8
> as
> > > >> Nikolay
> > > >> >> suggested. Let's release 2.7.6 as quickly as possible to let
> roll out
> > > >> fixes
> > > >> >> for the critical issues from the scope.
> > > >> >>
> > > >> >>
> > > >> >> -
> > > >> >> Denis
> > > >> >>
> > > >> >>
> > > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov <
> dpav...@apache.org
> > > >
> > > >> wrote:
> > > >> >>
> > > >> >> > Nikolay, how long does it take to update? I will be traveling
> > > from
> > > >> 28
> > > >> Aug
> > > >> >> > till 16 Sept. We can select new dates for release if the
> majority
> > > >> of
> > > >> >> fixes
> > > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please
> share
> > > >> your
> > > >> >> > vision about selecting new dates.
> > > >> >> >
> > > >> >> > *Voting Date: *Sept 18, 2019
> > > >> >> >
> > > >> >> > *Release Date: *Sept 23, 2019
> > > >> >> >
> > > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > > >> >> > <
> https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> > >
> > > >> >
> > > >> is
> > > >> >> > still
> > > >> >> > unassigned: Server node prints exception when ODBC driver
> > > >> disconnects
> > > >> >> > Igniters, who would like to pick up it? By default, I'm going
> to
> > > >> remove
> > > >> >> it
> > > >> >> > from release
> > > >> >> >
> > > >> >> >
> > > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov <
> nizhi...@apache.org
> > >
> > > >> >:
> > > >> >> >
> > > >> >> > > Hello, Igniters.
> > > >> >> > >
> > > >> >> > > I try to upgrade Spark version but failed.
> > > >> >> > >
> > > >> >> > > Seems, internal Spark API(External Catalog, SQL planner) that
> > > we
> > > >> use
> > > >> >> > > changed a lot.
> > > >> >> > > So it will take some time to upgrade version.
> > > >> >> > >
> > > >> >> > > For now, I work hard to complete the second phase of IEP-35
> so I
> > > >> >> postpone
> > > >> >> > > upgrade Spark version to Ignite 2.8.
> > > >> >> > >
> > > >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > > >> >> > > > Hi Denis,
> > > >> >> > > >
> > > >> >> > > > Sure, since code freeze is planned for today, I don't mind
> to
> > > >> include
> > > >> >> > > this
> > > >> >> > > > bug.
> > > >> >> > > >
> > > >> >> > > > Ivan, could you complete this issue by 20 August?
> > > >> >> > > >
> > > >> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> > > >> >> > > >
> > > >> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> > > >> >> > > >
> > > >> >> > > > BTW #2, FYI, release page is now available here
> > > >> >> > > >
> > > >> >>
> > > >>
>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Павлухин Иван

Dmitriy,

We accomplished with https://issues.apache.org/jira/browse/IGNITE-12068

Should I cherry-pick it to release branch?

пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
>
> Hi Igniters,
>
> Yesterday was a planned date of code freeze.
>
> So the scope (related both to features and to bugs) is final, we're
> entering to stabilization phase. Nothing can be included into scope besides
> blockers approved by the release manager.
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> 
>
> Unresolved tickets are:
> IGNITE-12071  Eduard Shangareev
> IGNITE-12068 Ivan Pavlukhin
> IGNITE-9562 Eduard Shangareev
> IGNITE-12057 Anton Kalashnikov
> IGNITE-12061 Stanilovsky Evgeny
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :
>
> > Dmitriy, review passed, plz proceed.
> > thanks !
> >
> > > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> > > nobody
> > > volunteer to complete the task.
> > >
> > > Evgeniy, please keep me updated about IGNITE-12061.
> > >
> > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> > >  > >> :
> > >
> > >> yep, i`l try to call someone who probably familiar with this problem.
> > >>
> > >> >
> > >> >
> > >> >Ok, I've removed Spark from the scope.
> > >> >
> > >> >What about the unassigned issue related to ODBC? It is not looking like
> > >> >somebody will fix it before release.
> > >> >
> > >> >Evgeniy Stanilovsky, what about
> > >> >https://issues.apache.org/jira/browse/IGNITE-12061
> > >> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >> >do you have someone to review the fix?
> > >> >
> > >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > >> >
> > >> >> Dmitry,
> > >> >>
> > >> >> It would be better for us to put off the Spark upgrade until 2.8 as
> > >> Nikolay
> > >> >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> > >> fixes
> > >> >> for the critical issues from the scope.
> > >> >>
> > >> >>
> > >> >> -
> > >> >> Denis
> > >> >>
> > >> >>
> > >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org
> > >
> > >> wrote:
> > >> >>
> > >> >> > Nikolay, how long does it take to update? I will be traveling
> > from
> > >> 28
> > >> Aug
> > >> >> > till 16 Sept. We can select new dates for release if the majority
> > >> of
> > >> >> fixes
> > >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> > >> your
> > >> >> > vision about selecting new dates.
> > >> >> >
> > >> >> > *Voting Date: *Sept 18, 2019
> > >> >> >
> > >> >> > *Release Date: *Sept 23, 2019
> > >> >> >
> > >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > >> >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >
> > >> >
> > >> is
> > >> >> > still
> > >> >> > unassigned: Server node prints exception when ODBC driver
> > >> disconnects
> > >> >> > Igniters, who would like to pick up it? By default, I'm going to
> > >> remove
> > >> >> it
> > >> >> > from release
> > >> >> >
> > >> >> >
> > >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org
> >
> > >> >:
> > >> >> >
> > >> >> > > Hello, Igniters.
> > >> >> > >
> > >> >> > > I try to upgrade Spark version but failed.
> > >> >> > >
> > >> >> > > Seems, internal Spark API(External Catalog, SQL planner) that
> > we
> > >> use
> > >> >> > > changed a lot.
> > >> >> > > So it will take some time to upgrade version.
> > >> >> > >
> > >> >> > > For now, I work hard to complete the second phase of IEP-35 so I
> > >> >> postpone
> > >> >> > > upgrade Spark version to Ignite 2.8.
> > >> >> > >
> > >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > >> >> > > > Hi Denis,
> > >> >> > > >
> > >> >> > > > Sure, since code freeze is planned for today, I don't mind to
> > >> include
> > >> >> > > this
> > >> >> > > > bug.
> > >> >> > > >
> > >> >> > > > Ivan, could you complete this issue by 20 August?
> > >> >> > > >
> > >> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> > >> >> > > >
> > >> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> > >> >> > > >
> > >> >> > > > BTW #2, FYI, release page is now available here
> > >> >> > > >
> > >> >>
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> > >> >> > > >
> > >> >> > > > BTW #3, FYI, release related test PR is here
> > >> >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> > >> report is
> > >> >> > > here:
> > >> >> > > >
> > >> >> > >
> > >> >> >
> > >> >>
> > >>
> > https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org
> > >:
> > >> >> > > >
> > >> >> > > > > An Ignite user just reported a silly issue that needs to be
> > >> fixed
> > >> >> in
> > >> >>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-16 Thread Dmitriy Pavlov

Hi Igniters,

Yesterday was a planned date of code freeze.

So the scope (related both to features and to bugs) is final, we're
entering to stabilization phase. Nothing can be included into scope besides
blockers approved by the release manager.
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process


Unresolved tickets are:
IGNITE-12071  Eduard Shangareev
IGNITE-12068 Ivan Pavlukhin
IGNITE-9562 Eduard Shangareev
IGNITE-12057 Anton Kalashnikov
IGNITE-12061 Stanilovsky Evgeny

Sincerely,
Dmitriy Pavlov

чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky :

> Dmitriy, review passed, plz proceed.
> thanks !
>
> > I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until
> > nobody
> > volunteer to complete the task.
> >
> > Evgeniy, please keep me updated about IGNITE-12061.
> >
> > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >  >> :
> >
> >> yep, i`l try to call someone who probably familiar with this problem.
> >>
> >> >
> >> >
> >> >Ok, I've removed Spark from the scope.
> >> >
> >> >What about the unassigned issue related to ODBC? It is not looking like
> >> >somebody will fix it before release.
> >> >
> >> >Evgeniy Stanilovsky, what about
> >> >https://issues.apache.org/jira/browse/IGNITE-12061
> >> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >> >do you have someone to review the fix?
> >> >
> >> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> >> >
> >> >> Dmitry,
> >> >>
> >> >> It would be better for us to put off the Spark upgrade until 2.8 as
> >> Nikolay
> >> >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> >> fixes
> >> >> for the critical issues from the scope.
> >> >>
> >> >>
> >> >> -
> >> >> Denis
> >> >>
> >> >>
> >> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org
> >
> >> wrote:
> >> >>
> >> >> > Nikolay, how long does it take to update? I will be traveling
> from
> >> 28
> >> Aug
> >> >> > till 16 Sept. We can select new dates for release if the majority
> >> of
> >> >> fixes
> >> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> >> your
> >> >> > vision about selecting new dates.
> >> >> >
> >> >> > *Voting Date: *Sept 18, 2019
> >> >> >
> >> >> > *Release Date: *Sept 23, 2019
> >> >> >
> >> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> >> >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
>
> >> >
> >> is
> >> >> > still
> >> >> > unassigned: Server node prints exception when ODBC driver
> >> disconnects
> >> >> > Igniters, who would like to pick up it? By default, I'm going to
> >> remove
> >> >> it
> >> >> > from release
> >> >> >
> >> >> >
> >> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org
>
> >> >:
> >> >> >
> >> >> > > Hello, Igniters.
> >> >> > >
> >> >> > > I try to upgrade Spark version but failed.
> >> >> > >
> >> >> > > Seems, internal Spark API(External Catalog, SQL planner) that
> we
> >> use
> >> >> > > changed a lot.
> >> >> > > So it will take some time to upgrade version.
> >> >> > >
> >> >> > > For now, I work hard to complete the second phase of IEP-35 so I
> >> >> postpone
> >> >> > > upgrade Spark version to Ignite 2.8.
> >> >> > >
> >> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> >> >> > > > Hi Denis,
> >> >> > > >
> >> >> > > > Sure, since code freeze is planned for today, I don't mind to
> >> include
> >> >> > > this
> >> >> > > > bug.
> >> >> > > >
> >> >> > > > Ivan, could you complete this issue by 20 August?
> >> >> > > >
> >> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> >> >> > > >
> >> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> >> >> > > >
> >> >> > > > BTW #2, FYI, release page is now available here
> >> >> > > >
> >> >>
> >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> >> >> > > >
> >> >> > > > BTW #3, FYI, release related test PR is here
> >> >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> >> report is
> >> >> > > here:
> >> >> > > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> >> >> > > >
> >> >> > > >
> >> >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org
> >:
> >> >> > > >
> >> >> > > > > An Ignite user just reported a silly issue that needs to be
> >> fixed
> >> >> in
> >> >> > > 2.7.6:
> >> >> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
> >> >> > > > >
> >> >> > > > > More details and context:
> >> >> > > > >
> >> >> > > > >
> >> >> > >
> >> >> >
> >> >>
> >>
> https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
> >> >> > > > >
> >> >> > > > > Ivan, please help us to make it to the release.
> >> >> > > > >
> >> >> > > > > -
> >> >> > > > > Denis
> >> >> > > > >
> >> >> > > > >
> >> >> > >

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-15 Thread Zhenya Stanilovsky


Dmitriy, review passed, plz proceed.
thanks !

I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until  
nobody

volunteer to complete the task.

Evgeniy, please keep me updated about IGNITE-12061.

чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky  

:



yep, i`l try to call someone who probably familiar with this problem.

>
>
>Ok, I've removed Spark from the scope.
>
>What about the unassigned issue related to ODBC? It is not looking like
>somebody will fix it before release.
>
>Evgeniy Stanilovsky, what about
>https://issues.apache.org/jira/browse/IGNITE-12061
>< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>do you have someone to review the fix?
>
>чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
>
>> Dmitry,
>>
>> It would be better for us to put off the Spark upgrade until 2.8 as
Nikolay
>> suggested. Let's release 2.7.6 as quickly as possible to let roll out
fixes
>> for the critical issues from the scope.
>>
>>
>> -
>> Denis
>>
>>
>> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org >
wrote:
>>
>> > Nikolay, how long does it take to update? I will be traveling from  
28

Aug
>> > till 16 Sept. We can select new dates for release if the majority  
of

>> fixes
>> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
your
>> > vision about selecting new dates.
>> >
>> > *Voting Date: *Sept 18, 2019
>> >
>> > *Release Date: *Sept 23, 2019
>> >
>> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
>> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro  
>

is
>> > still
>> > unassigned: Server node prints exception when ODBC driver  
disconnects

>> > Igniters, who would like to pick up it? By default, I'm going to
remove
>> it
>> > from release
>> >
>> >
>> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org  
>:

>> >
>> > > Hello, Igniters.
>> > >
>> > > I try to upgrade Spark version but failed.
>> > >
>> > > Seems, internal Spark API(External Catalog, SQL planner) that we  
use

>> > > changed a lot.
>> > > So it will take some time to upgrade version.
>> > >
>> > > For now, I work hard to complete the second phase of IEP-35 so I
>> postpone
>> > > upgrade Spark version to Ignite 2.8.
>> > >
>> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
>> > > > Hi Denis,
>> > > >
>> > > > Sure, since code freeze is planned for today, I don't mind to
include
>> > > this
>> > > > bug.
>> > > >
>> > > > Ivan, could you complete this issue by 20 August?
>> > > >
>> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
>> > > >   
https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro

>> > > >
>> > > > BTW #2, FYI, release page is now available here
>> > > >
>>   
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6

>> > > >
>> > > > BTW #3, FYI, release related test PR is here
>> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
report is
>> > > here:
>> > > >
>> > >
>> >
>>
https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
>> > > >
>> > > >
>> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org >:
>> > > >
>> > > > > An Ignite user just reported a silly issue that needs to be
fixed
>> in
>> > > 2.7.6:
>> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
>> > > > >
>> > > > > More details and context:
>> > > > >
>> > > > >
>> > >
>> >
>>
https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
>> > > > >
>> > > > > Ivan, please help us to make it to the release.
>> > > > >
>> > > > > -
>> > > > > Denis
>> > > > >
>> > > > >
>> > > > > On Tue, Aug 13, 2019 at 6:47 AM Denis Magda <  
dma...@apache.org

>
>> > wrote:
>> > > > >
>> > > > > > IGNITE-12507 (Persistence files are stored to temp dir) has
>> > > definitely be
>> > > > > > added the scope and treated one of the main release  
drivers.

>> > > > > >
>> > > > > > Dmitry, please let us know once the release wiki page is
ready so
>> > > that we
>> > > > > > can finalize the timelines based on chosen scope.
>> > > > > >
>> > > > > > -
>> > > > > > Denis
>> > > > > >
>> > > > > >
>> > > > > > On Mon, Aug 12, 2019 at 7:12 PM Dmitriy Pavlov <
>>  dpav...@apache.org
>> > >
>> > > > >
>> > > > > wrote:
>> > > > > >
>> > > > > > > Hi,
>> > > > > > >
>> > > > > > > Thanks to everyone, who participated in the discussion.
>> > > > > > >
>> > > > > > > I would like to wait also fix for
>> > > > > > >  https://issues.apache.org/jira/browse/IGNITE-12057
>> > > > > > >
>> > > > > > > and discussion results for that issue:
>> > > > > > >
>> > > > > > >
>> > > > >
>> > > > >
>> > >
>> >
>>
https://lists.apache.org/thread.html/498a14b3971950a45ef57f45cc23d2438ce1afba000b586e230927bf@%3Cdev.ignite.apache.org%3E
>> > > > > > >
>> > > > > > >
>> > > > > > > Since some issues are still open, we'll probably move  
some

>> dates
>> > > > >
>> > > > > forward,
>> > > > > > >

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-15 Thread Dmitriy Pavlov

Sorry, it was too easy to do, no need to ask Maxim.

Cherry-picked to 2.7.6,
https://github.com/apache/ignite/commit/891e49fe1eeb28bc6b655024086c3f4d1324fda4

чт, 15 авг. 2019 г. в 19:02, Dmitriy Pavlov :

> Hi Ilya,
>
> I bypassed this problem in the Tc bot by
> "triggerBuild": true,
> "triggerBuildQuietPeriod": 480,  //triggering quiet period in minutes, 2
> builds per day
> "triggerParameters": [
>   {
> "name": "reverse.dep.*.IGNITE_LOGGING_OPTS",
> "value": "-DIGNITE_QUIET=false"
>   }
> ]
>
> But if is test code only, and Maxim would port it, it is a good thing to
> be there.
>
> Maxim, would you do it?
>
> Sincerely,
> Dmitriy Pavlov
>
> чт, 15 авг. 2019 г. в 18:56, Ilya Kasnacheev :
>
>> Hello!
>>
>> I suggest also including IGNITE-11736, otherwise we are going to run into
>> problems each time TC is invoked.
>>
>> https://issues.apache.org/jira/browse/IGNITE-11736
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
>> > >:
>>
>> > yep, i`l try to call someone who probably familiar with this problem.
>> >
>> > >
>> > >
>> > >Ok, I've removed Spark from the scope.
>> > >
>> > >What about the unassigned issue related to ODBC? It is not looking like
>> > >somebody will fix it before release.
>> > >
>> > >Evgeniy Stanilovsky, what about
>> > >https://issues.apache.org/jira/browse/IGNITE-12061
>> > >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
>> > >do you have someone to review the fix?
>> > >
>> > >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
>> > >
>> > >> Dmitry,
>> > >>
>> > >> It would be better for us to put off the Spark upgrade until 2.8 as
>> > Nikolay
>> > >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
>> > fixes
>> > >> for the critical issues from the scope.
>> > >>
>> > >>
>> > >> -
>> > >> Denis
>> > >>
>> > >>
>> > >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org
>> >
>> > wrote:
>> > >>
>> > >> > Nikolay, how long does it take to update? I will be traveling from
>> 28
>> > Aug
>> > >> > till 16 Sept. We can select new dates for release if the majority
>> of
>> > >> fixes
>> > >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
>> > your
>> > >> > vision about selecting new dates.
>> > >> >
>> > >> > *Voting Date: *Sept 18, 2019
>> > >> >
>> > >> > *Release Date: *Sept 23, 2019
>> > >> >
>> > >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
>> > >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
>> >
>> > is
>> > >> > still
>> > >> > unassigned: Server node prints exception when ODBC driver
>> disconnects
>> > >> > Igniters, who would like to pick up it? By default, I'm going to
>> > remove
>> > >> it
>> > >> > from release
>> > >> >
>> > >> >
>> > >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org
>> >:
>> > >> >
>> > >> > > Hello, Igniters.
>> > >> > >
>> > >> > > I try to upgrade Spark version but failed.
>> > >> > >
>> > >> > > Seems, internal Spark API(External Catalog, SQL planner) that we
>> use
>> > >> > > changed a lot.
>> > >> > > So it will take some time to upgrade version.
>> > >> > >
>> > >> > > For now, I work hard to complete the second phase of IEP-35 so I
>> > >> postpone
>> > >> > > upgrade Spark version to Ignite 2.8.
>> > >> > >
>> > >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
>> > >> > > > Hi Denis,
>> > >> > > >
>> > >> > > > Sure, since code freeze is planned for today, I don't mind to
>> > include
>> > >> > > this
>> > >> > > > bug.
>> > >> > > >
>> > >> > > > Ivan, could you complete this issue by 20 August?
>> > >> > > >
>> > >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
>> > >> > > >
>> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
>> > >> > > >
>> > >> > > > BTW #2, FYI, release page is now available here
>> > >> > > >
>> > >>
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
>> > >> > > >
>> > >> > > > BTW #3, FYI, release related test PR is here
>> > >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
>> > report is
>> > >> > > here:
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
>> > >> > > >
>> > >> > > >
>> > >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org
>> >:
>> > >> > > >
>> > >> > > > > An Ignite user just reported a silly issue that needs to be
>> > fixed
>> > >> in
>> > >> > > 2.7.6:
>> > >> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
>> > >> > > > >
>> > >> > > > > More details and context:
>> > >> > > > >
>> > >> > > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
>> > >> > > > >
>> > >> > > > > Ivan, please help us to make it to the release.
>> > >> > > > >
>> > >> > > > > -
>> > >> > > > > Denis
>>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-15 Thread Dmitriy Pavlov

Hi Ilya,

I bypassed this problem in the Tc bot by
"triggerBuild": true,
"triggerBuildQuietPeriod": 480,  //triggering quiet period in minutes, 2
builds per day
"triggerParameters": [
  {
"name": "reverse.dep.*.IGNITE_LOGGING_OPTS",
"value": "-DIGNITE_QUIET=false"
  }
]

But if is test code only, and Maxim would port it, it is a good thing to be
there.

Maxim, would you do it?

Sincerely,
Dmitriy Pavlov

чт, 15 авг. 2019 г. в 18:56, Ilya Kasnacheev :

> Hello!
>
> I suggest also including IGNITE-11736, otherwise we are going to run into
> problems each time TC is invoked.
>
> https://issues.apache.org/jira/browse/IGNITE-11736
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky  >:
>
> > yep, i`l try to call someone who probably familiar with this problem.
> >
> > >
> > >
> > >Ok, I've removed Spark from the scope.
> > >
> > >What about the unassigned issue related to ODBC? It is not looking like
> > >somebody will fix it before release.
> > >
> > >Evgeniy Stanilovsky, what about
> > >https://issues.apache.org/jira/browse/IGNITE-12061
> > >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> > >do you have someone to review the fix?
> > >
> > >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> > >
> > >> Dmitry,
> > >>
> > >> It would be better for us to put off the Spark upgrade until 2.8 as
> > Nikolay
> > >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> > fixes
> > >> for the critical issues from the scope.
> > >>
> > >>
> > >> -
> > >> Denis
> > >>
> > >>
> > >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org >
> > wrote:
> > >>
> > >> > Nikolay, how long does it take to update? I will be traveling from
> 28
> > Aug
> > >> > till 16 Sept. We can select new dates for release if the majority of
> > >> fixes
> > >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> > your
> > >> > vision about selecting new dates.
> > >> >
> > >> > *Voting Date: *Sept 18, 2019
> > >> >
> > >> > *Release Date: *Sept 23, 2019
> > >> >
> > >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> > >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro
> >
> > is
> > >> > still
> > >> > unassigned: Server node prints exception when ODBC driver
> disconnects
> > >> > Igniters, who would like to pick up it? By default, I'm going to
> > remove
> > >> it
> > >> > from release
> > >> >
> > >> >
> > >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org
> >:
> > >> >
> > >> > > Hello, Igniters.
> > >> > >
> > >> > > I try to upgrade Spark version but failed.
> > >> > >
> > >> > > Seems, internal Spark API(External Catalog, SQL planner) that we
> use
> > >> > > changed a lot.
> > >> > > So it will take some time to upgrade version.
> > >> > >
> > >> > > For now, I work hard to complete the second phase of IEP-35 so I
> > >> postpone
> > >> > > upgrade Spark version to Ignite 2.8.
> > >> > >
> > >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> > >> > > > Hi Denis,
> > >> > > >
> > >> > > > Sure, since code freeze is planned for today, I don't mind to
> > include
> > >> > > this
> > >> > > > bug.
> > >> > > >
> > >> > > > Ivan, could you complete this issue by 20 August?
> > >> > > >
> > >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> > >> > > >
> https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> > >> > > >
> > >> > > > BTW #2, FYI, release page is now available here
> > >> > > >
> > >>
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> > >> > > >
> > >> > > > BTW #3, FYI, release related test PR is here
> > >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> > report is
> > >> > > here:
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> > >> > > >
> > >> > > >
> > >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org >:
> > >> > > >
> > >> > > > > An Ignite user just reported a silly issue that needs to be
> > fixed
> > >> in
> > >> > > 2.7.6:
> > >> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
> > >> > > > >
> > >> > > > > More details and context:
> > >> > > > >
> > >> > > > >
> > >> > >
> > >> >
> > >>
> >
> https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
> > >> > > > >
> > >> > > > > Ivan, please help us to make it to the release.
> > >> > > > >
> > >> > > > > -
> > >> > > > > Denis
> > >> > > > >
> > >> > > > >
> > >> > > > > On Tue, Aug 13, 2019 at 6:47 AM Denis Magda <
> dma...@apache.org
> > >
> > >> > wrote:
> > >> > > > >
> > >> > > > > > IGNITE-12507 (Persistence files are stored to temp dir) has
> > >> > > definitely be
> > >> > > > > > added the scope and treated one of the main release drivers.
> > >> > > > > >
> > >> > > > > > Dmitry, please let us know once the

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-15 Thread Ilya Kasnacheev

Hello!

I suggest also including IGNITE-11736, otherwise we are going to run into
problems each time TC is invoked.

https://issues.apache.org/jira/browse/IGNITE-11736

Regards,
-- 
Ilya Kasnacheev


чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky :

> yep, i`l try to call someone who probably familiar with this problem.
>
> >
> >
> >Ok, I've removed Spark from the scope.
> >
> >What about the unassigned issue related to ODBC? It is not looking like
> >somebody will fix it before release.
> >
> >Evgeniy Stanilovsky, what about
> >https://issues.apache.org/jira/browse/IGNITE-12061
> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >do you have someone to review the fix?
> >
> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> >
> >> Dmitry,
> >>
> >> It would be better for us to put off the Spark upgrade until 2.8 as
> Nikolay
> >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> fixes
> >> for the critical issues from the scope.
> >>
> >>
> >> -
> >> Denis
> >>
> >>
> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org >
> wrote:
> >>
> >> > Nikolay, how long does it take to update? I will be traveling from 28
> Aug
> >> > till 16 Sept. We can select new dates for release if the majority of
> >> fixes
> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> your
> >> > vision about selecting new dates.
> >> >
> >> > *Voting Date: *Sept 18, 2019
> >> >
> >> > *Release Date: *Sept 23, 2019
> >> >
> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro >
> is
> >> > still
> >> > unassigned: Server node prints exception when ODBC driver disconnects
> >> > Igniters, who would like to pick up it? By default, I'm going to
> remove
> >> it
> >> > from release
> >> >
> >> >
> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org >:
> >> >
> >> > > Hello, Igniters.
> >> > >
> >> > > I try to upgrade Spark version but failed.
> >> > >
> >> > > Seems, internal Spark API(External Catalog, SQL planner) that we use
> >> > > changed a lot.
> >> > > So it will take some time to upgrade version.
> >> > >
> >> > > For now, I work hard to complete the second phase of IEP-35 so I
> >> postpone
> >> > > upgrade Spark version to Ignite 2.8.
> >> > >
> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> >> > > > Hi Denis,
> >> > > >
> >> > > > Sure, since code freeze is planned for today, I don't mind to
> include
> >> > > this
> >> > > > bug.
> >> > > >
> >> > > > Ivan, could you complete this issue by 20 August?
> >> > > >
> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> >> > > >  https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> >> > > >
> >> > > > BTW #2, FYI, release page is now available here
> >> > > >
> >>  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> >> > > >
> >> > > > BTW #3, FYI, release related test PR is here
> >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> report is
> >> > > here:
> >> > > >
> >> > >
> >> >
> >>
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> >> > > >
> >> > > >
> >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org >:
> >> > > >
> >> > > > > An Ignite user just reported a silly issue that needs to be
> fixed
> >> in
> >> > > 2.7.6:
> >> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
> >> > > > >
> >> > > > > More details and context:
> >> > > > >
> >> > > > >
> >> > >
> >> >
> >>
> https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
> >> > > > >
> >> > > > > Ivan, please help us to make it to the release.
> >> > > > >
> >> > > > > -
> >> > > > > Denis
> >> > > > >
> >> > > > >
> >> > > > > On Tue, Aug 13, 2019 at 6:47 AM Denis Magda < dma...@apache.org
> >
> >> > wrote:
> >> > > > >
> >> > > > > > IGNITE-12507 (Persistence files are stored to temp dir) has
> >> > > definitely be
> >> > > > > > added the scope and treated one of the main release drivers.
> >> > > > > >
> >> > > > > > Dmitry, please let us know once the release wiki page is
> ready so
> >> > > that we
> >> > > > > > can finalize the timelines based on chosen scope.
> >> > > > > >
> >> > > > > > -
> >> > > > > > Denis
> >> > > > > >
> >> > > > > >
> >> > > > > > On Mon, Aug 12, 2019 at 7:12 PM Dmitriy Pavlov <
> >>  dpav...@apache.org
> >> > >
> >> > > > >
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > > Hi,
> >> > > > > > >
> >> > > > > > > Thanks to everyone, who participated in the discussion.
> >> > > > > > >
> >> > > > > > > I would like to wait also fix for
> >> > > > > > >  https://issues.apache.org/jira/browse/IGNITE-12057
> >> > > > > > >
> >> > > > > > > and discussion results for that issue:
> >> > > > > > >
> >> > > > > > >
> >> > > > >
> >> > > > >
> >> > >
> >> >
> >>
>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

2019-08-15 Thread Dmitriy Pavlov

I removed  https://issues.apache.org/jira/browse/IGNITE-12032 until nobody
volunteer to complete the task.

Evgeniy, please keep me updated about IGNITE-12061.

чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky :

> yep, i`l try to call someone who probably familiar with this problem.
>
> >
> >
> >Ok, I've removed Spark from the scope.
> >
> >What about the unassigned issue related to ODBC? It is not looking like
> >somebody will fix it before release.
> >
> >Evgeniy Stanilovsky, what about
> >https://issues.apache.org/jira/browse/IGNITE-12061
> >< https://issues.apache.org/jira/browse/IGNITE-12061?src=confmacro >
> >do you have someone to review the fix?
> >
> >чт, 15 авг. 2019 г. в 16:05, Denis Magda < dma...@apache.org >:
> >
> >> Dmitry,
> >>
> >> It would be better for us to put off the Spark upgrade until 2.8 as
> Nikolay
> >> suggested. Let's release 2.7.6 as quickly as possible to let roll out
> fixes
> >> for the critical issues from the scope.
> >>
> >>
> >> -
> >> Denis
> >>
> >>
> >> On Thu, Aug 15, 2019 at 3:29 PM Dmitriy Pavlov < dpav...@apache.org >
> wrote:
> >>
> >> > Nikolay, how long does it take to update? I will be traveling from 28
> Aug
> >> > till 16 Sept. We can select new dates for release if the majority of
> >> fixes
> >> > can be done by 16 Sept, but can't be by 20 Aug. Denis, please share
> your
> >> > vision about selecting new dates.
> >> >
> >> > *Voting Date: *Sept 18, 2019
> >> >
> >> > *Release Date: *Sept 23, 2019
> >> >
> >> > Issue  https://issues.apache.org/jira/browse/IGNITE-12032
> >> > < https://issues.apache.org/jira/browse/IGNITE-12032?src=confmacro >
> is
> >> > still
> >> > unassigned: Server node prints exception when ODBC driver disconnects
> >> > Igniters, who would like to pick up it? By default, I'm going to
> remove
> >> it
> >> > from release
> >> >
> >> >
> >> > чт, 15 авг. 2019 г. в 14:54, Nikolay Izhikov < nizhi...@apache.org >:
> >> >
> >> > > Hello, Igniters.
> >> > >
> >> > > I try to upgrade Spark version but failed.
> >> > >
> >> > > Seems, internal Spark API(External Catalog, SQL planner) that we use
> >> > > changed a lot.
> >> > > So it will take some time to upgrade version.
> >> > >
> >> > > For now, I work hard to complete the second phase of IEP-35 so I
> >> postpone
> >> > > upgrade Spark version to Ignite 2.8.
> >> > >
> >> > > В Чт, 15/08/2019 в 14:51 +0300, Dmitriy Pavlov пишет:
> >> > > > Hi Denis,
> >> > > >
> >> > > > Sure, since code freeze is planned for today, I don't mind to
> include
> >> > > this
> >> > > > bug.
> >> > > >
> >> > > > Ivan, could you complete this issue by 20 August?
> >> > > >
> >> > > > BTW #1, Dmitriy Govoruchnin, please reply about commit for
> >> > > >  https://issues.apache.org/jira/browse/IGNITE-11953?src=confmacro
> >> > > >
> >> > > > BTW #2, FYI, release page is now available here
> >> > > >
> >>  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.7.6
> >> > > >
> >> > > > BTW #3, FYI, release related test PR is here
> >> > > >  https://github.com/apache/ignite/pull/6775 and it's TC Bot
> report is
> >> > > here:
> >> > > >
> >> > >
> >> >
> >>
> https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=ignite-2.7.6=Latest=ignite-2.7.6
> >> > > >
> >> > > >
> >> > > > чт, 15 авг. 2019 г. в 13:55, Denis Magda < dma...@apache.org >:
> >> > > >
> >> > > > > An Ignite user just reported a silly issue that needs to be
> fixed
> >> in
> >> > > 2.7.6:
> >> > > > >  https://issues.apache.org/jira/browse/IGNITE-12068
> >> > > > >
> >> > > > > More details and context:
> >> > > > >
> >> > > > >
> >> > >
> >> >
> >>
> https://stackoverflow.com/questions/57479636/simple-select-query-missing-rows-in-ignite
> >> > > > >
> >> > > > > Ivan, please help us to make it to the release.
> >> > > > >
> >> > > > > -
> >> > > > > Denis
> >> > > > >
> >> > > > >
> >> > > > > On Tue, Aug 13, 2019 at 6:47 AM Denis Magda < dma...@apache.org
> >
> >> > wrote:
> >> > > > >
> >> > > > > > IGNITE-12507 (Persistence files are stored to temp dir) has
> >> > > definitely be
> >> > > > > > added the scope and treated one of the main release drivers.
> >> > > > > >
> >> > > > > > Dmitry, please let us know once the release wiki page is
> ready so
> >> > > that we
> >> > > > > > can finalize the timelines based on chosen scope.
> >> > > > > >
> >> > > > > > -
> >> > > > > > Denis
> >> > > > > >
> >> > > > > >
> >> > > > > > On Mon, Aug 12, 2019 at 7:12 PM Dmitriy Pavlov <
> >>  dpav...@apache.org
> >> > >
> >> > > > >
> >> > > > > wrote:
> >> > > > > >
> >> > > > > > > Hi,
> >> > > > > > >
> >> > > > > > > Thanks to everyone, who participated in the discussion.
> >> > > > > > >
> >> > > > > > > I would like to wait also fix for
> >> > > > > > >  https://issues.apache.org/jira/browse/IGNITE-12057
> >> > > > > > >
> >> > > > > > > and discussion results for that issue:
> >> > > > > > >
> >> > > > > > >
> >> > > > >
> >> > > > >
> >> > >
> >> >
> >>
>

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Re: Re[4]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

14 matches

Site Navigation

Mail list logo

Footer information