Ignite 2.6 emergency release suggestion

classic Classic list List threaded Threaded
43 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

dmagda
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 <
[hidden email]> 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 <
> [hidden email]> 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 <[hidden email]> 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 <[hidden email]>
> >> 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 <
> >> [hidden email]
> >> > >:
> >> >
> >> > > 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 <[hidden email]>:
> >> > >
> >> > >> 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 <
> >> > >> [hidden email]>
> >> > >> 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 <[hidden email]>:
> >> > >> >
> >> > >> > > 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 <
> >> [hidden email]
> >> > >
> >> > >> > > 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
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >>
> >> > >
> >> >
> >>
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Dmitriy 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 <[hidden email]>:

> 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 <
> [hidden email]> 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 <
> > [hidden email]> 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 <[hidden email]>
> 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 <[hidden email]>
> > >> 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 <
> > >> [hidden email]
> > >> > >:
> > >> >
> > >> > > 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 <[hidden email]>:
> > >> > >
> > >> > >> 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 <
> > >> > >> [hidden email]>
> > >> > >> 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 <[hidden email]
> >:
> > >> > >> >
> > >> > >> > > 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 <
> > >> [hidden email]
> > >> > >
> > >> > >> > > 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
> > >> > >> > >
> > >> > >> > >
> > >> > >> >
> > >> > >>
> > >> > >
> > >> >
> > >>
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Nikolay Izhikov-2
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 <[hidden email]>:
>
> > 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 <
> > [hidden email]> 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 <
> > > [hidden email]> 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 <[hidden email]>
> >
> > 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 <[hidden email]>
> > > > > 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 <
> > > > >
> > > > > [hidden email]
> > > > > > > :
> > > > > > > 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 <[hidden email]>:
> > > > > > >
> > > > > > > > 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 <
> > > > > > > > [hidden email]>
> > > > > > > > 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 <[hidden email]
> > >
> > > :
> > > > > > > > >
> > > > > > > > > > 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 <
> > > > >
> > > > > [hidden email]
> > > > > > >
> > > > > > > > > > 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
> > > > > > > > > >
> > > > > > > > > >

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Nikolay Izhikov-2
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 <[hidden email]>:
> >
> > > 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 <
> > > [hidden email]> 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 <
> > > > [hidden email]> 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 <[hidden email]>
> > >
> > > 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 <[hidden email]>
> > > > > > 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 <
> > > > > >
> > > > > > [hidden email]
> > > > > > > > :
> > > > > > > > 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 <[hidden email]>:
> > > > > > > >
> > > > > > > > > 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 <
> > > > > > > > > [hidden email]>
> > > > > > > > > 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 <[hidden email]
> > > >
> > > > :
> > > > > > > > > >
> > > > > > > > > > > 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 <
> > > > > >
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > > > > > 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

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Dmitriy Pavlov
In reply to this post by Nikolay Izhikov-2
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 <[hidden email]>:

> 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 <[hidden email]>:
> >
> > > 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 <
> > > [hidden email]> 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 <
> > > > [hidden email]> 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 <[hidden email]>
> > >
> > > 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 <
> [hidden email]>
> > > > > > 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 <
> > > > > >
> > > > > > [hidden email]
> > > > > > > > :
> > > > > > > > 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 <[hidden email]
> >:
> > > > > > > >
> > > > > > > > > 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 <
> > > > > > > > > [hidden email]>
> > > > > > > > > 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 <
> [hidden email]
> > > >
> > > > :
> > > > > > > > > >
> > > > > > > > > > > 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 <
> > > > > >
> > > > > > [hidden email]
> > > > > > > >
> > > > > > > > > > > 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
> > > > > > > > > > >
> > > > > > > > > > >
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

dmagda
+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 <[hidden email]>
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 <[hidden email]>:
>
> > 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 <[hidden email]>:
> > >
> > > > 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 <
> > > > [hidden email]> 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 <
> > > > > [hidden email]> 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 <[hidden email]>
> > > >
> > > > 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 <
> > [hidden email]>
> > > > > > > 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 <
> > > > > > >
> > > > > > > [hidden email]
> > > > > > > > > :
> > > > > > > > > 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 <
> [hidden email]
> > >:
> > > > > > > > >
> > > > > > > > > > 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 <
> > > > > > > > > > [hidden email]>
> > > > > > > > > > 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 <
> > [hidden email]
> > > > >
> > > > > :
> > > > > > > > > > >
> > > > > > > > > > > > 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 <
> > > > > > >
> > > > > > > [hidden email]
> > > > > > > > >
> > > > > > > > > > > > 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
> > > > > > > > > > > >
> > > > > > > > > > > >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Dmitriy Pavlov
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]>:

> +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 <[hidden email]>
> 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 <[hidden email]>:
> >
> > > 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 <[hidden email]>:
> > > >
> > > > > 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 <
> > > > > [hidden email]> 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 <
> > > > > > [hidden email]> 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 <
> [hidden email]>
> > > > >
> > > > > 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 <
> > > [hidden email]>
> > > > > > > > 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 <
> > > > > > > >
> > > > > > > > [hidden email]
> > > > > > > > > > :
> > > > > > > > > > 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 <
> > [hidden email]
> > > >:
> > > > > > > > > >
> > > > > > > > > > > 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 <
> > > > > > > > > > > [hidden email]>
> > > > > > > > > > > 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 <
> > > [hidden email]
> > > > > >
> > > > > > :
> > > > > > > > > > > >
> > > > > > > > > > > > > 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 <
> > > > > > > >
> > > > > > > > [hidden email]
> > > > > > > > > >
> > > > > > > > > > > > > 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
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Spider (Alexey)
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]>:

Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

dmagda
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]>:
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Dmitriy 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]>:
> >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Nikolay Izhikov-2
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]>:
> > >
> > >

signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Dmitriy Pavlov
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]>:
> > > >
> > > >
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Ivan Rakov
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]>:
>>>>>

Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

agura
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]>:
> >>>>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Ivan Rakov
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]>:

Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

agura
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]>:
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Anton Vinogradov-2
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]>:
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

agura
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]>:
> > >
> >
Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

vveider
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]>:
>>>>
>>>

Reply | Threaded
Open this post in threaded view
|

Re: Ignite 2.6 emergency release suggestion

Anton Vinogradov-2
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]>:
> >>>>
> >>>
>
>
123