Ignite 2.6 emergency release suggestion

[agura]

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 <[hidden email]> 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 <[hidden email]>:
>
> > 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]>:
> > >>
> > >>> 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 <[hidden email]>
> > 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 <[hidden email]>
> > >>> 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 <[hidden email]
> > >:
> > >>>>>>>
> > >>>>>>>> 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 <[hidden email]>:
> > >>>>>>>>>
> > >>>>>>>>>> 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) <
> > >>>>>>>> [hidden email]>
> > >>>>>>>>>> wrote:
> > >>>>>>>>>>
> > >>>>>>>>>>> Yes, it will be in the release 2.6
> > >>>>>>>>>>>
> > >>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
> > [hidden email]>
> > >>>>>>>>>>> написал(а):
> > >>>>>>>>>>>> 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 <[hidden email]>:
> > >>>>
> > >>>
> >
> >

[Anton Vinogradov-2]

Thank you!

пн, 9 июл. 2018 г. в 18:57, Andrey Gura <[hidden email]>:

> 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 <[hidden email]> 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 <[hidden email]>:
> >
> > > 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 <[hidden email]> 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 <[hidden email]>
> 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 <[hidden email]>:
> > > >>
> > > >>> 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 <[hidden email]>
> > > 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 <[hidden email]
> >
> > > >>> 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 <
> [hidden email]
> > > >:
> > > >>>>>>>
> > > >>>>>>>> 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 <[hidden email]
> >:
> > > >>>>>>>>>
> > > >>>>>>>>>> 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) <
> > > >>>>>>>> [hidden email]>
> > > >>>>>>>>>> wrote:
> > > >>>>>>>>>>
> > > >>>>>>>>>>> Yes, it will be in the release 2.6
> > > >>>>>>>>>>>
> > > >>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
> > > [hidden email]>
> > > >>>>>>>>>>> написал(а):
> > > >>>>>>>>>>>> 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 <
> [hidden email]>:
> > > >>>>
> > > >>>
> > >
> > >
>

[vveider]

Awesome!
Thanks, Andrey!

> On 9 Jul 2018, at 18:57, Andrey Gura <[hidden email]> 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 <[hidden email]> 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 <[hidden email]>:
>>
>>> 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 <[hidden email]> 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 <[hidden email]> 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 <[hidden email]>:
>>>>>
>>>>>> 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 <[hidden email]>
>>> 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 <[hidden email]>
>>>>>> 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 <[hidden email]
>>>> :
>>>>>>>>>>
>>>>>>>>>>> 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 <[hidden email]>:
>>>>>>>>>>>>
>>>>>>>>>>>>> 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) <
>>>>>>>>>>> [hidden email]>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Yes, it will be in the release 2.6
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> 27 июня 2018 г., в 14:15, Dmitry Pavlov <
>>> [hidden email]>
>>>>>>>>>>>>>> написал(а):
>>>>>>>>>>>>>>> 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 <[hidden email]>:
>>>>>>>
>>>>>>
>>>
>>>