You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Alexey Goncharuk <al...@gmail.com> on 2018/06/05 16:39:30 UTC
Ignite 2.6 emergency release suggestion
Igniters,
Recently we've stumbled across the following two tickets [1], [2] which
seem to be very critical from the usability and stability points of view.
The [1] results in clients not being able to update persistence-enabled
clusters unless the client configuration is identical to the server
configuration. The [2] may result in incorrect node state recovery and
either corrupted storage or lost updates.
I suggest we make an emergency release (to my knowledge, we already had
such a practice with Ignite 2.3) and include the fixes for both of the
issues to it.
Thoughts?
[1] https://issues.apache.org/jira/browse/IGNITE-8476
[2] https://issues.apache.org/jira/browse/IGNITE-8685
--AG
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
I agree with Eduard.
вс, 10 июн. 2018 г. в 13:22, Eduard Shangareev <eduard.shangareev@gmail.com
>:
> Guys,
>
> I have found an issue which could cause JVM Crash.
>
> https://issues.apache.org/jira/browse/IGNITE-8768
> (JVM Crash on node stop or deactivate while async evict in progress).
>
> Another one could hang node or throw AssertionError when we try to recycle
> data pages:
> https://issues.apache.org/jira/browse/IGNITE-8769
>
>
> I believe, that we should consider to include them.
>
>
>
>
>
> On Sat, Jun 9, 2018 at 11:29 PM, Alexey Goncharuk <
> alexey.goncharuk@gmail.com> wrote:
>
> > Ignite-2.6 branch is created, all mentioned fixes were pushed. I also
> > included the fix for [1] because the issue could lead to a hanging PME in
> > some circumstances.
> > Will trigger TC shortly.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-8530
> >
> > вт, 5 июн. 2018 г. в 21:18, Ivan Rakov <iv...@gmail.com>:
> >
> > > I'd like to add that first issue [1] has a follow-up fix [2]. It should
> > > be backported along with the first fix.
> > >
> > > [1] - https://issues.apache.org/jira/browse/IGNITE-8476
> > > [2] - https://issues.apache.org/jira/browse/IGNITE-8682
> > >
> > > Best Regards,
> > > Ivan Rakov
> > >
> > > On 05.06.2018 20:57, Ivan Rakov wrote:
> > > > I agree in general. First issue is severe usability issue, while
> > > > second one may fail crash recovery and cause data loss. This makes AI
> > > > 2.5 not recommended for using.
> > > >
> > > > Best Regards,
> > > > Ivan Rakov
> > > >
> > > > On 05.06.2018 19:39, Alexey Goncharuk wrote:
> > > >> Igniters,
> > > >>
> > > >> Recently we've stumbled across the following two tickets [1], [2]
> > which
> > > >> seem to be very critical from the usability and stability points of
> > > >> view.
> > > >> The [1] results in clients not being able to update
> > persistence-enabled
> > > >> clusters unless the client configuration is identical to the server
> > > >> configuration. The [2] may result in incorrect node state recovery
> and
> > > >> either corrupted storage or lost updates.
> > > >>
> > > >> I suggest we make an emergency release (to my knowledge, we already
> > had
> > > >> such a practice with Ignite 2.3) and include the fixes for both of
> the
> > > >> issues to it.
> > > >>
> > > >> Thoughts?
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-8476
> > > >> [2] https://issues.apache.org/jira/browse/IGNITE-8685
> > > >>
> > > >> --AG
> > > >>
> > > >
> > >
> > >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Eduard Shangareev <ed...@gmail.com>.
Guys,
I have found an issue which could cause JVM Crash.
https://issues.apache.org/jira/browse/IGNITE-8768
(JVM Crash on node stop or deactivate while async evict in progress).
Another one could hang node or throw AssertionError when we try to recycle
data pages:
https://issues.apache.org/jira/browse/IGNITE-8769
I believe, that we should consider to include them.
On Sat, Jun 9, 2018 at 11:29 PM, Alexey Goncharuk <
alexey.goncharuk@gmail.com> wrote:
> Ignite-2.6 branch is created, all mentioned fixes were pushed. I also
> included the fix for [1] because the issue could lead to a hanging PME in
> some circumstances.
> Will trigger TC shortly.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8530
>
> вт, 5 июн. 2018 г. в 21:18, Ivan Rakov <iv...@gmail.com>:
>
> > I'd like to add that first issue [1] has a follow-up fix [2]. It should
> > be backported along with the first fix.
> >
> > [1] - https://issues.apache.org/jira/browse/IGNITE-8476
> > [2] - https://issues.apache.org/jira/browse/IGNITE-8682
> >
> > Best Regards,
> > Ivan Rakov
> >
> > On 05.06.2018 20:57, Ivan Rakov wrote:
> > > I agree in general. First issue is severe usability issue, while
> > > second one may fail crash recovery and cause data loss. This makes AI
> > > 2.5 not recommended for using.
> > >
> > > Best Regards,
> > > Ivan Rakov
> > >
> > > On 05.06.2018 19:39, Alexey Goncharuk wrote:
> > >> Igniters,
> > >>
> > >> Recently we've stumbled across the following two tickets [1], [2]
> which
> > >> seem to be very critical from the usability and stability points of
> > >> view.
> > >> The [1] results in clients not being able to update
> persistence-enabled
> > >> clusters unless the client configuration is identical to the server
> > >> configuration. The [2] may result in incorrect node state recovery and
> > >> either corrupted storage or lost updates.
> > >>
> > >> I suggest we make an emergency release (to my knowledge, we already
> had
> > >> such a practice with Ignite 2.3) and include the fixes for both of the
> > >> issues to it.
> > >>
> > >> Thoughts?
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-8476
> > >> [2] https://issues.apache.org/jira/browse/IGNITE-8685
> > >>
> > >> --AG
> > >>
> > >
> >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Alexey Goncharuk <al...@gmail.com>.
Ignite-2.6 branch is created, all mentioned fixes were pushed. I also
included the fix for [1] because the issue could lead to a hanging PME in
some circumstances.
Will trigger TC shortly.
[1] https://issues.apache.org/jira/browse/IGNITE-8530
вт, 5 июн. 2018 г. в 21:18, Ivan Rakov <iv...@gmail.com>:
> I'd like to add that first issue [1] has a follow-up fix [2]. It should
> be backported along with the first fix.
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-8476
> [2] - https://issues.apache.org/jira/browse/IGNITE-8682
>
> Best Regards,
> Ivan Rakov
>
> On 05.06.2018 20:57, Ivan Rakov wrote:
> > I agree in general. First issue is severe usability issue, while
> > second one may fail crash recovery and cause data loss. This makes AI
> > 2.5 not recommended for using.
> >
> > Best Regards,
> > Ivan Rakov
> >
> > On 05.06.2018 19:39, Alexey Goncharuk wrote:
> >> Igniters,
> >>
> >> Recently we've stumbled across the following two tickets [1], [2] which
> >> seem to be very critical from the usability and stability points of
> >> view.
> >> The [1] results in clients not being able to update persistence-enabled
> >> clusters unless the client configuration is identical to the server
> >> configuration. The [2] may result in incorrect node state recovery and
> >> either corrupted storage or lost updates.
> >>
> >> I suggest we make an emergency release (to my knowledge, we already had
> >> such a practice with Ignite 2.3) and include the fixes for both of the
> >> issues to it.
> >>
> >> Thoughts?
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-8476
> >> [2] https://issues.apache.org/jira/browse/IGNITE-8685
> >>
> >> --AG
> >>
> >
>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Ivan Rakov <iv...@gmail.com>.
I'd like to add that first issue [1] has a follow-up fix [2]. It should
be backported along with the first fix.
[1] - https://issues.apache.org/jira/browse/IGNITE-8476
[2] - https://issues.apache.org/jira/browse/IGNITE-8682
Best Regards,
Ivan Rakov
On 05.06.2018 20:57, Ivan Rakov wrote:
> I agree in general. First issue is severe usability issue, while
> second one may fail crash recovery and cause data loss. This makes AI
> 2.5 not recommended for using.
>
> Best Regards,
> Ivan Rakov
>
> On 05.06.2018 19:39, Alexey Goncharuk wrote:
>> Igniters,
>>
>> Recently we've stumbled across the following two tickets [1], [2] which
>> seem to be very critical from the usability and stability points of
>> view.
>> The [1] results in clients not being able to update persistence-enabled
>> clusters unless the client configuration is identical to the server
>> configuration. The [2] may result in incorrect node state recovery and
>> either corrupted storage or lost updates.
>>
>> I suggest we make an emergency release (to my knowledge, we already had
>> such a practice with Ignite 2.3) and include the fixes for both of the
>> issues to it.
>>
>> Thoughts?
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-8476
>> [2] https://issues.apache.org/jira/browse/IGNITE-8685
>>
>> --AG
>>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Ivan Rakov <iv...@gmail.com>.
I agree in general. First issue is severe usability issue, while second
one may fail crash recovery and cause data loss. This makes AI 2.5 not
recommended for using.
Best Regards,
Ivan Rakov
On 05.06.2018 19:39, Alexey Goncharuk wrote:
> Igniters,
>
> Recently we've stumbled across the following two tickets [1], [2] which
> seem to be very critical from the usability and stability points of view.
> The [1] results in clients not being able to update persistence-enabled
> clusters unless the client configuration is identical to the server
> configuration. The [2] may result in incorrect node state recovery and
> either corrupted storage or lost updates.
>
> I suggest we make an emergency release (to my knowledge, we already had
> such a practice with Ignite 2.3) and include the fixes for both of the
> issues to it.
>
> Thoughts?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8476
> [2] https://issues.apache.org/jira/browse/IGNITE-8685
>
> --AG
>
Re: Ignite 2.6 emergency release suggestion
Posted by Anton Vinogradov <av...@apache.org>.
Thank you!
пн, 9 июл. 2018 г. в 18:57, Andrey Gura <ag...@apache.org>:
> POM is updated in master branch.
>
> And no more commits to ignite-2.6 branch.
> On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov <av...@apache.org> wrote:
> >
> > Andrey,
> >
> > Answered at the same [1] issue.
> > Anyway, we have to increment version now. We had to do this at the moment
> > we created ignite-2.6 branch.
> > In case you have some issues with increment, I can do this by myself.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-7823
> >
> > пн, 9 июл. 2018 г. в 16:35, Petr Ivanov <mr...@gmail.com>:
> >
> > > I will side with Anton.
> > > In any case right after branch creation, master version should be
> > > incremented.
> > >
> > > Or version increase is planned right after 2.6 release?
> > >
> > >
> > >
> > > > On 9 Jul 2018, at 16:32, Andrey Gura <ag...@apache.org> wrote:
> > > >
> > > > Anton,
> > > >
> > > > while version number is frequently used in Ignite code base I believe
> > > > that it's bad approach. See my comment to IGNITE-7823 [1] issue.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-7823
> > > > On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov <av...@apache.org>
> wrote:
> > > >>
> > > >> Igniters,
> > > >>
> > > >> Ignite version still 2.6.0-SNAPSHOT at master,
> > > >> It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a
> > > special
> > > >> branch.
> > > >>
> > > >> Some issues affecting backward compatibility can not be merged while
> > > >> version not incremented.
> > > >>
> > > >> ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
> > > >>
> > > >>> Igniters,
> > > >>>
> > > >>> I've moved IGNITE-8780 [1] issue to the next release. It can't be
> > > >>> merged to AI 2.6 because it has many other dependent commits.
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-8780
> > > >>> On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com>
> > > wrote:
> > > >>>>
> > > >>>> Andrey, thanks!
> > > >>>>
> > > >>>> I've cherry-picked the fixes to ignite-2.6 branch.
> > > >>>>
> > > >>>> Best Regards,
> > > >>>> Ivan Rakov
> > > >>>>
> > > >>>> On 04.07.2018 16:26, Andrey Gura wrote:
> > > >>>>> Ivan,
> > > >>>>>
> > > >>>>> I agree to include this fixes into AI 2.6 release. Please, feel
> free
> > > >>> to merge.
> > > >>>>> On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <ivan.glukos@gmail.com
> >
> > > >>> wrote:
> > > >>>>>> Igniters,
> > > >>>>>>
> > > >>>>>> Do we still have chance to extend 2.6 scope?
> > > >>>>>>
> > > >>>>>> I propose to include two more tickets into 2.6:
> > > >>>>>> https://issues.apache.org/jira/browse/IGNITE-8769
> > > >>>>>> https://issues.apache.org/jira/browse/IGNITE-8910
> > > >>>>>>
> > > >>>>>> We had data races in our free lists implementation. Fixes
> prevent
> > > >>>>>> possibility of AssertionError during cache operation, which may
> lead
> > > >>> to
> > > >>>>>> hangs and data inconsistency.
> > > >>>>>>
> > > >>>>>> Best Regards,
> > > >>>>>> Ivan Rakov
> > > >>>>>>
> > > >>>>>>
> > > >>>>>> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> > > >>>>>>> Nikolay, thank you for such fast reaction. Tests are passing
> now.
> > > >>>>>>>
> > > >>>>>>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <
> nizhikov@apache.org
> > > >:
> > > >>>>>>>
> > > >>>>>>>> Hello, Dmitriy.
> > > >>>>>>>>
> > > >>>>>>>> I fixed this issue, already.
> > > >>>>>>>> Please, check it.
> > > >>>>>>>>
> > > >>>>>>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > > >>>>>>>>> Hi Denis,
> > > >>>>>>>>>
> > > >>>>>>>>> currently anyway we have TC issue came from spark version
> > > >>> migrations.
> > > >>>>>>>>>
> > > >>>>>>>>> I also currently experiencing challenges with my local
> > > environment
> > > >>> setup.
> > > >>>>>>>>> So I guess we have day or two to wait this fix.
> > > >>>>>>>>>
> > > >>>>>>>>> Sincerely.
> > > >>>>>>>>> Dmitriy Pavlov
> > > >>>>>>>>>
> > > >>>>>>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dmagda@apache.org
> >:
> > > >>>>>>>>>
> > > >>>>>>>>>> May I ask when? The current status of the ticket is not
> clear.
> > > >>>>>>>>>>
> > > >>>>>>>>>> --
> > > >>>>>>>>>> Denis
> > > >>>>>>>>>>
> > > >>>>>>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> > > >>>>>>>> spiderru5597@gmail.com>
> > > >>>>>>>>>> wrote:
> > > >>>>>>>>>>
> > > >>>>>>>>>>> Yes, it will be in the release 2.6
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
> > > dpavlov.spb@gmail.com>
> > > >>>>>>>>>>> написал(а):
> > > >>>>>>>>>>>> Hi Igniters,
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> I've returned
> > > https://issues.apache.org/jira/browse/IGNITE-8780
> > > >>>>>>>> to the
> > > >>>>>>>>>>>> scope because it was initially discussed to be in this
> > > reselase.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Alexey Stelmak, could you please confirm fix could be
> ready
> > > >>> soon?
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Also I've cherry-picked javadoc fix.
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> Sincerely,
> > > >>>>>>>>>>>> Dmitriy Pavlov
> > > >>>>>>>>>>>>
> > > >>>>>>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <
> dmagda@apache.org>:
> > > >>>>
> > > >>>
> > >
> > >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Petr Ivanov <mr...@gmail.com>.
Awesome!
Thanks, Andrey!
> On 9 Jul 2018, at 18:57, Andrey Gura <ag...@apache.org> wrote:
>
> POM is updated in master branch.
>
> And no more commits to ignite-2.6 branch.
> On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov <av...@apache.org> wrote:
>>
>> Andrey,
>>
>> Answered at the same [1] issue.
>> Anyway, we have to increment version now. We had to do this at the moment
>> we created ignite-2.6 branch.
>> In case you have some issues with increment, I can do this by myself.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-7823
>>
>> пн, 9 июл. 2018 г. в 16:35, Petr Ivanov <mr...@gmail.com>:
>>
>>> I will side with Anton.
>>> In any case right after branch creation, master version should be
>>> incremented.
>>>
>>> Or version increase is planned right after 2.6 release?
>>>
>>>
>>>
>>>> On 9 Jul 2018, at 16:32, Andrey Gura <ag...@apache.org> wrote:
>>>>
>>>> Anton,
>>>>
>>>> while version number is frequently used in Ignite code base I believe
>>>> that it's bad approach. See my comment to IGNITE-7823 [1] issue.
>>>>
>>>> [1] https://issues.apache.org/jira/browse/IGNITE-7823
>>>> On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov <av...@apache.org> wrote:
>>>>>
>>>>> Igniters,
>>>>>
>>>>> Ignite version still 2.6.0-SNAPSHOT at master,
>>>>> It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a
>>> special
>>>>> branch.
>>>>>
>>>>> Some issues affecting backward compatibility can not be merged while
>>>>> version not incremented.
>>>>>
>>>>> ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
>>>>>
>>>>>> Igniters,
>>>>>>
>>>>>> I've moved IGNITE-8780 [1] issue to the next release. It can't be
>>>>>> merged to AI 2.6 because it has many other dependent commits.
>>>>>>
>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-8780
>>>>>> On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com>
>>> wrote:
>>>>>>>
>>>>>>> Andrey, thanks!
>>>>>>>
>>>>>>> I've cherry-picked the fixes to ignite-2.6 branch.
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Ivan Rakov
>>>>>>>
>>>>>>> On 04.07.2018 16:26, Andrey Gura wrote:
>>>>>>>> Ivan,
>>>>>>>>
>>>>>>>> I agree to include this fixes into AI 2.6 release. Please, feel free
>>>>>> to merge.
>>>>>>>> On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com>
>>>>>> wrote:
>>>>>>>>> Igniters,
>>>>>>>>>
>>>>>>>>> Do we still have chance to extend 2.6 scope?
>>>>>>>>>
>>>>>>>>> I propose to include two more tickets into 2.6:
>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-8769
>>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-8910
>>>>>>>>>
>>>>>>>>> We had data races in our free lists implementation. Fixes prevent
>>>>>>>>> possibility of AssertionError during cache operation, which may lead
>>>>>> to
>>>>>>>>> hangs and data inconsistency.
>>>>>>>>>
>>>>>>>>> Best Regards,
>>>>>>>>> Ivan Rakov
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 27.06.2018 18:56, Dmitry Pavlov wrote:
>>>>>>>>>> Nikolay, thank you for such fast reaction. Tests are passing now.
>>>>>>>>>>
>>>>>>>>>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <nizhikov@apache.org
>>>> :
>>>>>>>>>>
>>>>>>>>>>> Hello, Dmitriy.
>>>>>>>>>>>
>>>>>>>>>>> I fixed this issue, already.
>>>>>>>>>>> Please, check it.
>>>>>>>>>>>
>>>>>>>>>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
>>>>>>>>>>>> Hi Denis,
>>>>>>>>>>>>
>>>>>>>>>>>> currently anyway we have TC issue came from spark version
>>>>>> migrations.
>>>>>>>>>>>>
>>>>>>>>>>>> I also currently experiencing challenges with my local
>>> environment
>>>>>> setup.
>>>>>>>>>>>> So I guess we have day or two to wait this fix.
>>>>>>>>>>>>
>>>>>>>>>>>> Sincerely.
>>>>>>>>>>>> Dmitriy Pavlov
>>>>>>>>>>>>
>>>>>>>>>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
>>>>>>>>>>>>
>>>>>>>>>>>>> May I ask when? The current status of the ticket is not clear.
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Denis
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
>>>>>>>>>>> spiderru5597@gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes, it will be in the release 2.6
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
>>> dpavlov.spb@gmail.com>
>>>>>>>>>>>>>> написал(а):
>>>>>>>>>>>>>>> Hi Igniters,
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> I've returned
>>> https://issues.apache.org/jira/browse/IGNITE-8780
>>>>>>>>>>> to the
>>>>>>>>>>>>>>> scope because it was initially discussed to be in this
>>> reselase.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Alexey Stelmak, could you please confirm fix could be ready
>>>>>> soon?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Also I've cherry-picked javadoc fix.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> Sincerely,
>>>>>>>>>>>>>>> Dmitriy Pavlov
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
>>>>>>>
>>>>>>
>>>
>>>
Re: Ignite 2.6 emergency release suggestion
Posted by Andrey Gura <ag...@apache.org>.
POM is updated in master branch.
And no more commits to ignite-2.6 branch.
On Mon, Jul 9, 2018 at 4:58 PM Anton Vinogradov <av...@apache.org> wrote:
>
> Andrey,
>
> Answered at the same [1] issue.
> Anyway, we have to increment version now. We had to do this at the moment
> we created ignite-2.6 branch.
> In case you have some issues with increment, I can do this by myself.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7823
>
> пн, 9 июл. 2018 г. в 16:35, Petr Ivanov <mr...@gmail.com>:
>
> > I will side with Anton.
> > In any case right after branch creation, master version should be
> > incremented.
> >
> > Or version increase is planned right after 2.6 release?
> >
> >
> >
> > > On 9 Jul 2018, at 16:32, Andrey Gura <ag...@apache.org> wrote:
> > >
> > > Anton,
> > >
> > > while version number is frequently used in Ignite code base I believe
> > > that it's bad approach. See my comment to IGNITE-7823 [1] issue.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-7823
> > > On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov <av...@apache.org> wrote:
> > >>
> > >> Igniters,
> > >>
> > >> Ignite version still 2.6.0-SNAPSHOT at master,
> > >> It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a
> > special
> > >> branch.
> > >>
> > >> Some issues affecting backward compatibility can not be merged while
> > >> version not incremented.
> > >>
> > >> ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
> > >>
> > >>> Igniters,
> > >>>
> > >>> I've moved IGNITE-8780 [1] issue to the next release. It can't be
> > >>> merged to AI 2.6 because it has many other dependent commits.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-8780
> > >>> On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com>
> > wrote:
> > >>>>
> > >>>> Andrey, thanks!
> > >>>>
> > >>>> I've cherry-picked the fixes to ignite-2.6 branch.
> > >>>>
> > >>>> Best Regards,
> > >>>> Ivan Rakov
> > >>>>
> > >>>> On 04.07.2018 16:26, Andrey Gura wrote:
> > >>>>> Ivan,
> > >>>>>
> > >>>>> I agree to include this fixes into AI 2.6 release. Please, feel free
> > >>> to merge.
> > >>>>> On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com>
> > >>> wrote:
> > >>>>>> Igniters,
> > >>>>>>
> > >>>>>> Do we still have chance to extend 2.6 scope?
> > >>>>>>
> > >>>>>> I propose to include two more tickets into 2.6:
> > >>>>>> https://issues.apache.org/jira/browse/IGNITE-8769
> > >>>>>> https://issues.apache.org/jira/browse/IGNITE-8910
> > >>>>>>
> > >>>>>> We had data races in our free lists implementation. Fixes prevent
> > >>>>>> possibility of AssertionError during cache operation, which may lead
> > >>> to
> > >>>>>> hangs and data inconsistency.
> > >>>>>>
> > >>>>>> Best Regards,
> > >>>>>> Ivan Rakov
> > >>>>>>
> > >>>>>>
> > >>>>>> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> > >>>>>>> Nikolay, thank you for such fast reaction. Tests are passing now.
> > >>>>>>>
> > >>>>>>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <nizhikov@apache.org
> > >:
> > >>>>>>>
> > >>>>>>>> Hello, Dmitriy.
> > >>>>>>>>
> > >>>>>>>> I fixed this issue, already.
> > >>>>>>>> Please, check it.
> > >>>>>>>>
> > >>>>>>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > >>>>>>>>> Hi Denis,
> > >>>>>>>>>
> > >>>>>>>>> currently anyway we have TC issue came from spark version
> > >>> migrations.
> > >>>>>>>>>
> > >>>>>>>>> I also currently experiencing challenges with my local
> > environment
> > >>> setup.
> > >>>>>>>>> So I guess we have day or two to wait this fix.
> > >>>>>>>>>
> > >>>>>>>>> Sincerely.
> > >>>>>>>>> Dmitriy Pavlov
> > >>>>>>>>>
> > >>>>>>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> > >>>>>>>>>
> > >>>>>>>>>> May I ask when? The current status of the ticket is not clear.
> > >>>>>>>>>>
> > >>>>>>>>>> --
> > >>>>>>>>>> Denis
> > >>>>>>>>>>
> > >>>>>>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> > >>>>>>>> spiderru5597@gmail.com>
> > >>>>>>>>>> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> Yes, it will be in the release 2.6
> > >>>>>>>>>>>
> > >>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
> > dpavlov.spb@gmail.com>
> > >>>>>>>>>>> написал(а):
> > >>>>>>>>>>>> Hi Igniters,
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> I've returned
> > https://issues.apache.org/jira/browse/IGNITE-8780
> > >>>>>>>> to the
> > >>>>>>>>>>>> scope because it was initially discussed to be in this
> > reselase.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Alexey Stelmak, could you please confirm fix could be ready
> > >>> soon?
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Also I've cherry-picked javadoc fix.
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> Sincerely,
> > >>>>>>>>>>>> Dmitriy Pavlov
> > >>>>>>>>>>>>
> > >>>>>>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> > >>>>
> > >>>
> >
> >
Re: Ignite 2.6 emergency release suggestion
Posted by Anton Vinogradov <av...@apache.org>.
Andrey,
Answered at the same [1] issue.
Anyway, we have to increment version now. We had to do this at the moment
we created ignite-2.6 branch.
In case you have some issues with increment, I can do this by myself.
[1] https://issues.apache.org/jira/browse/IGNITE-7823
пн, 9 июл. 2018 г. в 16:35, Petr Ivanov <mr...@gmail.com>:
> I will side with Anton.
> In any case right after branch creation, master version should be
> incremented.
>
> Or version increase is planned right after 2.6 release?
>
>
>
> > On 9 Jul 2018, at 16:32, Andrey Gura <ag...@apache.org> wrote:
> >
> > Anton,
> >
> > while version number is frequently used in Ignite code base I believe
> > that it's bad approach. See my comment to IGNITE-7823 [1] issue.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-7823
> > On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov <av...@apache.org> wrote:
> >>
> >> Igniters,
> >>
> >> Ignite version still 2.6.0-SNAPSHOT at master,
> >> It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a
> special
> >> branch.
> >>
> >> Some issues affecting backward compatibility can not be merged while
> >> version not incremented.
> >>
> >> ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
> >>
> >>> Igniters,
> >>>
> >>> I've moved IGNITE-8780 [1] issue to the next release. It can't be
> >>> merged to AI 2.6 because it has many other dependent commits.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-8780
> >>> On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com>
> wrote:
> >>>>
> >>>> Andrey, thanks!
> >>>>
> >>>> I've cherry-picked the fixes to ignite-2.6 branch.
> >>>>
> >>>> Best Regards,
> >>>> Ivan Rakov
> >>>>
> >>>> On 04.07.2018 16:26, Andrey Gura wrote:
> >>>>> Ivan,
> >>>>>
> >>>>> I agree to include this fixes into AI 2.6 release. Please, feel free
> >>> to merge.
> >>>>> On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com>
> >>> wrote:
> >>>>>> Igniters,
> >>>>>>
> >>>>>> Do we still have chance to extend 2.6 scope?
> >>>>>>
> >>>>>> I propose to include two more tickets into 2.6:
> >>>>>> https://issues.apache.org/jira/browse/IGNITE-8769
> >>>>>> https://issues.apache.org/jira/browse/IGNITE-8910
> >>>>>>
> >>>>>> We had data races in our free lists implementation. Fixes prevent
> >>>>>> possibility of AssertionError during cache operation, which may lead
> >>> to
> >>>>>> hangs and data inconsistency.
> >>>>>>
> >>>>>> Best Regards,
> >>>>>> Ivan Rakov
> >>>>>>
> >>>>>>
> >>>>>> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> >>>>>>> Nikolay, thank you for such fast reaction. Tests are passing now.
> >>>>>>>
> >>>>>>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <nizhikov@apache.org
> >:
> >>>>>>>
> >>>>>>>> Hello, Dmitriy.
> >>>>>>>>
> >>>>>>>> I fixed this issue, already.
> >>>>>>>> Please, check it.
> >>>>>>>>
> >>>>>>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> >>>>>>>>> Hi Denis,
> >>>>>>>>>
> >>>>>>>>> currently anyway we have TC issue came from spark version
> >>> migrations.
> >>>>>>>>>
> >>>>>>>>> I also currently experiencing challenges with my local
> environment
> >>> setup.
> >>>>>>>>> So I guess we have day or two to wait this fix.
> >>>>>>>>>
> >>>>>>>>> Sincerely.
> >>>>>>>>> Dmitriy Pavlov
> >>>>>>>>>
> >>>>>>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> >>>>>>>>>
> >>>>>>>>>> May I ask when? The current status of the ticket is not clear.
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Denis
> >>>>>>>>>>
> >>>>>>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> >>>>>>>> spiderru5597@gmail.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Yes, it will be in the release 2.6
> >>>>>>>>>>>
> >>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
> dpavlov.spb@gmail.com>
> >>>>>>>>>>> написал(а):
> >>>>>>>>>>>> Hi Igniters,
> >>>>>>>>>>>>
> >>>>>>>>>>>> I've returned
> https://issues.apache.org/jira/browse/IGNITE-8780
> >>>>>>>> to the
> >>>>>>>>>>>> scope because it was initially discussed to be in this
> reselase.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Alexey Stelmak, could you please confirm fix could be ready
> >>> soon?
> >>>>>>>>>>>>
> >>>>>>>>>>>> Also I've cherry-picked javadoc fix.
> >>>>>>>>>>>>
> >>>>>>>>>>>> Sincerely,
> >>>>>>>>>>>> Dmitriy Pavlov
> >>>>>>>>>>>>
> >>>>>>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> >>>>
> >>>
>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Petr Ivanov <mr...@gmail.com>.
I will side with Anton.
In any case right after branch creation, master version should be incremented.
Or version increase is planned right after 2.6 release?
> On 9 Jul 2018, at 16:32, Andrey Gura <ag...@apache.org> wrote:
>
> Anton,
>
> while version number is frequently used in Ignite code base I believe
> that it's bad approach. See my comment to IGNITE-7823 [1] issue.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-7823
> On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov <av...@apache.org> wrote:
>>
>> Igniters,
>>
>> Ignite version still 2.6.0-SNAPSHOT at master,
>> It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a special
>> branch.
>>
>> Some issues affecting backward compatibility can not be merged while
>> version not incremented.
>>
>> ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
>>
>>> Igniters,
>>>
>>> I've moved IGNITE-8780 [1] issue to the next release. It can't be
>>> merged to AI 2.6 because it has many other dependent commits.
>>>
>>> [1] https://issues.apache.org/jira/browse/IGNITE-8780
>>> On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com> wrote:
>>>>
>>>> Andrey, thanks!
>>>>
>>>> I've cherry-picked the fixes to ignite-2.6 branch.
>>>>
>>>> Best Regards,
>>>> Ivan Rakov
>>>>
>>>> On 04.07.2018 16:26, Andrey Gura wrote:
>>>>> Ivan,
>>>>>
>>>>> I agree to include this fixes into AI 2.6 release. Please, feel free
>>> to merge.
>>>>> On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com>
>>> wrote:
>>>>>> Igniters,
>>>>>>
>>>>>> Do we still have chance to extend 2.6 scope?
>>>>>>
>>>>>> I propose to include two more tickets into 2.6:
>>>>>> https://issues.apache.org/jira/browse/IGNITE-8769
>>>>>> https://issues.apache.org/jira/browse/IGNITE-8910
>>>>>>
>>>>>> We had data races in our free lists implementation. Fixes prevent
>>>>>> possibility of AssertionError during cache operation, which may lead
>>> to
>>>>>> hangs and data inconsistency.
>>>>>>
>>>>>> Best Regards,
>>>>>> Ivan Rakov
>>>>>>
>>>>>>
>>>>>> On 27.06.2018 18:56, Dmitry Pavlov wrote:
>>>>>>> Nikolay, thank you for such fast reaction. Tests are passing now.
>>>>>>>
>>>>>>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
>>>>>>>
>>>>>>>> Hello, Dmitriy.
>>>>>>>>
>>>>>>>> I fixed this issue, already.
>>>>>>>> Please, check it.
>>>>>>>>
>>>>>>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
>>>>>>>>> Hi Denis,
>>>>>>>>>
>>>>>>>>> currently anyway we have TC issue came from spark version
>>> migrations.
>>>>>>>>>
>>>>>>>>> I also currently experiencing challenges with my local environment
>>> setup.
>>>>>>>>> So I guess we have day or two to wait this fix.
>>>>>>>>>
>>>>>>>>> Sincerely.
>>>>>>>>> Dmitriy Pavlov
>>>>>>>>>
>>>>>>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
>>>>>>>>>
>>>>>>>>>> May I ask when? The current status of the ticket is not clear.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Denis
>>>>>>>>>>
>>>>>>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
>>>>>>>> spiderru5597@gmail.com>
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Yes, it will be in the release 2.6
>>>>>>>>>>>
>>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
>>>>>>>>>>> написал(а):
>>>>>>>>>>>> Hi Igniters,
>>>>>>>>>>>>
>>>>>>>>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
>>>>>>>> to the
>>>>>>>>>>>> scope because it was initially discussed to be in this reselase.
>>>>>>>>>>>>
>>>>>>>>>>>> Alexey Stelmak, could you please confirm fix could be ready
>>> soon?
>>>>>>>>>>>>
>>>>>>>>>>>> Also I've cherry-picked javadoc fix.
>>>>>>>>>>>>
>>>>>>>>>>>> Sincerely,
>>>>>>>>>>>> Dmitriy Pavlov
>>>>>>>>>>>>
>>>>>>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
>>>>
>>>
Re: Ignite 2.6 emergency release suggestion
Posted by Andrey Gura <ag...@apache.org>.
Anton,
while version number is frequently used in Ignite code base I believe
that it's bad approach. See my comment to IGNITE-7823 [1] issue.
[1] https://issues.apache.org/jira/browse/IGNITE-7823
On Fri, Jul 6, 2018 at 4:08 PM Anton Vinogradov <av...@apache.org> wrote:
>
> Igniters,
>
> Ignite version still 2.6.0-SNAPSHOT at master,
> It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a special
> branch.
>
> Some issues affecting backward compatibility can not be merged while
> version not incremented.
>
> ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
>
> > Igniters,
> >
> > I've moved IGNITE-8780 [1] issue to the next release. It can't be
> > merged to AI 2.6 because it has many other dependent commits.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-8780
> > On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com> wrote:
> > >
> > > Andrey, thanks!
> > >
> > > I've cherry-picked the fixes to ignite-2.6 branch.
> > >
> > > Best Regards,
> > > Ivan Rakov
> > >
> > > On 04.07.2018 16:26, Andrey Gura wrote:
> > > > Ivan,
> > > >
> > > > I agree to include this fixes into AI 2.6 release. Please, feel free
> > to merge.
> > > > On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com>
> > wrote:
> > > >> Igniters,
> > > >>
> > > >> Do we still have chance to extend 2.6 scope?
> > > >>
> > > >> I propose to include two more tickets into 2.6:
> > > >> https://issues.apache.org/jira/browse/IGNITE-8769
> > > >> https://issues.apache.org/jira/browse/IGNITE-8910
> > > >>
> > > >> We had data races in our free lists implementation. Fixes prevent
> > > >> possibility of AssertionError during cache operation, which may lead
> > to
> > > >> hangs and data inconsistency.
> > > >>
> > > >> Best Regards,
> > > >> Ivan Rakov
> > > >>
> > > >>
> > > >> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> > > >>> Nikolay, thank you for such fast reaction. Tests are passing now.
> > > >>>
> > > >>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
> > > >>>
> > > >>>> Hello, Dmitriy.
> > > >>>>
> > > >>>> I fixed this issue, already.
> > > >>>> Please, check it.
> > > >>>>
> > > >>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > > >>>>> Hi Denis,
> > > >>>>>
> > > >>>>> currently anyway we have TC issue came from spark version
> > migrations.
> > > >>>>>
> > > >>>>> I also currently experiencing challenges with my local environment
> > setup.
> > > >>>>> So I guess we have day or two to wait this fix.
> > > >>>>>
> > > >>>>> Sincerely.
> > > >>>>> Dmitriy Pavlov
> > > >>>>>
> > > >>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> > > >>>>>
> > > >>>>>> May I ask when? The current status of the ticket is not clear.
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Denis
> > > >>>>>>
> > > >>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> > > >>>> spiderru5597@gmail.com>
> > > >>>>>> wrote:
> > > >>>>>>
> > > >>>>>>> Yes, it will be in the release 2.6
> > > >>>>>>>
> > > >>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> > > >>>>>>> написал(а):
> > > >>>>>>>> Hi Igniters,
> > > >>>>>>>>
> > > >>>>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
> > > >>>> to the
> > > >>>>>>>> scope because it was initially discussed to be in this reselase.
> > > >>>>>>>>
> > > >>>>>>>> Alexey Stelmak, could you please confirm fix could be ready
> > soon?
> > > >>>>>>>>
> > > >>>>>>>> Also I've cherry-picked javadoc fix.
> > > >>>>>>>>
> > > >>>>>>>> Sincerely,
> > > >>>>>>>> Dmitriy Pavlov
> > > >>>>>>>>
> > > >>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> > >
> >
Re: Ignite 2.6 emergency release suggestion
Posted by Anton Vinogradov <av...@apache.org>.
Igniters,
Ignite version still 2.6.0-SNAPSHOT at master,
It should be changed to 2.7.0-SNAPSHOT since we relocated 2.6 to a special
branch.
Some issues affecting backward compatibility can not be merged while
version not incremented.
ср, 4 июл. 2018 г. в 20:59, Andrey Gura <ag...@apache.org>:
> Igniters,
>
> I've moved IGNITE-8780 [1] issue to the next release. It can't be
> merged to AI 2.6 because it has many other dependent commits.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8780
> On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com> wrote:
> >
> > Andrey, thanks!
> >
> > I've cherry-picked the fixes to ignite-2.6 branch.
> >
> > Best Regards,
> > Ivan Rakov
> >
> > On 04.07.2018 16:26, Andrey Gura wrote:
> > > Ivan,
> > >
> > > I agree to include this fixes into AI 2.6 release. Please, feel free
> to merge.
> > > On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com>
> wrote:
> > >> Igniters,
> > >>
> > >> Do we still have chance to extend 2.6 scope?
> > >>
> > >> I propose to include two more tickets into 2.6:
> > >> https://issues.apache.org/jira/browse/IGNITE-8769
> > >> https://issues.apache.org/jira/browse/IGNITE-8910
> > >>
> > >> We had data races in our free lists implementation. Fixes prevent
> > >> possibility of AssertionError during cache operation, which may lead
> to
> > >> hangs and data inconsistency.
> > >>
> > >> Best Regards,
> > >> Ivan Rakov
> > >>
> > >>
> > >> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> > >>> Nikolay, thank you for such fast reaction. Tests are passing now.
> > >>>
> > >>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
> > >>>
> > >>>> Hello, Dmitriy.
> > >>>>
> > >>>> I fixed this issue, already.
> > >>>> Please, check it.
> > >>>>
> > >>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > >>>>> Hi Denis,
> > >>>>>
> > >>>>> currently anyway we have TC issue came from spark version
> migrations.
> > >>>>>
> > >>>>> I also currently experiencing challenges with my local environment
> setup.
> > >>>>> So I guess we have day or two to wait this fix.
> > >>>>>
> > >>>>> Sincerely.
> > >>>>> Dmitriy Pavlov
> > >>>>>
> > >>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> > >>>>>
> > >>>>>> May I ask when? The current status of the ticket is not clear.
> > >>>>>>
> > >>>>>> --
> > >>>>>> Denis
> > >>>>>>
> > >>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> > >>>> spiderru5597@gmail.com>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>> Yes, it will be in the release 2.6
> > >>>>>>>
> > >>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> > >>>>>>> написал(а):
> > >>>>>>>> Hi Igniters,
> > >>>>>>>>
> > >>>>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
> > >>>> to the
> > >>>>>>>> scope because it was initially discussed to be in this reselase.
> > >>>>>>>>
> > >>>>>>>> Alexey Stelmak, could you please confirm fix could be ready
> soon?
> > >>>>>>>>
> > >>>>>>>> Also I've cherry-picked javadoc fix.
> > >>>>>>>>
> > >>>>>>>> Sincerely,
> > >>>>>>>> Dmitriy Pavlov
> > >>>>>>>>
> > >>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Andrey Gura <ag...@apache.org>.
Igniters,
I've moved IGNITE-8780 [1] issue to the next release. It can't be
merged to AI 2.6 because it has many other dependent commits.
[1] https://issues.apache.org/jira/browse/IGNITE-8780
On Wed, Jul 4, 2018 at 6:05 PM Ivan Rakov <iv...@gmail.com> wrote:
>
> Andrey, thanks!
>
> I've cherry-picked the fixes to ignite-2.6 branch.
>
> Best Regards,
> Ivan Rakov
>
> On 04.07.2018 16:26, Andrey Gura wrote:
> > Ivan,
> >
> > I agree to include this fixes into AI 2.6 release. Please, feel free to merge.
> > On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com> wrote:
> >> Igniters,
> >>
> >> Do we still have chance to extend 2.6 scope?
> >>
> >> I propose to include two more tickets into 2.6:
> >> https://issues.apache.org/jira/browse/IGNITE-8769
> >> https://issues.apache.org/jira/browse/IGNITE-8910
> >>
> >> We had data races in our free lists implementation. Fixes prevent
> >> possibility of AssertionError during cache operation, which may lead to
> >> hangs and data inconsistency.
> >>
> >> Best Regards,
> >> Ivan Rakov
> >>
> >>
> >> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> >>> Nikolay, thank you for such fast reaction. Tests are passing now.
> >>>
> >>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
> >>>
> >>>> Hello, Dmitriy.
> >>>>
> >>>> I fixed this issue, already.
> >>>> Please, check it.
> >>>>
> >>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> >>>>> Hi Denis,
> >>>>>
> >>>>> currently anyway we have TC issue came from spark version migrations.
> >>>>>
> >>>>> I also currently experiencing challenges with my local environment setup.
> >>>>> So I guess we have day or two to wait this fix.
> >>>>>
> >>>>> Sincerely.
> >>>>> Dmitriy Pavlov
> >>>>>
> >>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> >>>>>
> >>>>>> May I ask when? The current status of the ticket is not clear.
> >>>>>>
> >>>>>> --
> >>>>>> Denis
> >>>>>>
> >>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> >>>> spiderru5597@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Yes, it will be in the release 2.6
> >>>>>>>
> >>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> >>>>>>> написал(а):
> >>>>>>>> Hi Igniters,
> >>>>>>>>
> >>>>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
> >>>> to the
> >>>>>>>> scope because it was initially discussed to be in this reselase.
> >>>>>>>>
> >>>>>>>> Alexey Stelmak, could you please confirm fix could be ready soon?
> >>>>>>>>
> >>>>>>>> Also I've cherry-picked javadoc fix.
> >>>>>>>>
> >>>>>>>> Sincerely,
> >>>>>>>> Dmitriy Pavlov
> >>>>>>>>
> >>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
>
Re: Ignite 2.6 emergency release suggestion
Posted by Ivan Rakov <iv...@gmail.com>.
Andrey, thanks!
I've cherry-picked the fixes to ignite-2.6 branch.
Best Regards,
Ivan Rakov
On 04.07.2018 16:26, Andrey Gura wrote:
> Ivan,
>
> I agree to include this fixes into AI 2.6 release. Please, feel free to merge.
> On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com> wrote:
>> Igniters,
>>
>> Do we still have chance to extend 2.6 scope?
>>
>> I propose to include two more tickets into 2.6:
>> https://issues.apache.org/jira/browse/IGNITE-8769
>> https://issues.apache.org/jira/browse/IGNITE-8910
>>
>> We had data races in our free lists implementation. Fixes prevent
>> possibility of AssertionError during cache operation, which may lead to
>> hangs and data inconsistency.
>>
>> Best Regards,
>> Ivan Rakov
>>
>>
>> On 27.06.2018 18:56, Dmitry Pavlov wrote:
>>> Nikolay, thank you for such fast reaction. Tests are passing now.
>>>
>>> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
>>>
>>>> Hello, Dmitriy.
>>>>
>>>> I fixed this issue, already.
>>>> Please, check it.
>>>>
>>>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
>>>>> Hi Denis,
>>>>>
>>>>> currently anyway we have TC issue came from spark version migrations.
>>>>>
>>>>> I also currently experiencing challenges with my local environment setup.
>>>>> So I guess we have day or two to wait this fix.
>>>>>
>>>>> Sincerely.
>>>>> Dmitriy Pavlov
>>>>>
>>>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
>>>>>
>>>>>> May I ask when? The current status of the ticket is not clear.
>>>>>>
>>>>>> --
>>>>>> Denis
>>>>>>
>>>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
>>>> spiderru5597@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Yes, it will be in the release 2.6
>>>>>>>
>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
>>>>>>> написал(а):
>>>>>>>> Hi Igniters,
>>>>>>>>
>>>>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
>>>> to the
>>>>>>>> scope because it was initially discussed to be in this reselase.
>>>>>>>>
>>>>>>>> Alexey Stelmak, could you please confirm fix could be ready soon?
>>>>>>>>
>>>>>>>> Also I've cherry-picked javadoc fix.
>>>>>>>>
>>>>>>>> Sincerely,
>>>>>>>> Dmitriy Pavlov
>>>>>>>>
>>>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
Re: Ignite 2.6 emergency release suggestion
Posted by Andrey Gura <ag...@apache.org>.
Ivan,
I agree to include this fixes into AI 2.6 release. Please, feel free to merge.
On Wed, Jul 4, 2018 at 4:08 PM Ivan Rakov <iv...@gmail.com> wrote:
>
> Igniters,
>
> Do we still have chance to extend 2.6 scope?
>
> I propose to include two more tickets into 2.6:
> https://issues.apache.org/jira/browse/IGNITE-8769
> https://issues.apache.org/jira/browse/IGNITE-8910
>
> We had data races in our free lists implementation. Fixes prevent
> possibility of AssertionError during cache operation, which may lead to
> hangs and data inconsistency.
>
> Best Regards,
> Ivan Rakov
>
>
> On 27.06.2018 18:56, Dmitry Pavlov wrote:
> > Nikolay, thank you for such fast reaction. Tests are passing now.
> >
> > ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
> >
> >> Hello, Dmitriy.
> >>
> >> I fixed this issue, already.
> >> Please, check it.
> >>
> >> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> >>> Hi Denis,
> >>>
> >>> currently anyway we have TC issue came from spark version migrations.
> >>>
> >>> I also currently experiencing challenges with my local environment setup.
> >>> So I guess we have day or two to wait this fix.
> >>>
> >>> Sincerely.
> >>> Dmitriy Pavlov
> >>>
> >>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> >>>
> >>>> May I ask when? The current status of the ticket is not clear.
> >>>>
> >>>> --
> >>>> Denis
> >>>>
> >>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> >> spiderru5597@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Yes, it will be in the release 2.6
> >>>>>
> >>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> >>>>> написал(а):
> >>>>>> Hi Igniters,
> >>>>>>
> >>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
> >> to the
> >>>>>> scope because it was initially discussed to be in this reselase.
> >>>>>>
> >>>>>> Alexey Stelmak, could you please confirm fix could be ready soon?
> >>>>>>
> >>>>>> Also I've cherry-picked javadoc fix.
> >>>>>>
> >>>>>> Sincerely,
> >>>>>> Dmitriy Pavlov
> >>>>>>
> >>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> >>>>>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Ivan Rakov <iv...@gmail.com>.
Igniters,
Do we still have chance to extend 2.6 scope?
I propose to include two more tickets into 2.6:
https://issues.apache.org/jira/browse/IGNITE-8769
https://issues.apache.org/jira/browse/IGNITE-8910
We had data races in our free lists implementation. Fixes prevent
possibility of AssertionError during cache operation, which may lead to
hangs and data inconsistency.
Best Regards,
Ivan Rakov
On 27.06.2018 18:56, Dmitry Pavlov wrote:
> Nikolay, thank you for such fast reaction. Tests are passing now.
>
> ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
>
>> Hello, Dmitriy.
>>
>> I fixed this issue, already.
>> Please, check it.
>>
>> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
>>> Hi Denis,
>>>
>>> currently anyway we have TC issue came from spark version migrations.
>>>
>>> I also currently experiencing challenges with my local environment setup.
>>> So I guess we have day or two to wait this fix.
>>>
>>> Sincerely.
>>> Dmitriy Pavlov
>>>
>>> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
>>>
>>>> May I ask when? The current status of the ticket is not clear.
>>>>
>>>> --
>>>> Denis
>>>>
>>>> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
>> spiderru5597@gmail.com>
>>>> wrote:
>>>>
>>>>> Yes, it will be in the release 2.6
>>>>>
>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
>>>>> написал(а):
>>>>>> Hi Igniters,
>>>>>>
>>>>>> I've returned https://issues.apache.org/jira/browse/IGNITE-8780
>> to the
>>>>>> scope because it was initially discussed to be in this reselase.
>>>>>>
>>>>>> Alexey Stelmak, could you please confirm fix could be ready soon?
>>>>>>
>>>>>> Also I've cherry-picked javadoc fix.
>>>>>>
>>>>>> Sincerely,
>>>>>> Dmitriy Pavlov
>>>>>>
>>>>>> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
>>>>>
Re: Ignite 2.6 emergency release suggestion
Posted by Nikolay Izhikov <ni...@apache.org>.
Also, Igniters, be aware
https://issues.apache.org/jira/browse/IGNITE-8534 merged to master and cherry picked to 2.6 branch.
В Вт, 26/06/2018 в 19:29 +0300, Nikolay Izhikov пишет:
> Hello, Igniters.
>
> We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
>
> IGNITE-6055 has to be included in 2.6, also.
> Final review from Vladimir required to merge this ticket.
>
> Do we have a chance to include this ticket to 2.6?
>
> В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> > Hi Igniters,
> >
> > I've prepared wiki page
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
> > started to reassign existing issues to 2.7.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > сб, 23 июн. 2018 г. в 2:58, Denis Magda <dm...@apache.org>:
> >
> > > Thanks folks!
> > >
> > > Dmitriy P., please proceed with the release finalization. Don't accept any
> > > other commits to 2.6.
> > >
> > > --
> > > Denis
> > >
> > > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > > valentin.kulichenko@gmail.com> wrote:
> > >
> > > > After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
> > > >
> > > > -Val
> > > >
> > > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > > valentin.kulichenko@gmail.com> wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> > >
> > > correct. I
> > > > > left a more detailed comment in the ticket. Hopefully, Mair will be
> > >
> > > able
> > > > to
> > > > > respond shortly and clarify.
> > > > >
> > > > > -Val
> > > > >
> > > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org>
> > >
> > > wrote:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > No, that's an honor for us to see you in this role ;) Both Andrey
> > >
> > > Gura,
> > > > > > Anton Vinogradov are our release-management veterans. Please feel free
> > > >
> > > > to
> > > > > > contact them directly.
> > > > > >
> > > > > > Could you take over this ticket review and include it in the release:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > >
> > > > > > It's not good that we have spring integration broken in some places in
> > > > > > several releases. I would treat is as a usability blocker and
> > > >
> > > > regression.
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Alexey,
> > > > > > >
> > > > > > > Sure, it will be honor for me.
> > > > > > >
> > > > > > > In the same time I relatevely new in this area, so I would highly
> > > > > > > appreciate any assistance of experienced community members to make
> > > >
> > > > this
> > > > > > > happen.
> > > > > > >
> > > > > > > Sincerely,
> > > > > > >
> > > > > > > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > > > > >
> > > > > > alexey.goncharuk@gmail.com
> > > > > > > > :
> > > > > > > > Denis,
> > > > > > > >
> > > > > > > > Currently, I am not aware of anybody who can immediately review
> > >
> > > and
> > > > > > > > sign-off the suggested patch. The original scope of tickets have
> > > >
> > > > been
> > > > > > > > resolved, so I suggest to move on with what we have now.
> > > > > > > >
> > > > > > > > I will not be able to continue with the release process until
> > > >
> > > > Thursday
> > > > > > > > next week.
> > > > > > > >
> > > > > > > > Dmitriy Pavlov, do you mind taking over and finishing the release?
> > > > > > > >
> > > > > > > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> > > > > > > >
> > > > > > > > > Folks,
> > > > > > > > >
> > > > > > > > > This release no longer reminds an emergency one :) Are we done
> > >
> > > with
> > > > > > the
> > > > > > > > > scope, who is a release manager?
> > > > > > > > >
> > > > > > > > > From my side, I'd like us to review and add the fix for broken
> > > >
> > > > Spring
> > > > > > > > > integration which is a significant regression:
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Denis
> > > > > > > > >
> > > > > > > > > On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > > > > > > > > alexey.goncharuk@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Petr,
> > > > > > > > > >
> > > > > > > > > > Who will be able to make the review for the suggested patch? I
> > > > > >
> > > > > > would
> > > > > > > > > like
> > > > > > > > > > to freeze the branch and start preparing the release.
> > > > > > > > > >
> > > > > > > > > > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr.weider@gmail.com
> > > >
> > > > :
> > > > > > > > > >
> > > > > > > > > > > Igniters,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I’d like to stage for 2.6 release also this issue [1].
> > > > > >
> > > > > > Corresponding
> > > > > > > > > PR
> > > > > > > > > > > [2] is ready for review and merge.
> > > > > > > > > > > This is not related to code additional configuration file for
> > > > > > >
> > > > > > > enabling
> > > > > > > > > > > support of Windows 10 WSL Environment.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > > > > > > > > > > [2] https://github.com/apache/ignite/pull/4194
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> > > > > >
> > > > > > akuznetsov@apache.org
> > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi,
> > > > > > > > > > > >
> > > > > > > > > > > > Fix for IGNITE-8722 (
> > > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8722
> > > > > > > > > > )
> > > > > > > > > > > is
> > > > > > > > > > > > ready.
> > > > > > > > > > > >
> > > > > > > > > > > > Diff
> > > > > > > > > > > >
> > > > > > > > > > > >
> > >
> > > https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > > > > > > > > > > >
> > > > > > > > > > > > TC looks good for me.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > > > > > > > > > > >
> > > > > > > > > > > > I'm ready to merge to master and 2.6 branches.
> > > > > > > > > > > > Please approve.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Alexey Kuznetsov
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
Nikolay, thank you for such fast reaction. Tests are passing now.
ср, 27 июн. 2018 г. в 17:28, Nikolay Izhikov <ni...@apache.org>:
> Hello, Dmitriy.
>
> I fixed this issue, already.
> Please, check it.
>
> В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> > Hi Denis,
> >
> > currently anyway we have TC issue came from spark version migrations.
> >
> > I also currently experiencing challenges with my local environment setup.
> > So I guess we have day or two to wait this fix.
> >
> > Sincerely.
> > Dmitriy Pavlov
> >
> > ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> >
> > > May I ask when? The current status of the ticket is not clear.
> > >
> > > --
> > > Denis
> > >
> > > On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <
> spiderru5597@gmail.com>
> > > wrote:
> > >
> > > > Yes, it will be in the release 2.6
> > > >
> > > > > 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> > > >
> > > > написал(а):
> > > > >
> > > > > Hi Igniters,
> > > > >
> > > > > I've returned https://issues.apache.org/jira/browse/IGNITE-8780
> to the
> > > > > scope because it was initially discussed to be in this reselase.
> > > > >
> > > > > Alexey Stelmak, could you please confirm fix could be ready soon?
> > > > >
> > > > > Also I've cherry-picked javadoc fix.
> > > > >
> > > > > Sincerely,
> > > > > Dmitriy Pavlov
> > > > >
> > > > > вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> > > >
> > > >
Re: Ignite 2.6 emergency release suggestion
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Dmitriy.
I fixed this issue, already.
Please, check it.
В Ср, 27/06/2018 в 16:55 +0300, Dmitry Pavlov пишет:
> Hi Denis,
>
> currently anyway we have TC issue came from spark version migrations.
>
> I also currently experiencing challenges with my local environment setup.
> So I guess we have day or two to wait this fix.
>
> Sincerely.
> Dmitriy Pavlov
>
> ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
>
> > May I ask when? The current status of the ticket is not clear.
> >
> > --
> > Denis
> >
> > On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <sp...@gmail.com>
> > wrote:
> >
> > > Yes, it will be in the release 2.6
> > >
> > > > 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> > >
> > > написал(а):
> > > >
> > > > Hi Igniters,
> > > >
> > > > I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> > > > scope because it was initially discussed to be in this reselase.
> > > >
> > > > Alexey Stelmak, could you please confirm fix could be ready soon?
> > > >
> > > > Also I've cherry-picked javadoc fix.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> > >
> > >
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
Hi Denis,
currently anyway we have TC issue came from spark version migrations.
I also currently experiencing challenges with my local environment setup.
So I guess we have day or two to wait this fix.
Sincerely.
Dmitriy Pavlov
ср, 27 июн. 2018 г. в 16:05, Denis Magda <dm...@apache.org>:
> May I ask when? The current status of the ticket is not clear.
>
> --
> Denis
>
> On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <sp...@gmail.com>
> wrote:
>
> > Yes, it will be in the release 2.6
> >
> > > 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> > написал(а):
> > >
> > > Hi Igniters,
> > >
> > > I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> > > scope because it was initially discussed to be in this reselase.
> > >
> > > Alexey Stelmak, could you please confirm fix could be ready soon?
> > >
> > > Also I've cherry-picked javadoc fix.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Denis Magda <dm...@apache.org>.
May I ask when? The current status of the ticket is not clear.
--
Denis
On Wed, Jun 27, 2018 at 7:27 AM Spider (Alexey) <sp...@gmail.com>
wrote:
> Yes, it will be in the release 2.6
>
> > 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com>
> написал(а):
> >
> > Hi Igniters,
> >
> > I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> > scope because it was initially discussed to be in this reselase.
> >
> > Alexey Stelmak, could you please confirm fix could be ready soon?
> >
> > Also I've cherry-picked javadoc fix.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
>
>
Re: Ignite 2.6 emergency release suggestion
Posted by "Spider (Alexey)" <sp...@gmail.com>.
Yes, it will be in the release 2.6
> 27 июня 2018 г., в 14:15, Dmitry Pavlov <dp...@gmail.com> написал(а):
>
> Hi Igniters,
>
> I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
> scope because it was initially discussed to be in this reselase.
>
> Alexey Stelmak, could you please confirm fix could be ready soon?
>
> Also I've cherry-picked javadoc fix.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
Hi Igniters,
I've returned https://issues.apache.org/jira/browse/IGNITE-8780 to the
scope because it was initially discussed to be in this reselase.
Alexey Stelmak, could you please confirm fix could be ready soon?
Also I've cherry-picked javadoc fix.
Sincerely,
Dmitriy Pavlov
вт, 26 июн. 2018 г. в 20:33, Denis Magda <dm...@apache.org>:
> +1 to Dmitriy's stance.
>
> IGNITE-6055 doesn't look like something that needs to halt this release.
> Plus, let me remind us that it's an emergency release that has to solve
> severe problems at the persistence layer. What planned to be released
> within 2 weeks got stuck for almost a month.
>
> Dmitriy, as a release manager, please announce official code freeze (send a
> separate message) and pass the release to the QA members of the community
> for final testing.
>
> --
> Denis
>
>
> On Tue, Jun 26, 2018 at 12:49 PM Dmitry Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Nikolay,
> >
> > why this ticket should be included into emergency release?
> >
> > I agree in case
> > 1) Vladimir has time to review it now,
> > 2) we have clear motivation why it is emergency change.
> >
> > We are still going to do 2.7 release as normal Ignite release later.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вт, 26 июн. 2018 г. в 19:30, Nikolay Izhikov <ni...@apache.org>:
> >
> > > Hello, Igniters.
> > >
> > > We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
> > >
> > > IGNITE-6055 has to be included in 2.6, also.
> > > Final review from Vladimir required to merge this ticket.
> > >
> > > Do we have a chance to include this ticket to 2.6?
> > >
> > > В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> > > > Hi Igniters,
> > > >
> > > > I've prepared wiki page
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6
> > and
> > > > started to reassign existing issues to 2.7.
> > > >
> > > > Sincerely,
> > > > Dmitriy Pavlov
> > > >
> > > > сб, 23 июн. 2018 г. в 2:58, Denis Magda <dm...@apache.org>:
> > > >
> > > > > Thanks folks!
> > > > >
> > > > > Dmitriy P., please proceed with the release finalization. Don't
> > accept
> > > any
> > > > > other commits to 2.6.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > > > > valentin.kulichenko@gmail.com> wrote:
> > > > >
> > > > > > After a conversation with Amir, IGNITE-8740 is merged to master
> and
> > > 2.6.
> > > > > >
> > > > > > -Val
> > > > > >
> > > > > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > > > > valentin.kulichenko@gmail.com> wrote:
> > > > > >
> > > > > > > Guys,
> > > > > > >
> > > > > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> > > > >
> > > > > correct. I
> > > > > > > left a more detailed comment in the ticket. Hopefully, Mair
> will
> > be
> > > > >
> > > > > able
> > > > > > to
> > > > > > > respond shortly and clarify.
> > > > > > >
> > > > > > > -Val
> > > > > > >
> > > > > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <
> dmagda@apache.org>
> > > > >
> > > > > wrote:
> > > > > > >
> > > > > > > > Dmitriy,
> > > > > > > >
> > > > > > > > No, that's an honor for us to see you in this role ;) Both
> > Andrey
> > > > >
> > > > > Gura,
> > > > > > > > Anton Vinogradov are our release-management veterans. Please
> > > feel free
> > > > > >
> > > > > > to
> > > > > > > > contact them directly.
> > > > > > > >
> > > > > > > > Could you take over this ticket review and include it in the
> > > release:
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > >
> > > > > > > > It's not good that we have spring integration broken in some
> > > places in
> > > > > > > > several releases. I would treat is as a usability blocker and
> > > > > >
> > > > > > regression.
> > > > > > > >
> > > > > > > > --
> > > > > > > > Denis
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <
> > > dpavlov.spb@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Alexey,
> > > > > > > > >
> > > > > > > > > Sure, it will be honor for me.
> > > > > > > > >
> > > > > > > > > In the same time I relatevely new in this area, so I would
> > > highly
> > > > > > > > > appreciate any assistance of experienced community members
> to
> > > make
> > > > > >
> > > > > > this
> > > > > > > > > happen.
> > > > > > > > >
> > > > > > > > > Sincerely,
> > > > > > > > >
> > > > > > > > > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > > > > > > >
> > > > > > > > alexey.goncharuk@gmail.com
> > > > > > > > > > :
> > > > > > > > > > Denis,
> > > > > > > > > >
> > > > > > > > > > Currently, I am not aware of anybody who can immediately
> > > review
> > > > >
> > > > > and
> > > > > > > > > > sign-off the suggested patch. The original scope of
> tickets
> > > have
> > > > > >
> > > > > > been
> > > > > > > > > > resolved, so I suggest to move on with what we have now.
> > > > > > > > > >
> > > > > > > > > > I will not be able to continue with the release process
> > until
> > > > > >
> > > > > > Thursday
> > > > > > > > > > next week.
> > > > > > > > > >
> > > > > > > > > > Dmitriy Pavlov, do you mind taking over and finishing the
> > > release?
> > > > > > > > > >
> > > > > > > > > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <
> > dmagda@apache.org
> > > >:
> > > > > > > > > >
> > > > > > > > > > > Folks,
> > > > > > > > > > >
> > > > > > > > > > > This release no longer reminds an emergency one :) Are
> we
> > > done
> > > > >
> > > > > with
> > > > > > > > the
> > > > > > > > > > > scope, who is a release manager?
> > > > > > > > > > >
> > > > > > > > > > > From my side, I'd like us to review and add the fix for
> > > broken
> > > > > >
> > > > > > Spring
> > > > > > > > > > > integration which is a significant regression:
> > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Denis
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > > > > > > > > > > alexey.goncharuk@gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi Petr,
> > > > > > > > > > > >
> > > > > > > > > > > > Who will be able to make the review for the suggested
> > > patch? I
> > > > > > > >
> > > > > > > > would
> > > > > > > > > > > like
> > > > > > > > > > > > to freeze the branch and start preparing the release.
> > > > > > > > > > > >
> > > > > > > > > > > > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <
> > > mr.weider@gmail.com
> > > > > >
> > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > Igniters,
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > I’d like to stage for 2.6 release also this issue
> > [1].
> > > > > > > >
> > > > > > > > Corresponding
> > > > > > > > > > > PR
> > > > > > > > > > > > > [2] is ready for review and merge.
> > > > > > > > > > > > > This is not related to code additional
> configuration
> > > file for
> > > > > > > > >
> > > > > > > > > enabling
> > > > > > > > > > > > > support of Windows 10 WSL Environment.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > [1]
> > https://issues.apache.org/jira/browse/IGNITE-8804
> > > > > > > > > > > > > [2] https://github.com/apache/ignite/pull/4194
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> > > > > > > >
> > > > > > > > akuznetsov@apache.org
> > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Hi,
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Fix for IGNITE-8722 (
> > > > > > > > > > >
> > > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8722
> > > > > > > > > > > > )
> > > > > > > > > > > > > is
> > > > > > > > > > > > > > ready.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Diff
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > >
> > >
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > TC looks good for me.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > >
> > > > >
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I'm ready to merge to master and 2.6 branches.
> > > > > > > > > > > > > > Please approve.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Denis Magda <dm...@apache.org>.
+1 to Dmitriy's stance.
IGNITE-6055 doesn't look like something that needs to halt this release.
Plus, let me remind us that it's an emergency release that has to solve
severe problems at the persistence layer. What planned to be released
within 2 weeks got stuck for almost a month.
Dmitriy, as a release manager, please announce official code freeze (send a
separate message) and pass the release to the QA members of the community
for final testing.
--
Denis
On Tue, Jun 26, 2018 at 12:49 PM Dmitry Pavlov <dp...@gmail.com>
wrote:
> Hi Nikolay,
>
> why this ticket should be included into emergency release?
>
> I agree in case
> 1) Vladimir has time to review it now,
> 2) we have clear motivation why it is emergency change.
>
> We are still going to do 2.7 release as normal Ignite release later.
>
> Sincerely,
> Dmitriy Pavlov
>
> вт, 26 июн. 2018 г. в 19:30, Nikolay Izhikov <ni...@apache.org>:
>
> > Hello, Igniters.
> >
> > We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
> >
> > IGNITE-6055 has to be included in 2.6, also.
> > Final review from Vladimir required to merge this ticket.
> >
> > Do we have a chance to include this ticket to 2.6?
> >
> > В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> > > Hi Igniters,
> > >
> > > I've prepared wiki page
> > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6
> and
> > > started to reassign existing issues to 2.7.
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > сб, 23 июн. 2018 г. в 2:58, Denis Magda <dm...@apache.org>:
> > >
> > > > Thanks folks!
> > > >
> > > > Dmitriy P., please proceed with the release finalization. Don't
> accept
> > any
> > > > other commits to 2.6.
> > > >
> > > > --
> > > > Denis
> > > >
> > > > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > > > valentin.kulichenko@gmail.com> wrote:
> > > >
> > > > > After a conversation with Amir, IGNITE-8740 is merged to master and
> > 2.6.
> > > > >
> > > > > -Val
> > > > >
> > > > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > > > valentin.kulichenko@gmail.com> wrote:
> > > > >
> > > > > > Guys,
> > > > > >
> > > > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> > > >
> > > > correct. I
> > > > > > left a more detailed comment in the ticket. Hopefully, Mair will
> be
> > > >
> > > > able
> > > > > to
> > > > > > respond shortly and clarify.
> > > > > >
> > > > > > -Val
> > > > > >
> > > > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org>
> > > >
> > > > wrote:
> > > > > >
> > > > > > > Dmitriy,
> > > > > > >
> > > > > > > No, that's an honor for us to see you in this role ;) Both
> Andrey
> > > >
> > > > Gura,
> > > > > > > Anton Vinogradov are our release-management veterans. Please
> > feel free
> > > > >
> > > > > to
> > > > > > > contact them directly.
> > > > > > >
> > > > > > > Could you take over this ticket review and include it in the
> > release:
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > >
> > > > > > > It's not good that we have spring integration broken in some
> > places in
> > > > > > > several releases. I would treat is as a usability blocker and
> > > > >
> > > > > regression.
> > > > > > >
> > > > > > > --
> > > > > > > Denis
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <
> > dpavlov.spb@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Alexey,
> > > > > > > >
> > > > > > > > Sure, it will be honor for me.
> > > > > > > >
> > > > > > > > In the same time I relatevely new in this area, so I would
> > highly
> > > > > > > > appreciate any assistance of experienced community members to
> > make
> > > > >
> > > > > this
> > > > > > > > happen.
> > > > > > > >
> > > > > > > > Sincerely,
> > > > > > > >
> > > > > > > > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > > > > > >
> > > > > > > alexey.goncharuk@gmail.com
> > > > > > > > > :
> > > > > > > > > Denis,
> > > > > > > > >
> > > > > > > > > Currently, I am not aware of anybody who can immediately
> > review
> > > >
> > > > and
> > > > > > > > > sign-off the suggested patch. The original scope of tickets
> > have
> > > > >
> > > > > been
> > > > > > > > > resolved, so I suggest to move on with what we have now.
> > > > > > > > >
> > > > > > > > > I will not be able to continue with the release process
> until
> > > > >
> > > > > Thursday
> > > > > > > > > next week.
> > > > > > > > >
> > > > > > > > > Dmitriy Pavlov, do you mind taking over and finishing the
> > release?
> > > > > > > > >
> > > > > > > > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <
> dmagda@apache.org
> > >:
> > > > > > > > >
> > > > > > > > > > Folks,
> > > > > > > > > >
> > > > > > > > > > This release no longer reminds an emergency one :) Are we
> > done
> > > >
> > > > with
> > > > > > > the
> > > > > > > > > > scope, who is a release manager?
> > > > > > > > > >
> > > > > > > > > > From my side, I'd like us to review and add the fix for
> > broken
> > > > >
> > > > > Spring
> > > > > > > > > > integration which is a significant regression:
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Denis
> > > > > > > > > >
> > > > > > > > > > On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > > > > > > > > > alexey.goncharuk@gmail.com>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Petr,
> > > > > > > > > > >
> > > > > > > > > > > Who will be able to make the review for the suggested
> > patch? I
> > > > > > >
> > > > > > > would
> > > > > > > > > > like
> > > > > > > > > > > to freeze the branch and start preparing the release.
> > > > > > > > > > >
> > > > > > > > > > > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <
> > mr.weider@gmail.com
> > > > >
> > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > Igniters,
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > I’d like to stage for 2.6 release also this issue
> [1].
> > > > > > >
> > > > > > > Corresponding
> > > > > > > > > > PR
> > > > > > > > > > > > [2] is ready for review and merge.
> > > > > > > > > > > > This is not related to code additional configuration
> > file for
> > > > > > > >
> > > > > > > > enabling
> > > > > > > > > > > > support of Windows 10 WSL Environment.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > [1]
> https://issues.apache.org/jira/browse/IGNITE-8804
> > > > > > > > > > > > [2] https://github.com/apache/ignite/pull/4194
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> > > > > > >
> > > > > > > akuznetsov@apache.org
> > > > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > Hi,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Fix for IGNITE-8722 (
> > > > > > > > > >
> > > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8722
> > > > > > > > > > > )
> > > > > > > > > > > > is
> > > > > > > > > > > > > ready.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Diff
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > >
> > > >
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > > > > > > > > > > > >
> > > > > > > > > > > > > TC looks good for me.
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > >
> > > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > > > > > > > > > > > >
> > > > > > > > > > > > > I'm ready to merge to master and 2.6 branches.
> > > > > > > > > > > > > Please approve.
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > > >
> > > > > > > > > > > >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
Hi Nikolay,
why this ticket should be included into emergency release?
I agree in case
1) Vladimir has time to review it now,
2) we have clear motivation why it is emergency change.
We are still going to do 2.7 release as normal Ignite release later.
Sincerely,
Dmitriy Pavlov
вт, 26 июн. 2018 г. в 19:30, Nikolay Izhikov <ni...@apache.org>:
> Hello, Igniters.
>
> We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
>
> IGNITE-6055 has to be included in 2.6, also.
> Final review from Vladimir required to merge this ticket.
>
> Do we have a chance to include this ticket to 2.6?
>
> В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> > Hi Igniters,
> >
> > I've prepared wiki page
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
> > started to reassign existing issues to 2.7.
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > сб, 23 июн. 2018 г. в 2:58, Denis Magda <dm...@apache.org>:
> >
> > > Thanks folks!
> > >
> > > Dmitriy P., please proceed with the release finalization. Don't accept
> any
> > > other commits to 2.6.
> > >
> > > --
> > > Denis
> > >
> > > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > > valentin.kulichenko@gmail.com> wrote:
> > >
> > > > After a conversation with Amir, IGNITE-8740 is merged to master and
> 2.6.
> > > >
> > > > -Val
> > > >
> > > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > > valentin.kulichenko@gmail.com> wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> > >
> > > correct. I
> > > > > left a more detailed comment in the ticket. Hopefully, Mair will be
> > >
> > > able
> > > > to
> > > > > respond shortly and clarify.
> > > > >
> > > > > -Val
> > > > >
> > > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org>
> > >
> > > wrote:
> > > > >
> > > > > > Dmitriy,
> > > > > >
> > > > > > No, that's an honor for us to see you in this role ;) Both Andrey
> > >
> > > Gura,
> > > > > > Anton Vinogradov are our release-management veterans. Please
> feel free
> > > >
> > > > to
> > > > > > contact them directly.
> > > > > >
> > > > > > Could you take over this ticket review and include it in the
> release:
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > >
> > > > > > It's not good that we have spring integration broken in some
> places in
> > > > > > several releases. I would treat is as a usability blocker and
> > > >
> > > > regression.
> > > > > >
> > > > > > --
> > > > > > Denis
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <
> dpavlov.spb@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Alexey,
> > > > > > >
> > > > > > > Sure, it will be honor for me.
> > > > > > >
> > > > > > > In the same time I relatevely new in this area, so I would
> highly
> > > > > > > appreciate any assistance of experienced community members to
> make
> > > >
> > > > this
> > > > > > > happen.
> > > > > > >
> > > > > > > Sincerely,
> > > > > > >
> > > > > > > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > > > > >
> > > > > > alexey.goncharuk@gmail.com
> > > > > > > > :
> > > > > > > > Denis,
> > > > > > > >
> > > > > > > > Currently, I am not aware of anybody who can immediately
> review
> > >
> > > and
> > > > > > > > sign-off the suggested patch. The original scope of tickets
> have
> > > >
> > > > been
> > > > > > > > resolved, so I suggest to move on with what we have now.
> > > > > > > >
> > > > > > > > I will not be able to continue with the release process until
> > > >
> > > > Thursday
> > > > > > > > next week.
> > > > > > > >
> > > > > > > > Dmitriy Pavlov, do you mind taking over and finishing the
> release?
> > > > > > > >
> > > > > > > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dmagda@apache.org
> >:
> > > > > > > >
> > > > > > > > > Folks,
> > > > > > > > >
> > > > > > > > > This release no longer reminds an emergency one :) Are we
> done
> > >
> > > with
> > > > > > the
> > > > > > > > > scope, who is a release manager?
> > > > > > > > >
> > > > > > > > > From my side, I'd like us to review and add the fix for
> broken
> > > >
> > > > Spring
> > > > > > > > > integration which is a significant regression:
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Denis
> > > > > > > > >
> > > > > > > > > On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > > > > > > > > alexey.goncharuk@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Petr,
> > > > > > > > > >
> > > > > > > > > > Who will be able to make the review for the suggested
> patch? I
> > > > > >
> > > > > > would
> > > > > > > > > like
> > > > > > > > > > to freeze the branch and start preparing the release.
> > > > > > > > > >
> > > > > > > > > > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <
> mr.weider@gmail.com
> > > >
> > > > :
> > > > > > > > > >
> > > > > > > > > > > Igniters,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I’d like to stage for 2.6 release also this issue [1].
> > > > > >
> > > > > > Corresponding
> > > > > > > > > PR
> > > > > > > > > > > [2] is ready for review and merge.
> > > > > > > > > > > This is not related to code additional configuration
> file for
> > > > > > >
> > > > > > > enabling
> > > > > > > > > > > support of Windows 10 WSL Environment.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > > > > > > > > > > [2] https://github.com/apache/ignite/pull/4194
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> > > > > >
> > > > > > akuznetsov@apache.org
> > > > > > > >
> > > > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > Hi,
> > > > > > > > > > > >
> > > > > > > > > > > > Fix for IGNITE-8722 (
> > > > > > > > >
> > > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8722
> > > > > > > > > > )
> > > > > > > > > > > is
> > > > > > > > > > > > ready.
> > > > > > > > > > > >
> > > > > > > > > > > > Diff
> > > > > > > > > > > >
> > > > > > > > > > > >
> > >
> > >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > > > > > > > > > > >
> > > > > > > > > > > > TC looks good for me.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > >
> > >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > > > > > > > > > > >
> > > > > > > > > > > > I'm ready to merge to master and 2.6 branches.
> > > > > > > > > > > > Please approve.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > > >
> > > > > > > > > > >
Re: Ignite 2.6 emergency release suggestion
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, Igniters.
We have private discussion with Vladimir Ozerov and Dmitry Pavlov.
IGNITE-6055 has to be included in 2.6, also.
Final review from Vladimir required to merge this ticket.
Do we have a chance to include this ticket to 2.6?
В Вт, 26/06/2018 в 19:26 +0300, Dmitry Pavlov пишет:
> Hi Igniters,
>
> I've prepared wiki page
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
> started to reassign existing issues to 2.7.
>
> Sincerely,
> Dmitriy Pavlov
>
> сб, 23 июн. 2018 г. в 2:58, Denis Magda <dm...@apache.org>:
>
> > Thanks folks!
> >
> > Dmitriy P., please proceed with the release finalization. Don't accept any
> > other commits to 2.6.
> >
> > --
> > Denis
> >
> > On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> > valentin.kulichenko@gmail.com> wrote:
> >
> > > After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
> > >
> > > -Val
> > >
> > > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > > valentin.kulichenko@gmail.com> wrote:
> > >
> > > > Guys,
> > > >
> > > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> >
> > correct. I
> > > > left a more detailed comment in the ticket. Hopefully, Mair will be
> >
> > able
> > > to
> > > > respond shortly and clarify.
> > > >
> > > > -Val
> > > >
> > > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org>
> >
> > wrote:
> > > >
> > > > > Dmitriy,
> > > > >
> > > > > No, that's an honor for us to see you in this role ;) Both Andrey
> >
> > Gura,
> > > > > Anton Vinogradov are our release-management veterans. Please feel free
> > >
> > > to
> > > > > contact them directly.
> > > > >
> > > > > Could you take over this ticket review and include it in the release:
> > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > >
> > > > > It's not good that we have spring integration broken in some places in
> > > > > several releases. I would treat is as a usability blocker and
> > >
> > > regression.
> > > > >
> > > > > --
> > > > > Denis
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Alexey,
> > > > > >
> > > > > > Sure, it will be honor for me.
> > > > > >
> > > > > > In the same time I relatevely new in this area, so I would highly
> > > > > > appreciate any assistance of experienced community members to make
> > >
> > > this
> > > > > > happen.
> > > > > >
> > > > > > Sincerely,
> > > > > >
> > > > > > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > > > >
> > > > > alexey.goncharuk@gmail.com
> > > > > > > :
> > > > > > > Denis,
> > > > > > >
> > > > > > > Currently, I am not aware of anybody who can immediately review
> >
> > and
> > > > > > > sign-off the suggested patch. The original scope of tickets have
> > >
> > > been
> > > > > > > resolved, so I suggest to move on with what we have now.
> > > > > > >
> > > > > > > I will not be able to continue with the release process until
> > >
> > > Thursday
> > > > > > > next week.
> > > > > > >
> > > > > > > Dmitriy Pavlov, do you mind taking over and finishing the release?
> > > > > > >
> > > > > > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> > > > > > >
> > > > > > > > Folks,
> > > > > > > >
> > > > > > > > This release no longer reminds an emergency one :) Are we done
> >
> > with
> > > > > the
> > > > > > > > scope, who is a release manager?
> > > > > > > >
> > > > > > > > From my side, I'd like us to review and add the fix for broken
> > >
> > > Spring
> > > > > > > > integration which is a significant regression:
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8740
> > > > > > > >
> > > > > > > > --
> > > > > > > > Denis
> > > > > > > >
> > > > > > > > On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > > > > > > > alexey.goncharuk@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Petr,
> > > > > > > > >
> > > > > > > > > Who will be able to make the review for the suggested patch? I
> > > > >
> > > > > would
> > > > > > > > like
> > > > > > > > > to freeze the branch and start preparing the release.
> > > > > > > > >
> > > > > > > > > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr.weider@gmail.com
> > >
> > > :
> > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > I’d like to stage for 2.6 release also this issue [1].
> > > > >
> > > > > Corresponding
> > > > > > > > PR
> > > > > > > > > > [2] is ready for review and merge.
> > > > > > > > > > This is not related to code additional configuration file for
> > > > > >
> > > > > > enabling
> > > > > > > > > > support of Windows 10 WSL Environment.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > > > > > > > > > [2] https://github.com/apache/ignite/pull/4194
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> > > > >
> > > > > akuznetsov@apache.org
> > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > Hi,
> > > > > > > > > > >
> > > > > > > > > > > Fix for IGNITE-8722 (
> > > > > > > >
> > > > > > > > https://issues.apache.org/jira/browse/IGNITE-8722
> > > > > > > > > )
> > > > > > > > > > is
> > > > > > > > > > > ready.
> > > > > > > > > > >
> > > > > > > > > > > Diff
> > > > > > > > > > >
> > > > > > > > > > >
> >
> > https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > > > > > > > > > >
> > > > > > > > > > > TC looks good for me.
> > > > > > > > > > >
> > > > > > > > > > >
> >
> > https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > > > > > > > > > >
> > > > > > > > > > > I'm ready to merge to master and 2.6 branches.
> > > > > > > > > > > Please approve.
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Alexey Kuznetsov
> > > > > > > > > >
> > > > > > > > > >
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
Hi Igniters,
I've prepared wiki page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6 and
started to reassign existing issues to 2.7.
Sincerely,
Dmitriy Pavlov
сб, 23 июн. 2018 г. в 2:58, Denis Magda <dm...@apache.org>:
> Thanks folks!
>
> Dmitriy P., please proceed with the release finalization. Don't accept any
> other commits to 2.6.
>
> --
> Denis
>
> On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
> > After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
> >
> > -Val
> >
> > On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> > valentin.kulichenko@gmail.com> wrote:
> >
> > > Guys,
> > >
> > > I reviewed changes in IGNITE-8740, but I'm not sure the fix is
> correct. I
> > > left a more detailed comment in the ticket. Hopefully, Mair will be
> able
> > to
> > > respond shortly and clarify.
> > >
> > > -Val
> > >
> > > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org>
> wrote:
> > >
> > >> Dmitriy,
> > >>
> > >> No, that's an honor for us to see you in this role ;) Both Andrey
> Gura,
> > >> Anton Vinogradov are our release-management veterans. Please feel free
> > to
> > >> contact them directly.
> > >>
> > >> Could you take over this ticket review and include it in the release:
> > >> https://issues.apache.org/jira/browse/IGNITE-8740
> > >>
> > >> It's not good that we have spring integration broken in some places in
> > >> several releases. I would treat is as a usability blocker and
> > regression.
> > >>
> > >> --
> > >> Denis
> > >>
> > >>
> > >>
> > >> On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Alexey,
> > >> >
> > >> > Sure, it will be honor for me.
> > >> >
> > >> > In the same time I relatevely new in this area, so I would highly
> > >> > appreciate any assistance of experienced community members to make
> > this
> > >> > happen.
> > >> >
> > >> > Sincerely,
> > >> >
> > >> > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> > >> alexey.goncharuk@gmail.com
> > >> > >:
> > >> >
> > >> > > Denis,
> > >> > >
> > >> > > Currently, I am not aware of anybody who can immediately review
> and
> > >> > > sign-off the suggested patch. The original scope of tickets have
> > been
> > >> > > resolved, so I suggest to move on with what we have now.
> > >> > >
> > >> > > I will not be able to continue with the release process until
> > Thursday
> > >> > > next week.
> > >> > >
> > >> > > Dmitriy Pavlov, do you mind taking over and finishing the release?
> > >> > >
> > >> > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> > >> > >
> > >> > >> Folks,
> > >> > >>
> > >> > >> This release no longer reminds an emergency one :) Are we done
> with
> > >> the
> > >> > >> scope, who is a release manager?
> > >> > >>
> > >> > >> From my side, I'd like us to review and add the fix for broken
> > Spring
> > >> > >> integration which is a significant regression:
> > >> > >> https://issues.apache.org/jira/browse/IGNITE-8740
> > >> > >>
> > >> > >> --
> > >> > >> Denis
> > >> > >>
> > >> > >> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > >> > >> alexey.goncharuk@gmail.com>
> > >> > >> wrote:
> > >> > >>
> > >> > >> > Hi Petr,
> > >> > >> >
> > >> > >> > Who will be able to make the review for the suggested patch? I
> > >> would
> > >> > >> like
> > >> > >> > to freeze the branch and start preparing the release.
> > >> > >> >
> > >> > >> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr.weider@gmail.com
> >:
> > >> > >> >
> > >> > >> > > Igniters,
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > I’d like to stage for 2.6 release also this issue [1].
> > >> Corresponding
> > >> > >> PR
> > >> > >> > > [2] is ready for review and merge.
> > >> > >> > > This is not related to code additional configuration file for
> > >> > enabling
> > >> > >> > > support of Windows 10 WSL Environment.
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > >> > >> > > [2] https://github.com/apache/ignite/pull/4194
> > >> > >> > >
> > >> > >> > >
> > >> > >> > >
> > >> > >> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> > >> akuznetsov@apache.org
> > >> > >
> > >> > >> > > wrote:
> > >> > >> > > >
> > >> > >> > > > Hi,
> > >> > >> > > >
> > >> > >> > > > Fix for IGNITE-8722 (
> > >> > >> https://issues.apache.org/jira/browse/IGNITE-8722
> > >> > >> > )
> > >> > >> > > is
> > >> > >> > > > ready.
> > >> > >> > > >
> > >> > >> > > > Diff
> > >> > >> > > >
> > >> > >> > > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> >
> > >>
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > >> > >> > > >
> > >> > >> > > > TC looks good for me.
> > >> > >> > > >
> > >> > >> > > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> >
> > >>
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > >> > >> > > >
> > >> > >> > > > I'm ready to merge to master and 2.6 branches.
> > >> > >> > > > Please approve.
> > >> > >> > > >
> > >> > >> > > > --
> > >> > >> > > > Alexey Kuznetsov
> > >> > >> > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Denis Magda <dm...@apache.org>.
Thanks folks!
Dmitriy P., please proceed with the release finalization. Don't accept any
other commits to 2.6.
--
Denis
On Fri, Jun 22, 2018 at 4:32 PM Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:
> After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
>
> -Val
>
> On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
> valentin.kulichenko@gmail.com> wrote:
>
> > Guys,
> >
> > I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
> > left a more detailed comment in the ticket. Hopefully, Mair will be able
> to
> > respond shortly and clarify.
> >
> > -Val
> >
> > On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org> wrote:
> >
> >> Dmitriy,
> >>
> >> No, that's an honor for us to see you in this role ;) Both Andrey Gura,
> >> Anton Vinogradov are our release-management veterans. Please feel free
> to
> >> contact them directly.
> >>
> >> Could you take over this ticket review and include it in the release:
> >> https://issues.apache.org/jira/browse/IGNITE-8740
> >>
> >> It's not good that we have spring integration broken in some places in
> >> several releases. I would treat is as a usability blocker and
> regression.
> >>
> >> --
> >> Denis
> >>
> >>
> >>
> >> On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com>
> >> wrote:
> >>
> >> > Hi Alexey,
> >> >
> >> > Sure, it will be honor for me.
> >> >
> >> > In the same time I relatevely new in this area, so I would highly
> >> > appreciate any assistance of experienced community members to make
> this
> >> > happen.
> >> >
> >> > Sincerely,
> >> >
> >> > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> >> alexey.goncharuk@gmail.com
> >> > >:
> >> >
> >> > > Denis,
> >> > >
> >> > > Currently, I am not aware of anybody who can immediately review and
> >> > > sign-off the suggested patch. The original scope of tickets have
> been
> >> > > resolved, so I suggest to move on with what we have now.
> >> > >
> >> > > I will not be able to continue with the release process until
> Thursday
> >> > > next week.
> >> > >
> >> > > Dmitriy Pavlov, do you mind taking over and finishing the release?
> >> > >
> >> > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> >> > >
> >> > >> Folks,
> >> > >>
> >> > >> This release no longer reminds an emergency one :) Are we done with
> >> the
> >> > >> scope, who is a release manager?
> >> > >>
> >> > >> From my side, I'd like us to review and add the fix for broken
> Spring
> >> > >> integration which is a significant regression:
> >> > >> https://issues.apache.org/jira/browse/IGNITE-8740
> >> > >>
> >> > >> --
> >> > >> Denis
> >> > >>
> >> > >> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> >> > >> alexey.goncharuk@gmail.com>
> >> > >> wrote:
> >> > >>
> >> > >> > Hi Petr,
> >> > >> >
> >> > >> > Who will be able to make the review for the suggested patch? I
> >> would
> >> > >> like
> >> > >> > to freeze the branch and start preparing the release.
> >> > >> >
> >> > >> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
> >> > >> >
> >> > >> > > Igniters,
> >> > >> > >
> >> > >> > >
> >> > >> > > I’d like to stage for 2.6 release also this issue [1].
> >> Corresponding
> >> > >> PR
> >> > >> > > [2] is ready for review and merge.
> >> > >> > > This is not related to code additional configuration file for
> >> > enabling
> >> > >> > > support of Windows 10 WSL Environment.
> >> > >> > >
> >> > >> > >
> >> > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> >> > >> > > [2] https://github.com/apache/ignite/pull/4194
> >> > >> > >
> >> > >> > >
> >> > >> > >
> >> > >> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> >> akuznetsov@apache.org
> >> > >
> >> > >> > > wrote:
> >> > >> > > >
> >> > >> > > > Hi,
> >> > >> > > >
> >> > >> > > > Fix for IGNITE-8722 (
> >> > >> https://issues.apache.org/jira/browse/IGNITE-8722
> >> > >> > )
> >> > >> > > is
> >> > >> > > > ready.
> >> > >> > > >
> >> > >> > > > Diff
> >> > >> > > >
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> >> > >> > > >
> >> > >> > > > TC looks good for me.
> >> > >> > > >
> >> > >> > > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> >
> >>
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> >> > >> > > >
> >> > >> > > > I'm ready to merge to master and 2.6 branches.
> >> > >> > > > Please approve.
> >> > >> > > >
> >> > >> > > > --
> >> > >> > > > Alexey Kuznetsov
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> >
> >>
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Valentin Kulichenko <va...@gmail.com>.
After a conversation with Amir, IGNITE-8740 is merged to master and 2.6.
-Val
On Fri, Jun 22, 2018 at 2:52 PM Valentin Kulichenko <
valentin.kulichenko@gmail.com> wrote:
> Guys,
>
> I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
> left a more detailed comment in the ticket. Hopefully, Mair will be able to
> respond shortly and clarify.
>
> -Val
>
> On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org> wrote:
>
>> Dmitriy,
>>
>> No, that's an honor for us to see you in this role ;) Both Andrey Gura,
>> Anton Vinogradov are our release-management veterans. Please feel free to
>> contact them directly.
>>
>> Could you take over this ticket review and include it in the release:
>> https://issues.apache.org/jira/browse/IGNITE-8740
>>
>> It's not good that we have spring integration broken in some places in
>> several releases. I would treat is as a usability blocker and regression.
>>
>> --
>> Denis
>>
>>
>>
>> On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com>
>> wrote:
>>
>> > Hi Alexey,
>> >
>> > Sure, it will be honor for me.
>> >
>> > In the same time I relatevely new in this area, so I would highly
>> > appreciate any assistance of experienced community members to make this
>> > happen.
>> >
>> > Sincerely,
>> >
>> > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
>> alexey.goncharuk@gmail.com
>> > >:
>> >
>> > > Denis,
>> > >
>> > > Currently, I am not aware of anybody who can immediately review and
>> > > sign-off the suggested patch. The original scope of tickets have been
>> > > resolved, so I suggest to move on with what we have now.
>> > >
>> > > I will not be able to continue with the release process until Thursday
>> > > next week.
>> > >
>> > > Dmitriy Pavlov, do you mind taking over and finishing the release?
>> > >
>> > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
>> > >
>> > >> Folks,
>> > >>
>> > >> This release no longer reminds an emergency one :) Are we done with
>> the
>> > >> scope, who is a release manager?
>> > >>
>> > >> From my side, I'd like us to review and add the fix for broken Spring
>> > >> integration which is a significant regression:
>> > >> https://issues.apache.org/jira/browse/IGNITE-8740
>> > >>
>> > >> --
>> > >> Denis
>> > >>
>> > >> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
>> > >> alexey.goncharuk@gmail.com>
>> > >> wrote:
>> > >>
>> > >> > Hi Petr,
>> > >> >
>> > >> > Who will be able to make the review for the suggested patch? I
>> would
>> > >> like
>> > >> > to freeze the branch and start preparing the release.
>> > >> >
>> > >> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
>> > >> >
>> > >> > > Igniters,
>> > >> > >
>> > >> > >
>> > >> > > I’d like to stage for 2.6 release also this issue [1].
>> Corresponding
>> > >> PR
>> > >> > > [2] is ready for review and merge.
>> > >> > > This is not related to code additional configuration file for
>> > enabling
>> > >> > > support of Windows 10 WSL Environment.
>> > >> > >
>> > >> > >
>> > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
>> > >> > > [2] https://github.com/apache/ignite/pull/4194
>> > >> > >
>> > >> > >
>> > >> > >
>> > >> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
>> akuznetsov@apache.org
>> > >
>> > >> > > wrote:
>> > >> > > >
>> > >> > > > Hi,
>> > >> > > >
>> > >> > > > Fix for IGNITE-8722 (
>> > >> https://issues.apache.org/jira/browse/IGNITE-8722
>> > >> > )
>> > >> > > is
>> > >> > > > ready.
>> > >> > > >
>> > >> > > > Diff
>> > >> > > >
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
>> > >> > > >
>> > >> > > > TC looks good for me.
>> > >> > > >
>> > >> > > >
>> > >> > >
>> > >> >
>> > >>
>> >
>> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
>> > >> > > >
>> > >> > > > I'm ready to merge to master and 2.6 branches.
>> > >> > > > Please approve.
>> > >> > > >
>> > >> > > > --
>> > >> > > > Alexey Kuznetsov
>> > >> > >
>> > >> > >
>> > >> >
>> > >>
>> > >
>> >
>>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Valentin Kulichenko <va...@gmail.com>.
Guys,
I reviewed changes in IGNITE-8740, but I'm not sure the fix is correct. I
left a more detailed comment in the ticket. Hopefully, Mair will be able to
respond shortly and clarify.
-Val
On Fri, Jun 22, 2018 at 10:58 AM Denis Magda <dm...@apache.org> wrote:
> Dmitriy,
>
> No, that's an honor for us to see you in this role ;) Both Andrey Gura,
> Anton Vinogradov are our release-management veterans. Please feel free to
> contact them directly.
>
> Could you take over this ticket review and include it in the release:
> https://issues.apache.org/jira/browse/IGNITE-8740
>
> It's not good that we have spring integration broken in some places in
> several releases. I would treat is as a usability blocker and regression.
>
> --
> Denis
>
>
>
> On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com>
> wrote:
>
> > Hi Alexey,
> >
> > Sure, it will be honor for me.
> >
> > In the same time I relatevely new in this area, so I would highly
> > appreciate any assistance of experienced community members to make this
> > happen.
> >
> > Sincerely,
> >
> > пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <
> alexey.goncharuk@gmail.com
> > >:
> >
> > > Denis,
> > >
> > > Currently, I am not aware of anybody who can immediately review and
> > > sign-off the suggested patch. The original scope of tickets have been
> > > resolved, so I suggest to move on with what we have now.
> > >
> > > I will not be able to continue with the release process until Thursday
> > > next week.
> > >
> > > Dmitriy Pavlov, do you mind taking over and finishing the release?
> > >
> > > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> > >
> > >> Folks,
> > >>
> > >> This release no longer reminds an emergency one :) Are we done with
> the
> > >> scope, who is a release manager?
> > >>
> > >> From my side, I'd like us to review and add the fix for broken Spring
> > >> integration which is a significant regression:
> > >> https://issues.apache.org/jira/browse/IGNITE-8740
> > >>
> > >> --
> > >> Denis
> > >>
> > >> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> > >> alexey.goncharuk@gmail.com>
> > >> wrote:
> > >>
> > >> > Hi Petr,
> > >> >
> > >> > Who will be able to make the review for the suggested patch? I would
> > >> like
> > >> > to freeze the branch and start preparing the release.
> > >> >
> > >> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
> > >> >
> > >> > > Igniters,
> > >> > >
> > >> > >
> > >> > > I’d like to stage for 2.6 release also this issue [1].
> Corresponding
> > >> PR
> > >> > > [2] is ready for review and merge.
> > >> > > This is not related to code additional configuration file for
> > enabling
> > >> > > support of Windows 10 WSL Environment.
> > >> > >
> > >> > >
> > >> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > >> > > [2] https://github.com/apache/ignite/pull/4194
> > >> > >
> > >> > >
> > >> > >
> > >> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <
> akuznetsov@apache.org
> > >
> > >> > > wrote:
> > >> > > >
> > >> > > > Hi,
> > >> > > >
> > >> > > > Fix for IGNITE-8722 (
> > >> https://issues.apache.org/jira/browse/IGNITE-8722
> > >> > )
> > >> > > is
> > >> > > > ready.
> > >> > > >
> > >> > > > Diff
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > >> > > >
> > >> > > > TC looks good for me.
> > >> > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > >> > > >
> > >> > > > I'm ready to merge to master and 2.6 branches.
> > >> > > > Please approve.
> > >> > > >
> > >> > > > --
> > >> > > > Alexey Kuznetsov
> > >> > >
> > >> > >
> > >> >
> > >>
> > >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Denis Magda <dm...@apache.org>.
Dmitriy,
No, that's an honor for us to see you in this role ;) Both Andrey Gura,
Anton Vinogradov are our release-management veterans. Please feel free to
contact them directly.
Could you take over this ticket review and include it in the release:
https://issues.apache.org/jira/browse/IGNITE-8740
It's not good that we have spring integration broken in some places in
several releases. I would treat is as a usability blocker and regression.
--
Denis
On Fri, Jun 22, 2018 at 3:06 AM Dmitry Pavlov <dp...@gmail.com> wrote:
> Hi Alexey,
>
> Sure, it will be honor for me.
>
> In the same time I relatevely new in this area, so I would highly
> appreciate any assistance of experienced community members to make this
> happen.
>
> Sincerely,
>
> пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <alexey.goncharuk@gmail.com
> >:
>
> > Denis,
> >
> > Currently, I am not aware of anybody who can immediately review and
> > sign-off the suggested patch. The original scope of tickets have been
> > resolved, so I suggest to move on with what we have now.
> >
> > I will not be able to continue with the release process until Thursday
> > next week.
> >
> > Dmitriy Pavlov, do you mind taking over and finishing the release?
> >
> > чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> >
> >> Folks,
> >>
> >> This release no longer reminds an emergency one :) Are we done with the
> >> scope, who is a release manager?
> >>
> >> From my side, I'd like us to review and add the fix for broken Spring
> >> integration which is a significant regression:
> >> https://issues.apache.org/jira/browse/IGNITE-8740
> >>
> >> --
> >> Denis
> >>
> >> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> >> alexey.goncharuk@gmail.com>
> >> wrote:
> >>
> >> > Hi Petr,
> >> >
> >> > Who will be able to make the review for the suggested patch? I would
> >> like
> >> > to freeze the branch and start preparing the release.
> >> >
> >> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
> >> >
> >> > > Igniters,
> >> > >
> >> > >
> >> > > I’d like to stage for 2.6 release also this issue [1]. Corresponding
> >> PR
> >> > > [2] is ready for review and merge.
> >> > > This is not related to code additional configuration file for
> enabling
> >> > > support of Windows 10 WSL Environment.
> >> > >
> >> > >
> >> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> >> > > [2] https://github.com/apache/ignite/pull/4194
> >> > >
> >> > >
> >> > >
> >> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <akuznetsov@apache.org
> >
> >> > > wrote:
> >> > > >
> >> > > > Hi,
> >> > > >
> >> > > > Fix for IGNITE-8722 (
> >> https://issues.apache.org/jira/browse/IGNITE-8722
> >> > )
> >> > > is
> >> > > > ready.
> >> > > >
> >> > > > Diff
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> >> > > >
> >> > > > TC looks good for me.
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> >> > > >
> >> > > > I'm ready to merge to master and 2.6 branches.
> >> > > > Please approve.
> >> > > >
> >> > > > --
> >> > > > Alexey Kuznetsov
> >> > >
> >> > >
> >> >
> >>
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Dmitry Pavlov <dp...@gmail.com>.
Hi Alexey,
Sure, it will be honor for me.
In the same time I relatevely new in this area, so I would highly
appreciate any assistance of experienced community members to make this
happen.
Sincerely,
пт, 22 июн. 2018 г. в 12:18, Alexey Goncharuk <al...@gmail.com>:
> Denis,
>
> Currently, I am not aware of anybody who can immediately review and
> sign-off the suggested patch. The original scope of tickets have been
> resolved, so I suggest to move on with what we have now.
>
> I will not be able to continue with the release process until Thursday
> next week.
>
> Dmitriy Pavlov, do you mind taking over and finishing the release?
>
> чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
>
>> Folks,
>>
>> This release no longer reminds an emergency one :) Are we done with the
>> scope, who is a release manager?
>>
>> From my side, I'd like us to review and add the fix for broken Spring
>> integration which is a significant regression:
>> https://issues.apache.org/jira/browse/IGNITE-8740
>>
>> --
>> Denis
>>
>> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
>> alexey.goncharuk@gmail.com>
>> wrote:
>>
>> > Hi Petr,
>> >
>> > Who will be able to make the review for the suggested patch? I would
>> like
>> > to freeze the branch and start preparing the release.
>> >
>> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
>> >
>> > > Igniters,
>> > >
>> > >
>> > > I’d like to stage for 2.6 release also this issue [1]. Corresponding
>> PR
>> > > [2] is ready for review and merge.
>> > > This is not related to code additional configuration file for enabling
>> > > support of Windows 10 WSL Environment.
>> > >
>> > >
>> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
>> > > [2] https://github.com/apache/ignite/pull/4194
>> > >
>> > >
>> > >
>> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <ak...@apache.org>
>> > > wrote:
>> > > >
>> > > > Hi,
>> > > >
>> > > > Fix for IGNITE-8722 (
>> https://issues.apache.org/jira/browse/IGNITE-8722
>> > )
>> > > is
>> > > > ready.
>> > > >
>> > > > Diff
>> > > >
>> > > >
>> > >
>> >
>> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
>> > > >
>> > > > TC looks good for me.
>> > > >
>> > > >
>> > >
>> >
>> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
>> > > >
>> > > > I'm ready to merge to master and 2.6 branches.
>> > > > Please approve.
>> > > >
>> > > > --
>> > > > Alexey Kuznetsov
>> > >
>> > >
>> >
>>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Alexey Goncharuk <al...@gmail.com>.
Denis,
Currently, I am not aware of anybody who can immediately review and
sign-off the suggested patch. The original scope of tickets have been
resolved, so I suggest to move on with what we have now.
I will not be able to continue with the release process until Thursday next
week.
Dmitriy Pavlov, do you mind taking over and finishing the release?
чт, 21 июн. 2018 г. в 23:02, Denis Magda <dm...@apache.org>:
> Folks,
>
> This release no longer reminds an emergency one :) Are we done with the
> scope, who is a release manager?
>
> From my side, I'd like us to review and add the fix for broken Spring
> integration which is a significant regression:
> https://issues.apache.org/jira/browse/IGNITE-8740
>
> --
> Denis
>
> On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <
> alexey.goncharuk@gmail.com>
> wrote:
>
> > Hi Petr,
> >
> > Who will be able to make the review for the suggested patch? I would like
> > to freeze the branch and start preparing the release.
> >
> > пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
> >
> > > Igniters,
> > >
> > >
> > > I’d like to stage for 2.6 release also this issue [1]. Corresponding PR
> > > [2] is ready for review and merge.
> > > This is not related to code additional configuration file for enabling
> > > support of Windows 10 WSL Environment.
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > > [2] https://github.com/apache/ignite/pull/4194
> > >
> > >
> > >
> > > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <ak...@apache.org>
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > Fix for IGNITE-8722 (
> https://issues.apache.org/jira/browse/IGNITE-8722
> > )
> > > is
> > > > ready.
> > > >
> > > > Diff
> > > >
> > > >
> > >
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > > >
> > > > TC looks good for me.
> > > >
> > > >
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > > >
> > > > I'm ready to merge to master and 2.6 branches.
> > > > Please approve.
> > > >
> > > > --
> > > > Alexey Kuznetsov
> > >
> > >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Denis Magda <dm...@apache.org>.
Folks,
This release no longer reminds an emergency one :) Are we done with the
scope, who is a release manager?
From my side, I'd like us to review and add the fix for broken Spring
integration which is a significant regression:
https://issues.apache.org/jira/browse/IGNITE-8740
--
Denis
On Mon, Jun 18, 2018 at 5:16 AM Alexey Goncharuk <al...@gmail.com>
wrote:
> Hi Petr,
>
> Who will be able to make the review for the suggested patch? I would like
> to freeze the branch and start preparing the release.
>
> пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
>
> > Igniters,
> >
> >
> > I’d like to stage for 2.6 release also this issue [1]. Corresponding PR
> > [2] is ready for review and merge.
> > This is not related to code additional configuration file for enabling
> > support of Windows 10 WSL Environment.
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-8804
> > [2] https://github.com/apache/ignite/pull/4194
> >
> >
> >
> > > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <ak...@apache.org>
> > wrote:
> > >
> > > Hi,
> > >
> > > Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722
> )
> > is
> > > ready.
> > >
> > > Diff
> > >
> > >
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> > >
> > > TC looks good for me.
> > >
> > >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> > >
> > > I'm ready to merge to master and 2.6 branches.
> > > Please approve.
> > >
> > > --
> > > Alexey Kuznetsov
> >
> >
>
Re: Ignite 2.6 emergency release suggestion
Posted by Alexey Goncharuk <al...@gmail.com>.
Hi Petr,
Who will be able to make the review for the suggested patch? I would like
to freeze the branch and start preparing the release.
пт, 15 июн. 2018 г. в 11:45, Petr Ivanov <mr...@gmail.com>:
> Igniters,
>
>
> I’d like to stage for 2.6 release also this issue [1]. Corresponding PR
> [2] is ready for review and merge.
> This is not related to code additional configuration file for enabling
> support of Windows 10 WSL Environment.
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-8804
> [2] https://github.com/apache/ignite/pull/4194
>
>
>
> > On 14 Jun 2018, at 06:59, Alexey Kuznetsov <ak...@apache.org>
> wrote:
> >
> > Hi,
> >
> > Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722)
> is
> > ready.
> >
> > Diff
> >
> >
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
> >
> > TC looks good for me.
> >
> >
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
> >
> > I'm ready to merge to master and 2.6 branches.
> > Please approve.
> >
> > --
> > Alexey Kuznetsov
>
>
Re: Ignite 2.6 emergency release suggestion
Posted by Petr Ivanov <mr...@gmail.com>.
Igniters,
I’d like to stage for 2.6 release also this issue [1]. Corresponding PR [2] is ready for review and merge.
This is not related to code additional configuration file for enabling support of Windows 10 WSL Environment.
[1] https://issues.apache.org/jira/browse/IGNITE-8804
[2] https://github.com/apache/ignite/pull/4194
> On 14 Jun 2018, at 06:59, Alexey Kuznetsov <ak...@apache.org> wrote:
>
> Hi,
>
> Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722) is
> ready.
>
> Diff
>
> https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
>
> TC looks good for me.
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
>
> I'm ready to merge to master and 2.6 branches.
> Please approve.
>
> --
> Alexey Kuznetsov
Re: Ignite 2.6 emergency release suggestion
Posted by Alexey Kuznetsov <ak...@apache.org>.
Hi,
Fix for IGNITE-8722 (https://issues.apache.org/jira/browse/IGNITE-8722) is
ready.
Diff
https://git1-us-west.apache.org/repos/asf?p=ignite.git&a=search&h=refs%2Fheads%2Fignite-8722&st=commit&s=IGNITE-8722
TC looks good for me.
https://ci.ignite.apache.org/viewLog.html?buildId=1385195&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient
I'm ready to merge to master and 2.6 branches.
Please approve.
--
Alexey Kuznetsov
Re: Ignite 2.6 emergency release suggestion
Posted by Pavel Kovalenko <jo...@gmail.com>.
Igniters,
Recently we noticed the issue when we don't completely persist some data on
the disk:
https://issues.apache.org/jira/browse/IGNITE-8780 . In some cases it can
lead node to unrecoverable state.
I think this problem should be included to release.
ср, 13 июн. 2018 г. в 14:06, Alexey Kuznetsov <ak...@apache.org>:
> Hi!
>
> Lets also include fix for
> https://issues.apache.org/jira/browse/IGNITE-8722
> in this release.
> This bug was introduced in IGNITE-7803 (Ignite 2.5) for data structures
> that has references to self-type.
>
> The fix is simple (remove one "else" key word in
> IGNITE_BINARY_OBJECT_SERIALIZER) + add test.
> I will do this today.
>
> Please approve.
>
>
> On Wed, Jun 13, 2018 at 2:36 PM, Nikolay Izhikov <ni...@apache.org>
> wrote:
>
> > Hello, guys.
> >
> > I try my best to do review in a next few days.
> >
> > В Вт, 12/06/2018 в 11:28 -0700, Denis Magda пишет:
> > > Agree with Ray. The ticket has been already reviewed and requires us to
> > run tests for an isolated module - Spark.
> > >
> > > Dmitriy Pavlov, Nickolay Izhikov, could you step in as final reviewers
> > and merge the changes?
> > >
> > > --
> > > Denis
> > >
> > > On Tue, Jun 12, 2018 at 12:01 AM Ray <ra...@cisco.com> wrote:
> > > > Igniters,
> > > >
> > > > Can you squeeze this ticket into 2.6 scope?
> > > > https://issues.apache.org/jira/browse/IGNITE-8534
> > > >
> > > > As ignite-spark module is relatively independent module, and there're
> > > > already two users in the user list trying to use spark 2.3 with
> Ignite
> > last
> > > > week only.
> > > >
> > > > http://apache-ignite-users.70518.x6.nabble.com/Spark-
> > Ignite-connection-using-Config-file-td21827.html
> > > >
> > > > http://apache-ignite-users.70518.x6.nabble.com/Spark-
> > Ignite-standalone-mode-on-Kubernetes-cluster-td21739.html
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
> >
>
>
>
> --
> Alexey Kuznetsov
>
Re: Ignite 2.6 emergency release suggestion
Posted by Alexey Kuznetsov <ak...@apache.org>.
Hi!
Lets also include fix for https://issues.apache.org/jira/browse/IGNITE-8722
in this release.
This bug was introduced in IGNITE-7803 (Ignite 2.5) for data structures
that has references to self-type.
The fix is simple (remove one "else" key word in
IGNITE_BINARY_OBJECT_SERIALIZER) + add test.
I will do this today.
Please approve.
On Wed, Jun 13, 2018 at 2:36 PM, Nikolay Izhikov <ni...@apache.org>
wrote:
> Hello, guys.
>
> I try my best to do review in a next few days.
>
> В Вт, 12/06/2018 в 11:28 -0700, Denis Magda пишет:
> > Agree with Ray. The ticket has been already reviewed and requires us to
> run tests for an isolated module - Spark.
> >
> > Dmitriy Pavlov, Nickolay Izhikov, could you step in as final reviewers
> and merge the changes?
> >
> > --
> > Denis
> >
> > On Tue, Jun 12, 2018 at 12:01 AM Ray <ra...@cisco.com> wrote:
> > > Igniters,
> > >
> > > Can you squeeze this ticket into 2.6 scope?
> > > https://issues.apache.org/jira/browse/IGNITE-8534
> > >
> > > As ignite-spark module is relatively independent module, and there're
> > > already two users in the user list trying to use spark 2.3 with Ignite
> last
> > > week only.
> > >
> > > http://apache-ignite-users.70518.x6.nabble.com/Spark-
> Ignite-connection-using-Config-file-td21827.html
> > >
> > > http://apache-ignite-users.70518.x6.nabble.com/Spark-
> Ignite-standalone-mode-on-Kubernetes-cluster-td21739.html
> > >
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
--
Alexey Kuznetsov
Re: Ignite 2.6 emergency release suggestion
Posted by Nikolay Izhikov <ni...@apache.org>.
Hello, guys.
I try my best to do review in a next few days.
В Вт, 12/06/2018 в 11:28 -0700, Denis Magda пишет:
> Agree with Ray. The ticket has been already reviewed and requires us to run tests for an isolated module - Spark.
>
> Dmitriy Pavlov, Nickolay Izhikov, could you step in as final reviewers and merge the changes?
>
> --
> Denis
>
> On Tue, Jun 12, 2018 at 12:01 AM Ray <ra...@cisco.com> wrote:
> > Igniters,
> >
> > Can you squeeze this ticket into 2.6 scope?
> > https://issues.apache.org/jira/browse/IGNITE-8534
> >
> > As ignite-spark module is relatively independent module, and there're
> > already two users in the user list trying to use spark 2.3 with Ignite last
> > week only.
> >
> > http://apache-ignite-users.70518.x6.nabble.com/Spark-Ignite-connection-using-Config-file-td21827.html
> >
> > http://apache-ignite-users.70518.x6.nabble.com/Spark-Ignite-standalone-mode-on-Kubernetes-cluster-td21739.html
> >
> >
> >
> >
> >
> > --
> > Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
Re: Ignite 2.6 emergency release suggestion
Posted by Denis Magda <dm...@apache.org>.
Agree with Ray. The ticket has been already reviewed and requires us to run
tests for an isolated module - Spark.
Dmitriy Pavlov, Nickolay Izhikov, could you step in as final reviewers and
merge the changes?
--
Denis
On Tue, Jun 12, 2018 at 12:01 AM Ray <ra...@cisco.com> wrote:
> Igniters,
>
> Can you squeeze this ticket into 2.6 scope?
> https://issues.apache.org/jira/browse/IGNITE-8534
>
> As ignite-spark module is relatively independent module, and there're
> already two users in the user list trying to use spark 2.3 with Ignite last
> week only.
>
>
> http://apache-ignite-users.70518.x6.nabble.com/Spark-Ignite-connection-using-Config-file-td21827.html
>
>
> http://apache-ignite-users.70518.x6.nabble.com/Spark-Ignite-standalone-mode-on-Kubernetes-cluster-td21739.html
>
>
>
>
>
> --
> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>
Re: Ignite 2.6 emergency release suggestion
Posted by Ray <ra...@cisco.com>.
Igniters,
Can you squeeze this ticket into 2.6 scope?
https://issues.apache.org/jira/browse/IGNITE-8534
As ignite-spark module is relatively independent module, and there're
already two users in the user list trying to use spark 2.3 with Ignite last
week only.
http://apache-ignite-users.70518.x6.nabble.com/Spark-Ignite-connection-using-Config-file-td21827.html
http://apache-ignite-users.70518.x6.nabble.com/Spark-Ignite-standalone-mode-on-Kubernetes-cluster-td21739.html
--
Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/