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

[Dmitriy Pavlov]

Hi Alexey,
dist SVN repo usually contains only latest version, older versions go to
the archive.

Release 2.7.5 can be moved to the archive (with corresponding site update).
And a folder for 2.7.0 is empty, it definitely can be deleted.

Sincerely,
Dmitriy Pavlov

чт, 19 сент. 2019 г. в 21:24, Denis Magda :

> Dmitry,
>
> Everyone who is added to the readme.io gets admin rights. The owner is one
> of our PMC Members Dmitry Setrakyan. We can start a discussion and transfer
> the ownership rights to some generic account known by PMC group only.
>
> -
> Denis
>
>
> On Thu, Sep 19, 2019 at 3:40 AM Dmitriy Pavlov  wrote:
>
> > Artem, thank you for doing that. But the same issue came up during 2.7.5.
> >
> > IMO PMC should have admin access to all these projects.
> >
> > Who can grant these permissions?
> >
> > Sincerely
> > Dmitriy Pavlov
> >
> > чт, 19 сент. 2019 г. в 09:44, Artem Budnikov <
> a.budnikov.ign...@gmail.com
> > >:
> >
> > > Hi,
> > >
> > > I've created new versions for other projects on readme.io
> > >
> > > -Artem
> > >
> > > On 18.09.2019 19:17, Alexey Goncharuk wrote:
> > > > Igniters,
> > > >
> > > > I am following the release process procedure [1] and currently on
> docs
> > > > update step. I can login to the admin panel, but I can only see the
> > main
> > > > Ignite docs project. Who can add me to the remaining projects
> (C#/.NET,
> > > > C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone
> the
> > > docs
> > > > for 2.7.6?
> > > >
> > > > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > >
> > > > ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk <
> > > alexey.goncha...@gmail.com>:
> > > >
> > > >> Ivan, thank you!
> > > >>
> > > >> Will update release notes and start the build shortly.
> > > >>
> > > >> ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
> > > >>
> > > >>> Alexey,
> > > >>>
> > > >>> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to
> > > master
> > > >>> and 2.7.6.
> > > >>>
> > > >>> Best Regards,
> > > >>> Ivan Rakov
> > > >>>
> > > >>> On 11.09.2019 18:13, Alexey Goncharuk wrote:
> > > >>>> Good,
> > > >>>>
> > > >>>> Please let me know when this is done, I will re-upload the release
> > > >>>> artifacts.
> > > >>>>
> > > >>>> ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin  >:
> > > >>>>
> > > >>>>> Alexey,
> > > >>>>>
> > > >>>>> The changes already have been tested, so no TC problems expected.
> > > >>>>> If this is true, then we need just a few hours to merge them.
> > > >>>>>
> > > >>>>> From: Alexey Goncharuk
> > > >>>>> Sent: Wednesday, September 11, 2019 6:03 PM
> > > >>>>> To: dev
> > > >>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> > > >>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> > > >>> manager)
> > > >>>>> Alexandr,
> > > >>>>>
> > > >>>>> I almost sent the vote email :) When do you expect the fix to be
> in
> > > >>> master
> > > >>>>> and 2.7.6?
> > > >>>>>
> > > >>>>> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin <
> lexw...@gmail.com
> > >:
> > > >>>>>
> > > >>>>>> Folks,
> > > >>>>>>
> > > >>>>>> A critical bug was detected in .NET [1].
> > > >>>>>>
> > > >>>>>> I understand that it’s a little bit late, but I propose to
> include
> > > >>> this
> > > >>>>>> issue into the release scope.
> > > >>>>>>
> > > >>>>>> PR is ready, currently waiting for a TC visa.
> > > >>>>>>
> > > >>>>>> Thoughts?
> > > >>>>>>
> > > >>>>&g

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

[Denis Magda]

Dmitry,

Everyone who is added to the readme.io gets admin rights. The owner is one
of our PMC Members Dmitry Setrakyan. We can start a discussion and transfer
the ownership rights to some generic account known by PMC group only.

-
Denis


On Thu, Sep 19, 2019 at 3:40 AM Dmitriy Pavlov  wrote:

> Artem, thank you for doing that. But the same issue came up during 2.7.5.
>
> IMO PMC should have admin access to all these projects.
>
> Who can grant these permissions?
>
> Sincerely
> Dmitriy Pavlov
>
> чт, 19 сент. 2019 г. в 09:44, Artem Budnikov  >:
>
> > Hi,
> >
> > I've created new versions for other projects on readme.io
> >
> > -Artem
> >
> > On 18.09.2019 19:17, Alexey Goncharuk wrote:
> > > Igniters,
> > >
> > > I am following the release process procedure [1] and currently on docs
> > > update step. I can login to the admin panel, but I can only see the
> main
> > > Ignite docs project. Who can add me to the remaining projects (C#/.NET,
> > > C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone the
> > docs
> > > for 2.7.6?
> > >
> > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >
> > > ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk <
> > alexey.goncha...@gmail.com>:
> > >
> > >> Ivan, thank you!
> > >>
> > >> Will update release notes and start the build shortly.
> > >>
> > >> ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
> > >>
> > >>> Alexey,
> > >>>
> > >>> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to
> > master
> > >>> and 2.7.6.
> > >>>
> > >>> Best Regards,
> > >>> Ivan Rakov
> > >>>
> > >>> On 11.09.2019 18:13, Alexey Goncharuk wrote:
> > >>>> Good,
> > >>>>
> > >>>> Please let me know when this is done, I will re-upload the release
> > >>>> artifacts.
> > >>>>
> > >>>> ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :
> > >>>>
> > >>>>> Alexey,
> > >>>>>
> > >>>>> The changes already have been tested, so no TC problems expected.
> > >>>>> If this is true, then we need just a few hours to merge them.
> > >>>>>
> > >>>>> From: Alexey Goncharuk
> > >>>>> Sent: Wednesday, September 11, 2019 6:03 PM
> > >>>>> To: dev
> > >>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> > >>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> > >>> manager)
> > >>>>> Alexandr,
> > >>>>>
> > >>>>> I almost sent the vote email :) When do you expect the fix to be in
> > >>> master
> > >>>>> and 2.7.6?
> > >>>>>
> > >>>>> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin  >:
> > >>>>>
> > >>>>>> Folks,
> > >>>>>>
> > >>>>>> A critical bug was detected in .NET [1].
> > >>>>>>
> > >>>>>> I understand that it’s a little bit late, but I propose to include
> > >>> this
> > >>>>>> issue into the release scope.
> > >>>>>>
> > >>>>>> PR is ready, currently waiting for a TC visa.
> > >>>>>>
> > >>>>>> Thoughts?
> > >>>>>>
> > >>>>>> [1] - https://issues.apache.org/jira/browse/IGNITE-12163
> > >>>>>>
> > >>>>>>
> > >>>>>> From: Alexey Goncharuk
> > >>>>>> Sent: Monday, September 9, 2019 5:11 PM
> > >>>>>> To: dev
> > >>>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> > >>>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> > >>>>> manager)
> > >>>>>> Igniters,
> > >>>>>>
> > >>>>>> I just pushed the last ticket to ignite-2.7.6 branch; looks like
> we
> > >>> are
> > >>>>>> ready for the next iteration.
> > >>>>>>
> > >>>>>> Given that Dmitriy Pavlov will be unavailable ti

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

[Alexey Goncharuk]

Folks,

I am following the step 6.3.12 of the release process [1] and see that the
release 2.7.0 is still present in the dist folder. Do I understand
correctly that I can remove both 2.7.0 and 2.7.5 at this point and 2.7.0
should have been removed during 2.7.5 release?

If not, the doc should be updated accordingly.

[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process

--AG

чт, 19 сент. 2019 г. в 13:40, Dmitriy Pavlov :

> Artem, thank you for doing that. But the same issue came up during 2.7.5.
>
> IMO PMC should have admin access to all these projects.
>
> Who can grant these permissions?
>
> Sincerely
> Dmitriy Pavlov
>
> чт, 19 сент. 2019 г. в 09:44, Artem Budnikov  >:
>
> > Hi,
> >
> > I've created new versions for other projects on readme.io
> >
> > -Artem
> >
> > On 18.09.2019 19:17, Alexey Goncharuk wrote:
> > > Igniters,
> > >
> > > I am following the release process procedure [1] and currently on docs
> > > update step. I can login to the admin panel, but I can only see the
> main
> > > Ignite docs project. Who can add me to the remaining projects (C#/.NET,
> > > C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone the
> > docs
> > > for 2.7.6?
> > >
> > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >
> > > ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk <
> > alexey.goncha...@gmail.com>:
> > >
> > >> Ivan, thank you!
> > >>
> > >> Will update release notes and start the build shortly.
> > >>
> > >> ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
> > >>
> > >>> Alexey,
> > >>>
> > >>> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to
> > master
> > >>> and 2.7.6.
> > >>>
> > >>> Best Regards,
> > >>> Ivan Rakov
> > >>>
> > >>> On 11.09.2019 18:13, Alexey Goncharuk wrote:
> > >>>> Good,
> > >>>>
> > >>>> Please let me know when this is done, I will re-upload the release
> > >>>> artifacts.
> > >>>>
> > >>>> ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :
> > >>>>
> > >>>>> Alexey,
> > >>>>>
> > >>>>> The changes already have been tested, so no TC problems expected.
> > >>>>> If this is true, then we need just a few hours to merge them.
> > >>>>>
> > >>>>> From: Alexey Goncharuk
> > >>>>> Sent: Wednesday, September 11, 2019 6:03 PM
> > >>>>> To: dev
> > >>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> > >>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> > >>> manager)
> > >>>>> Alexandr,
> > >>>>>
> > >>>>> I almost sent the vote email :) When do you expect the fix to be in
> > >>> master
> > >>>>> and 2.7.6?
> > >>>>>
> > >>>>> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin  >:
> > >>>>>
> > >>>>>> Folks,
> > >>>>>>
> > >>>>>> A critical bug was detected in .NET [1].
> > >>>>>>
> > >>>>>> I understand that it’s a little bit late, but I propose to include
> > >>> this
> > >>>>>> issue into the release scope.
> > >>>>>>
> > >>>>>> PR is ready, currently waiting for a TC visa.
> > >>>>>>
> > >>>>>> Thoughts?
> > >>>>>>
> > >>>>>> [1] - https://issues.apache.org/jira/browse/IGNITE-12163
> > >>>>>>
> > >>>>>>
> > >>>>>> From: Alexey Goncharuk
> > >>>>>> Sent: Monday, September 9, 2019 5:11 PM
> > >>>>>> To: dev
> > >>>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> > >>>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> > >>>>> manager)
> > >>>>>> Igniters,
> > >>>>>>
> > >>>>>> I just pushed the last ticket to ignite-2.7.6 branch; looks like
> we
> > >>> are
>

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

[Dmitriy Pavlov]

Artem, thank you for doing that. But the same issue came up during 2.7.5.

IMO PMC should have admin access to all these projects.

Who can grant these permissions?

Sincerely
Dmitriy Pavlov

чт, 19 сент. 2019 г. в 09:44, Artem Budnikov :

> Hi,
>
> I've created new versions for other projects on readme.io
>
> -Artem
>
> On 18.09.2019 19:17, Alexey Goncharuk wrote:
> > Igniters,
> >
> > I am following the release process procedure [1] and currently on docs
> > update step. I can login to the admin panel, but I can only see the main
> > Ignite docs project. Who can add me to the remaining projects (C#/.NET,
> > C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone the
> docs
> > for 2.7.6?
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >
> > ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk <
> alexey.goncha...@gmail.com>:
> >
> >> Ivan, thank you!
> >>
> >> Will update release notes and start the build shortly.
> >>
> >> ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
> >>
> >>> Alexey,
> >>>
> >>> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to
> master
> >>> and 2.7.6.
> >>>
> >>> Best Regards,
> >>> Ivan Rakov
> >>>
> >>> On 11.09.2019 18:13, Alexey Goncharuk wrote:
> >>>> Good,
> >>>>
> >>>> Please let me know when this is done, I will re-upload the release
> >>>> artifacts.
> >>>>
> >>>> ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :
> >>>>
> >>>>> Alexey,
> >>>>>
> >>>>> The changes already have been tested, so no TC problems expected.
> >>>>> If this is true, then we need just a few hours to merge them.
> >>>>>
> >>>>> From: Alexey Goncharuk
> >>>>> Sent: Wednesday, September 11, 2019 6:03 PM
> >>>>> To: dev
> >>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> >>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> >>> manager)
> >>>>> Alexandr,
> >>>>>
> >>>>> I almost sent the vote email :) When do you expect the fix to be in
> >>> master
> >>>>> and 2.7.6?
> >>>>>
> >>>>> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin :
> >>>>>
> >>>>>> Folks,
> >>>>>>
> >>>>>> A critical bug was detected in .NET [1].
> >>>>>>
> >>>>>> I understand that it’s a little bit late, but I propose to include
> >>> this
> >>>>>> issue into the release scope.
> >>>>>>
> >>>>>> PR is ready, currently waiting for a TC visa.
> >>>>>>
> >>>>>> Thoughts?
> >>>>>>
> >>>>>> [1] - https://issues.apache.org/jira/browse/IGNITE-12163
> >>>>>>
> >>>>>>
> >>>>>> From: Alexey Goncharuk
> >>>>>> Sent: Monday, September 9, 2019 5:11 PM
> >>>>>> To: dev
> >>>>>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> >>>>>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> >>>>> manager)
> >>>>>> Igniters,
> >>>>>>
> >>>>>> I just pushed the last ticket to ignite-2.7.6 branch; looks like we
> >>> are
> >>>>>> ready for the next iteration.
> >>>>>>
> >>>>>> Given that Dmitriy Pavlov will be unavailable till the end of this
> >>> week,
> >>>>> I
> >>>>>> will take over the release. TC re-run is started.
> >>>>>>
> >>>>>> чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin <
> >>>>>> dmitriy.govoruk...@gmail.com>:
> >>>>>>
> >>>>>>> Hi Igniters,
> >>>>>>>
> >>>>>>> I finished work on
> >>> https://issues.apache.org/jira/browse/IGNITE-12127,
> >>>>>> fix
> >>>>>>> already in master and ignite-2.7.6
> >>>>>>>
> >>>>>>> On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin <
> >>>>>>> 

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

[Artem Budnikov]

Hi,

I've created new versions for other projects on readme.io

-Artem

On 18.09.2019 19:17, Alexey Goncharuk wrote:

Igniters,

I am following the release process procedure [1] and currently on docs
update step. I can login to the admin panel, but I can only see the main
Ignite docs project. Who can add me to the remaining projects (C#/.NET,
C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone the docs
for 2.7.6?

[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process

ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk :


Ivan, thank you!

Will update release notes and start the build shortly.

ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :


Alexey,

I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master
and 2.7.6.

Best Regards,
Ivan Rakov

On 11.09.2019 18:13, Alexey Goncharuk wrote:

Good,

Please let me know when this is done, I will re-upload the release
artifacts.

ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :


Alexey,

The changes already have been tested, so no TC problems expected.
If this is true, then we need just a few hours to merge them.

From: Alexey Goncharuk
Sent: Wednesday, September 11, 2019 6:03 PM
To: dev
Cc: Dmitriy Govorukhin; Anton Kalashnikov
Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release

manager)

Alexandr,

I almost sent the vote email :) When do you expect the fix to be in

master

and 2.7.6?

ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin :


Folks,

A critical bug was detected in .NET [1].

I understand that it’s a little bit late, but I propose to include

this

issue into the release scope.

PR is ready, currently waiting for a TC visa.

Thoughts?

[1] - https://issues.apache.org/jira/browse/IGNITE-12163


From: Alexey Goncharuk
Sent: Monday, September 9, 2019 5:11 PM
To: dev
Cc: Dmitriy Govorukhin; Anton Kalashnikov
Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release

manager)

Igniters,

I just pushed the last ticket to ignite-2.7.6 branch; looks like we

are

ready for the next iteration.

Given that Dmitriy Pavlov will be unavailable till the end of this

week,

I

will take over the release. TC re-run is started.

чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:


Hi Igniters,

I finished work on

https://issues.apache.org/jira/browse/IGNITE-12127,

fix

already in master and ignite-2.7.6

On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:


Hi Alexey,

I think that I will finish work on the fix tomorrow. Fix already

completed

but I need to get VISA from TC bot.

On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:


Folks, it looks like I was overly optimistic with the estimates for

the

mentioned two tickets.

Dmitriy, Anton,
Can you share your vision when the issues will be fixed? Perhaps,

it

makes

sense to release 2.7.6 with the already fixed issues and schedule

2.7.7?

Neither of them is a regression, so it's ok to release 2.7.6 as it

is

now.

Thoughts?

сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk <

alexey.goncha...@gmail.com

:
Yes, my bad, forgot to include the link. That's the one.

пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov 
:

Alexey,

Does the issue [1] is related to this [2] discussion on the

user-list?

If yes, I think it is very important to include these fixes to

2.7.6.

[1] https://issues.apache.org/jira/browse/IGNITE-12127
[2]


http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html

On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov
 wrote:

Alexey,

Looks like important fixes, better to include them.

пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk <

alexey.goncha...@gmail.com>:

Igniters,

Given that the RC1 vote did not succeed and we are still

waiting

for

a few

minor fixes, may I suggest including these two tickest to the

2.7.6

scope?

https://issues.apache.org/jira/browse/IGNITE-12127
https://issues.apache.org/jira/browse/IGNITE-12128

The first one has been already reported on the dev-list [1],

the

second one

may cause a state when an Ignite node cannot start on

existing

persisted

data. Looking at the tickets, the fixes should be reasonably

easy,

so

it

should not shift 2.7.6 release timeline much.

Thoughts?

ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov <

nizhi...@apache.org

:

Separate repos for different Spark version is a good idea

for

me.

Anyway, can you help with Spark version migration,  for

now?

В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет:

Maybe the best solution today add for each new version of

Spark

the

sub-module (Spark-2.3, Spark-2.4) or the separate

repository

with

modules

for each version or another way with separate repository

and

different

branches like in

https://github.com/datastax/spark-cassandra-connector

3 ways to support different versions with the different

costs

of

support

In the case of se

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

[Alexey Goncharuk]

Igniters,

I am following the release process procedure [1] and currently on docs
update step. I can login to the admin panel, but I can only see the main
Ignite docs project. Who can add me to the remaining projects (C#/.NET,
C++, SQL, Integrations*, Ignite for Spark, Tools) or perhaps clone the docs
for 2.7.6?

[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process

ср, 11 сент. 2019 г. в 20:44, Alexey Goncharuk :

> Ivan, thank you!
>
> Will update release notes and start the build shortly.
>
> ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :
>
>> Alexey,
>>
>> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master
>> and 2.7.6.
>>
>> Best Regards,
>> Ivan Rakov
>>
>> On 11.09.2019 18:13, Alexey Goncharuk wrote:
>> > Good,
>> >
>> > Please let me know when this is done, I will re-upload the release
>> > artifacts.
>> >
>> > ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :
>> >
>> >> Alexey,
>> >>
>> >> The changes already have been tested, so no TC problems expected.
>> >> If this is true, then we need just a few hours to merge them.
>> >>
>> >> From: Alexey Goncharuk
>> >> Sent: Wednesday, September 11, 2019 6:03 PM
>> >> To: dev
>> >> Cc: Dmitriy Govorukhin; Anton Kalashnikov
>> >> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
>> manager)
>> >>
>> >> Alexandr,
>> >>
>> >> I almost sent the vote email :) When do you expect the fix to be in
>> master
>> >> and 2.7.6?
>> >>
>> >> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin :
>> >>
>> >>> Folks,
>> >>>
>> >>> A critical bug was detected in .NET [1].
>> >>>
>> >>> I understand that it’s a little bit late, but I propose to include
>> this
>> >>> issue into the release scope.
>> >>>
>> >>> PR is ready, currently waiting for a TC visa.
>> >>>
>> >>> Thoughts?
>> >>>
>> >>> [1] - https://issues.apache.org/jira/browse/IGNITE-12163
>> >>>
>> >>>
>> >>> From: Alexey Goncharuk
>> >>> Sent: Monday, September 9, 2019 5:11 PM
>> >>> To: dev
>> >>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
>> >>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
>> >> manager)
>> >>> Igniters,
>> >>>
>> >>> I just pushed the last ticket to ignite-2.7.6 branch; looks like we
>> are
>> >>> ready for the next iteration.
>> >>>
>> >>> Given that Dmitriy Pavlov will be unavailable till the end of this
>> week,
>> >> I
>> >>> will take over the release. TC re-run is started.
>> >>>
>> >>> чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin <
>> >>> dmitriy.govoruk...@gmail.com>:
>> >>>
>> >>>> Hi Igniters,
>> >>>>
>> >>>> I finished work on
>> https://issues.apache.org/jira/browse/IGNITE-12127,
>> >>> fix
>> >>>> already in master and ignite-2.7.6
>> >>>>
>> >>>> On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin <
>> >>>> dmitriy.govoruk...@gmail.com> wrote:
>> >>>>
>> >>>>> Hi Alexey,
>> >>>>>
>> >>>>> I think that I will finish work on the fix tomorrow. Fix already
>> >>>> completed
>> >>>>> but I need to get VISA from TC bot.
>> >>>>>
>> >>>>> On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk <
>> >>>>> alexey.goncha...@gmail.com> wrote:
>> >>>>>
>> >>>>>> Folks, it looks like I was overly optimistic with the estimates for
>> >>> the
>> >>>>>> mentioned two tickets.
>> >>>>>>
>> >>>>>> Dmitriy, Anton,
>> >>>>>> Can you share your vision when the issues will be fixed? Perhaps,
>> it
>> >>>> makes
>> >>>>>> sense to release 2.7.6 with the already fixed issues and schedule
>> >>> 2.7.7?
>> >>>>>> Neither of them is a regression, so it's ok to release 2.7.6 as it
>> >> is
>> >>>&g

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

[Alexey Goncharuk]

Ivan, thank you!

Will update release notes and start the build shortly.

ср, 11 сент. 2019 г. в 20:41, Ivan Rakov :

> Alexey,
>
> I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master
> and 2.7.6.
>
> Best Regards,
> Ivan Rakov
>
> On 11.09.2019 18:13, Alexey Goncharuk wrote:
> > Good,
> >
> > Please let me know when this is done, I will re-upload the release
> > artifacts.
> >
> > ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :
> >
> >> Alexey,
> >>
> >> The changes already have been tested, so no TC problems expected.
> >> If this is true, then we need just a few hours to merge them.
> >>
> >> From: Alexey Goncharuk
> >> Sent: Wednesday, September 11, 2019 6:03 PM
> >> To: dev
> >> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> >> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> manager)
> >>
> >> Alexandr,
> >>
> >> I almost sent the vote email :) When do you expect the fix to be in
> master
> >> and 2.7.6?
> >>
> >> ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin :
> >>
> >>> Folks,
> >>>
> >>> A critical bug was detected in .NET [1].
> >>>
> >>> I understand that it’s a little bit late, but I propose to include this
> >>> issue into the release scope.
> >>>
> >>> PR is ready, currently waiting for a TC visa.
> >>>
> >>> Thoughts?
> >>>
> >>> [1] - https://issues.apache.org/jira/browse/IGNITE-12163
> >>>
> >>>
> >>> From: Alexey Goncharuk
> >>> Sent: Monday, September 9, 2019 5:11 PM
> >>> To: dev
> >>> Cc: Dmitriy Govorukhin; Anton Kalashnikov
> >>> Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release
> >> manager)
> >>> Igniters,
> >>>
> >>> I just pushed the last ticket to ignite-2.7.6 branch; looks like we are
> >>> ready for the next iteration.
> >>>
> >>> Given that Dmitriy Pavlov will be unavailable till the end of this
> week,
> >> I
> >>> will take over the release. TC re-run is started.
> >>>
> >>> чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin <
> >>> dmitriy.govoruk...@gmail.com>:
> >>>
> >>>> Hi Igniters,
> >>>>
> >>>> I finished work on https://issues.apache.org/jira/browse/IGNITE-12127
> ,
> >>> fix
> >>>> already in master and ignite-2.7.6
> >>>>
> >>>> On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin <
> >>>> dmitriy.govoruk...@gmail.com> wrote:
> >>>>
> >>>>> Hi Alexey,
> >>>>>
> >>>>> I think that I will finish work on the fix tomorrow. Fix already
> >>>> completed
> >>>>> but I need to get VISA from TC bot.
> >>>>>
> >>>>> On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk <
> >>>>> alexey.goncha...@gmail.com> wrote:
> >>>>>
> >>>>>> Folks, it looks like I was overly optimistic with the estimates for
> >>> the
> >>>>>> mentioned two tickets.
> >>>>>>
> >>>>>> Dmitriy, Anton,
> >>>>>> Can you share your vision when the issues will be fixed? Perhaps, it
> >>>> makes
> >>>>>> sense to release 2.7.6 with the already fixed issues and schedule
> >>> 2.7.7?
> >>>>>> Neither of them is a regression, so it's ok to release 2.7.6 as it
> >> is
> >>>> now.
> >>>>>> Thoughts?
> >>>>>>
> >>>>>> сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk <
> >>>> alexey.goncha...@gmail.com
> >>>>>>> :
> >>>>>>> Yes, my bad, forgot to include the link. That's the one.
> >>>>>>>
> >>>>>>> пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov  >>> :
> >>>>>>>> Alexey,
> >>>>>>>>
> >>>>>>>> Does the issue [1] is related to this [2] discussion on the
> >>>> user-list?
> >>>>>>>> If yes, I think it is very important to include these fixes to
> >>> 2.7.6.
> >>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-

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

[Ivan Rakov]

Alexey,

I've merged https://issues.apache.org/jira/browse/IGNITE-12163 to master 
and 2.7.6.


Best Regards,
Ivan Rakov

On 11.09.2019 18:13, Alexey Goncharuk wrote:

Good,

Please let me know when this is done, I will re-upload the release
artifacts.

ср, 11 сент. 2019 г. в 18:11, Alexandr Shapkin :


Alexey,

The changes already have been tested, so no TC problems expected.
If this is true, then we need just a few hours to merge them.

From: Alexey Goncharuk
Sent: Wednesday, September 11, 2019 6:03 PM
To: dev
Cc: Dmitriy Govorukhin; Anton Kalashnikov
Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release manager)

Alexandr,

I almost sent the vote email :) When do you expect the fix to be in master
and 2.7.6?

ср, 11 сент. 2019 г. в 17:38, Alexandr Shapkin :


Folks,

A critical bug was detected in .NET [1].

I understand that it’s a little bit late, but I propose to include this
issue into the release scope.

PR is ready, currently waiting for a TC visa.

Thoughts?

[1] - https://issues.apache.org/jira/browse/IGNITE-12163


From: Alexey Goncharuk
Sent: Monday, September 9, 2019 5:11 PM
To: dev
Cc: Dmitriy Govorukhin; Anton Kalashnikov
Subject: Re: Re[2]: Apache Ignite 2.7.6 (Time, Scope, and Release

manager)

Igniters,

I just pushed the last ticket to ignite-2.7.6 branch; looks like we are
ready for the next iteration.

Given that Dmitriy Pavlov will be unavailable till the end of this week,

I

will take over the release. TC re-run is started.

чт, 5 сент. 2019 г. в 16:14, Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com>:


Hi Igniters,

I finished work on https://issues.apache.org/jira/browse/IGNITE-12127,

fix

already in master and ignite-2.7.6

On Wed, Sep 4, 2019 at 2:22 PM Dmitriy Govorukhin <
dmitriy.govoruk...@gmail.com> wrote:


Hi Alexey,

I think that I will finish work on the fix tomorrow. Fix already

completed

but I need to get VISA from TC bot.

On Mon, Sep 2, 2019 at 8:27 PM Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:


Folks, it looks like I was overly optimistic with the estimates for

the

mentioned two tickets.

Dmitriy, Anton,
Can you share your vision when the issues will be fixed? Perhaps, it

makes

sense to release 2.7.6 with the already fixed issues and schedule

2.7.7?

Neither of them is a regression, so it's ok to release 2.7.6 as it

is

now.

Thoughts?

сб, 31 авг. 2019 г. в 11:37, Alexey Goncharuk <

alexey.goncha...@gmail.com

:
Yes, my bad, forgot to include the link. That's the one.

пт, 30 авг. 2019 г. в 15:01, Maxim Muzafarov 
:

Alexey,

Does the issue [1] is related to this [2] discussion on the

user-list?

If yes, I think it is very important to include these fixes to

2.7.6.

[1] https://issues.apache.org/jira/browse/IGNITE-12127
[2]


http://apache-ignite-users.70518.x6.nabble.com/Node-failure-with-quot-Failed-to-write-buffer-quot-error-td29100.html

On Fri, 30 Aug 2019 at 14:26, Alexei Scherbakov
 wrote:

Alexey,

Looks like important fixes, better to include them.

пт, 30 авг. 2019 г. в 12:51, Alexey Goncharuk <

alexey.goncha...@gmail.com>:

Igniters,

Given that the RC1 vote did not succeed and we are still

waiting

for

a few

minor fixes, may I suggest including these two tickest to the

2.7.6

scope?

https://issues.apache.org/jira/browse/IGNITE-12127
https://issues.apache.org/jira/browse/IGNITE-12128

The first one has been already reported on the dev-list [1],

the

second one

may cause a state when an Ignite node cannot start on

existing

persisted

data. Looking at the tickets, the fixes should be reasonably

easy,

so

it

should not shift 2.7.6 release timeline much.

Thoughts?

ср, 28 авг. 2019 г. в 15:25, Nikolay Izhikov <

nizhi...@apache.org

:

Separate repos for different Spark version is a good idea

for

me.

Anyway, can you help with Spark version migration,  for

now?

В Ср, 28/08/2019 в 15:20 +0300, Alexey Zinoviev пишет:

Maybe the best solution today add for each new version of

Spark

the

sub-module (Spark-2.3, Spark-2.4) or the separate

repository

with

modules

for each version or another way with separate repository

and

different

branches like in

https://github.com/datastax/spark-cassandra-connector

3 ways to support different versions with the different

costs

of

support

In the case of separate repository I could help, for

example

ср, 28 авг. 2019 г. в 14:57, Nikolay Izhikov <

nizhi...@apache.org

:

Hello, Alexey.


But the
compatibility with Spark 2.3 will be broken, isn't

it?

Yes.


Do you have any
plans to support the different version of Spark

without

loosing

your

unique

expertise in Spark-Ignite integration?

What do you mean by "my unique expertise"? :)

How do you see support of several Spark version?


В Ср, 28/08/2019 в 14:29 +0300, Alexey Zinoviev пишет:

Dear Nikolay Izhikov
Are you going to update the Ignite-Spark integration

for

Spark 2.4.

But

the

compatibility with Spark 2.3 will be broken, isn't

it?

Do

you

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

[Dmitriy Pavlov]

Absolutely, error messages are the most important guidance for users, I see
no reason to reject.

пн, 26 авг. 2019 г. в 23:26, Denis Magda :

> Dmitry,
>
> As long as the vote has been canceled and we're going to do several
> improvements before starting a new one, I'd like to ask your permission to
> include this ticket in 2.7.6 scope:
> https://issues.apache.org/jira/browse/IGNITE-12106
>
> It suggests the changes in log messages to simplify "binary metadata not
> found"-class issues troubleshooting with the community involvement.
> Presently, users stumble upon the issue frequently and can't come around it
> w/o reaching us out. More details are here:
>
> http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html
>
> -
> Denis
>
>
> On Tue, Aug 20, 2019 at 8:00 AM Artem Budnikov <
> a.budnikov.ign...@gmail.com>
> wrote:
>
> > Hi Dmitry,
> >
> > The release notes reviewed. Please see my comment in the pull request.
> >
> > -Artem
> >
> > On 19.08.2019 14:20, Dmitriy Pavlov wrote:
> > > Hi Andrey,
> > >
> > > could you please take a look at
> > > https://issues.apache.org/jira/browse/IGNITE-12061 ?
> > >
> > > Are you comfortable with merging it to release (in rush mode)?
> > >
> > > Sincerely,
> > > Dmitriy Pavlov
> > >
> > > вс, 18 авг. 2019 г. в 18:12, Dmitriy Pavlov :
> > >
> > >> Hi Igniters,
> > >>
> > >> please review release notes for Ignite 2.7.6 (-rc0), tickets:
> > >> https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.7.6-rc0 :
> > >>
> > >> Text version:
> > >> https://github.com/apache/ignite/pull/6788/files
> > >>
> > >> And corresponding HTML version (will be available at SVN once vote
> > passes):
> > >>
> > >> - Ignite work directory is set to current user's home directory by
> > >> default, native persistence files aren't stored in Temp anymore
> > >> [#IGNITE-12057] <
> https://issues.apache.org/jira/browse/IGNITE-12057
> > >
> > >> - Fixed the bug when SELECT with an equality predicate on the part
> > of
> > >> a primary compound key returned a single row result while multiple
> > matching
> > >> rows existed in the table [#IGNITE-12068]
> > >> 
> > >> - Fixed data corruption in the rare case when page replacement can
> > >> reload an outdated page during checkpoint [#IGNITE-12081]
> > >> 
> > >> - Fixed tree corruption caused by incorrect row size calculation
> for
> > >> shared cache groups [#IGNITE-12060]
> > >> 
> > >> - Java heap footprint reduced by optimizing
> > >> GridDhtPartitionsFullMessage maps in exchange history
> > [#IGNITE-11767]
> > >> 
> > >> - .NET: Fix for native persistence, now it works with custom
> > affinity
> > >> function [#IGNITE-10451]
> > >> 
> > >>
> > >>
> > >> For remained tickets
> > >>
> > >>
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6%20and%20(labels%20!%3D%202.7.6-rc0%20or%20labels%20is%20EMPTY%20)
> > >>
> > >> please add desired release note as a comment (since I still not asked
> > >> Infra about a separate field).
> > >>
> > >> Sincerely,
> > >> Dmitriy Pavlov
> > >>
> > >> вс, 18 авг. 2019 г. в 12:59, Dmitriy Pavlov :
> > >>
> > >>> Ok, Ivan, thank you for sharing this bit of info. I always prefer to
> > >>> avoid any rush. It may be reasonable to wait for 2.8 or maybe we'll
> > decide
> > >>> to do 2.7.7. As the release is a trigger for activity in the
> > community, it
> > >>> is always better to prepare releases.
> > >>>
> > >>> BTW, minor correction: ticket mentioned here as IGNITE-12507
> > >>> (Persistence files are stored to temp dir) has
> > >>> actually is https://issues.apache.org/jira/browse/IGNITE-12057
> Anyway,
> > >>> thanks to Anton K. & Dmitriy G., is already in the release branch.
> > >>>
> > >>> вс, 18 авг. 2019 г. в 06:27, Ivan Pavlukhina :
> > >>>
> >  Zhenya, Dmitriy,
> > 
> > >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
> >  2.7.6, i
> > >>> have no clue - why,
> >  The reason here is a lack of time to ensure that everything is fine
> >  there. The patch is valuable but not so trivial. Honestly, I find it
> > wrong
> >  to merge a changes I am not sure with (yet). Especially in a hurry.
> > 
> >  Sent from my iPhone
> > 
> > > On 17 Aug 2019, at 13:13, Zhenya Stanilovsky
> >   wrote:
> > > I hope there is no data loss here, but index tree corruption can be
> >  easily obtained.
> > > Impact: someone believe that inline_size has been changed due to
> > index
> >  recreation but that`s not so.
> > >> Hi Evgeniy,
> > >>
> > >> I can't review this change. We need approve of a 

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

[Denis Magda]

Dmitry,

As long as the vote has been canceled and we're going to do several
improvements before starting a new one, I'd like to ask your permission to
include this ticket in 2.7.6 scope:
https://issues.apache.org/jira/browse/IGNITE-12106

It suggests the changes in log messages to simplify "binary metadata not
found"-class issues troubleshooting with the community involvement.
Presently, users stumble upon the issue frequently and can't come around it
w/o reaching us out. More details are here:
http://apache-ignite-developers.2346864.n4.nabble.com/Metastore-disappears-in-Docker-on-restarts-td43107.html

-
Denis


On Tue, Aug 20, 2019 at 8:00 AM Artem Budnikov 
wrote:

> Hi Dmitry,
>
> The release notes reviewed. Please see my comment in the pull request.
>
> -Artem
>
> On 19.08.2019 14:20, Dmitriy Pavlov wrote:
> > Hi Andrey,
> >
> > could you please take a look at
> > https://issues.apache.org/jira/browse/IGNITE-12061 ?
> >
> > Are you comfortable with merging it to release (in rush mode)?
> >
> > Sincerely,
> > Dmitriy Pavlov
> >
> > вс, 18 авг. 2019 г. в 18:12, Dmitriy Pavlov :
> >
> >> Hi Igniters,
> >>
> >> please review release notes for Ignite 2.7.6 (-rc0), tickets:
> >> https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.7.6-rc0 :
> >>
> >> Text version:
> >> https://github.com/apache/ignite/pull/6788/files
> >>
> >> And corresponding HTML version (will be available at SVN once vote
> passes):
> >>
> >> - Ignite work directory is set to current user's home directory by
> >> default, native persistence files aren't stored in Temp anymore
> >> [#IGNITE-12057]  >
> >> - Fixed the bug when SELECT with an equality predicate on the part
> of
> >> a primary compound key returned a single row result while multiple
> matching
> >> rows existed in the table [#IGNITE-12068]
> >> 
> >> - Fixed data corruption in the rare case when page replacement can
> >> reload an outdated page during checkpoint [#IGNITE-12081]
> >> 
> >> - Fixed tree corruption caused by incorrect row size calculation for
> >> shared cache groups [#IGNITE-12060]
> >> 
> >> - Java heap footprint reduced by optimizing
> >> GridDhtPartitionsFullMessage maps in exchange history
> [#IGNITE-11767]
> >> 
> >> - .NET: Fix for native persistence, now it works with custom
> affinity
> >> function [#IGNITE-10451]
> >> 
> >>
> >>
> >> For remained tickets
> >>
> >>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6%20and%20(labels%20!%3D%202.7.6-rc0%20or%20labels%20is%20EMPTY%20)
> >>
> >> please add desired release note as a comment (since I still not asked
> >> Infra about a separate field).
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> вс, 18 авг. 2019 г. в 12:59, Dmitriy Pavlov :
> >>
> >>> Ok, Ivan, thank you for sharing this bit of info. I always prefer to
> >>> avoid any rush. It may be reasonable to wait for 2.8 or maybe we'll
> decide
> >>> to do 2.7.7. As the release is a trigger for activity in the
> community, it
> >>> is always better to prepare releases.
> >>>
> >>> BTW, minor correction: ticket mentioned here as IGNITE-12507
> >>> (Persistence files are stored to temp dir) has
> >>> actually is https://issues.apache.org/jira/browse/IGNITE-12057 Anyway,
> >>> thanks to Anton K. & Dmitriy G., is already in the release branch.
> >>>
> >>> вс, 18 авг. 2019 г. в 06:27, Ivan Pavlukhina :
> >>>
>  Zhenya, Dmitriy,
> 
> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
>  2.7.6, i
> >>> have no clue - why,
>  The reason here is a lack of time to ensure that everything is fine
>  there. The patch is valuable but not so trivial. Honestly, I find it
> wrong
>  to merge a changes I am not sure with (yet). Especially in a hurry.
> 
>  Sent from my iPhone
> 
> > On 17 Aug 2019, at 13:13, Zhenya Stanilovsky
>   wrote:
> > I hope there is no data loss here, but index tree corruption can be
>  easily obtained.
> > Impact: someone believe that inline_size has been changed due to
> index
>  recreation but that`s not so.
> >> Hi Evgeniy,
> >>
> >> I can't review this change. We need approve of a committer, who is
>  SQL
> >> expert,  here.
> >>
> >> What would be an impact on users if we don' include it into 2.7.6?
> >>
> >> Is it a critical/data loss issue? If not, I agree it can wait for
> 2.8
> >> release.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky  >:
> >>
> >>> hi Dmitriy, Ivan Pavlukhin suggest to 

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

[Artem Budnikov]

Hi Dmitry,

The release notes reviewed. Please see my comment in the pull request.

-Artem

On 19.08.2019 14:20, Dmitriy Pavlov wrote:

Hi Andrey,

could you please take a look at
https://issues.apache.org/jira/browse/IGNITE-12061 ?

Are you comfortable with merging it to release (in rush mode)?

Sincerely,
Dmitriy Pavlov

вс, 18 авг. 2019 г. в 18:12, Dmitriy Pavlov :


Hi Igniters,

please review release notes for Ignite 2.7.6 (-rc0), tickets:
https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.7.6-rc0 :

Text version:
https://github.com/apache/ignite/pull/6788/files

And corresponding HTML version (will be available at SVN once vote passes):

- Ignite work directory is set to current user's home directory by
default, native persistence files aren't stored in Temp anymore
[#IGNITE-12057] 
- Fixed the bug when SELECT with an equality predicate on the part of
a primary compound key returned a single row result while multiple matching
rows existed in the table [#IGNITE-12068]

- Fixed data corruption in the rare case when page replacement can
reload an outdated page during checkpoint [#IGNITE-12081]

- Fixed tree corruption caused by incorrect row size calculation for
shared cache groups [#IGNITE-12060]

- Java heap footprint reduced by optimizing
GridDhtPartitionsFullMessage maps in exchange history [#IGNITE-11767]

- .NET: Fix for native persistence, now it works with custom affinity
function [#IGNITE-10451]



For remained tickets

https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6%20and%20(labels%20!%3D%202.7.6-rc0%20or%20labels%20is%20EMPTY%20)

please add desired release note as a comment (since I still not asked
Infra about a separate field).

Sincerely,
Dmitriy Pavlov

вс, 18 авг. 2019 г. в 12:59, Dmitriy Pavlov :


Ok, Ivan, thank you for sharing this bit of info. I always prefer to
avoid any rush. It may be reasonable to wait for 2.8 or maybe we'll decide
to do 2.7.7. As the release is a trigger for activity in the community, it
is always better to prepare releases.

BTW, minor correction: ticket mentioned here as IGNITE-12507
(Persistence files are stored to temp dir) has
actually is https://issues.apache.org/jira/browse/IGNITE-12057 Anyway,
thanks to Anton K. & Dmitriy G., is already in the release branch.

вс, 18 авг. 2019 г. в 06:27, Ivan Pavlukhina :


Zhenya, Dmitriy,


hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from

2.7.6, i

have no clue - why,

The reason here is a lack of time to ensure that everything is fine
there. The patch is valuable but not so trivial. Honestly, I find it wrong
to merge a changes I am not sure with (yet). Especially in a hurry.

Sent from my iPhone


On 17 Aug 2019, at 13:13, Zhenya Stanilovsky

 wrote:

I hope there is no data loss here, but index tree corruption can be

easily obtained.

Impact: someone believe that inline_size has been changed due to index

recreation but that`s not so.

Hi Evgeniy,

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

SQL

expert,  here.

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

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

Sincerely,
Dmitriy Pavlov

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


hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from

2.7.6, i

have no clue - why, but seems i can`t merge it without his visa.
thanks.


Hi Igniters,

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

assigned

since
it was discussed before in private communication).

It is not a regression but can cause data corruption, so I'd

rather wait

for the fix.

Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the

first RC

during the weekend, so I would be grateful if fixes can be

cherry-piked

to
the branch today. Also, since narrow time limit, please trigger

Run All

after each commit in 2.7.6. This will allow to immediately locate

which

commit caused test failure.

Sincerely,
Dmitriy Pavlov

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


Hi Ivan,

yes, sure.

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

  If it contains conflicts it is better to push to 2.7.6-based

branch and

start additional run-all, example
https://github.com/apache/ignite/pull/6781 -it is PR for

ignite-9562,

base: 2.7.6

Sincerely,
Dmitriy Pavlov

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


Dmitriy,

We accomplished with

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

Should I cherry-pick it to release branch?

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

[Dmitriy Pavlov]

Hi Andrey,

could you please take a look at
https://issues.apache.org/jira/browse/IGNITE-12061 ?

Are you comfortable with merging it to release (in rush mode)?

Sincerely,
Dmitriy Pavlov

вс, 18 авг. 2019 г. в 18:12, Dmitriy Pavlov :

> Hi Igniters,
>
> please review release notes for Ignite 2.7.6 (-rc0), tickets:
> https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.7.6-rc0 :
>
> Text version:
> https://github.com/apache/ignite/pull/6788/files
>
> And corresponding HTML version (will be available at SVN once vote passes):
>
>- Ignite work directory is set to current user's home directory by
>default, native persistence files aren't stored in Temp anymore
>[#IGNITE-12057] 
>- Fixed the bug when SELECT with an equality predicate on the part of
>a primary compound key returned a single row result while multiple matching
>rows existed in the table [#IGNITE-12068]
>
>- Fixed data corruption in the rare case when page replacement can
>reload an outdated page during checkpoint [#IGNITE-12081]
>
>- Fixed tree corruption caused by incorrect row size calculation for
>shared cache groups [#IGNITE-12060]
>
>- Java heap footprint reduced by optimizing
>GridDhtPartitionsFullMessage maps in exchange history [#IGNITE-11767]
>
>- .NET: Fix for native persistence, now it works with custom affinity
>function [#IGNITE-10451]
>
>
>
> For remained tickets
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6%20and%20(labels%20!%3D%202.7.6-rc0%20or%20labels%20is%20EMPTY%20)
>
> please add desired release note as a comment (since I still not asked
> Infra about a separate field).
>
> Sincerely,
> Dmitriy Pavlov
>
> вс, 18 авг. 2019 г. в 12:59, Dmitriy Pavlov :
>
>> Ok, Ivan, thank you for sharing this bit of info. I always prefer to
>> avoid any rush. It may be reasonable to wait for 2.8 or maybe we'll decide
>> to do 2.7.7. As the release is a trigger for activity in the community, it
>> is always better to prepare releases.
>>
>> BTW, minor correction: ticket mentioned here as IGNITE-12507
>> (Persistence files are stored to temp dir) has
>> actually is https://issues.apache.org/jira/browse/IGNITE-12057 Anyway,
>> thanks to Anton K. & Dmitriy G., is already in the release branch.
>>
>> вс, 18 авг. 2019 г. в 06:27, Ivan Pavlukhina :
>>
>>> Zhenya, Dmitriy,
>>>
>>> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
>>> 2.7.6, i
>>> >>> have no clue - why,
>>>
>>> The reason here is a lack of time to ensure that everything is fine
>>> there. The patch is valuable but not so trivial. Honestly, I find it wrong
>>> to merge a changes I am not sure with (yet). Especially in a hurry.
>>>
>>> Sent from my iPhone
>>>
>>> > On 17 Aug 2019, at 13:13, Zhenya Stanilovsky
>>>  wrote:
>>> >
>>> > I hope there is no data loss here, but index tree corruption can be
>>> easily obtained.
>>> > Impact: someone believe that inline_size has been changed due to index
>>> recreation but that`s not so.
>>> >
>>> >> Hi Evgeniy,
>>> >>
>>> >> I can't review this change. We need approve of a committer, who is
>>> SQL
>>> >> expert,  here.
>>> >>
>>> >> What would be an impact on users if we don' include it into 2.7.6?
>>> >>
>>> >> Is it a critical/data loss issue? If not, I agree it can wait for 2.8
>>> >> release.
>>> >>
>>> >> Sincerely,
>>> >> Dmitriy Pavlov
>>> >>
>>> >> сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :
>>> >>
>>> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
>>> 2.7.6, i
>>> >>> have no clue - why, but seems i can`t merge it without his visa.
>>> >>> thanks.
>>> >>>
>>> >>> > Hi Igniters,
>>> >>> >
>>> >>> > I also suggest adding newly created critical bug into scope
>>> >>> > https://issues.apache.org/jira/browse/IGNITE-12081 (already
>>> assigned
>>> >>> > since
>>> >>> > it was discussed before in private communication).
>>> >>> >
>>> >>> > It is not a regression but can cause data corruption, so I'd
>>> rather wait
>>> >>> > for the fix.
>>> >>> >
>>> >>> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the
>>> first RC
>>> >>> > during the weekend, so I would be grateful if fixes can be
>>> cherry-piked
>>> >>> > to
>>> >>> > the branch today. Also, since narrow time limit, please trigger
>>> Run All
>>> >>> > after each commit in 2.7.6. This will allow to immediately locate
>>> which
>>> >>> > commit caused test failure.
>>> >>> >
>>> >>> > Sincerely,
>>> >>> > Dmitriy Pavlov
>>> >>> >
>>> >>> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>>> >>> >
>>> >>> >> Hi Ivan,
>>> >>> >>
>>> >>> >> yes, sure.
>>> >>> >>
>>> >>> >> If it is 

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

[Dmitriy Pavlov]

Hi Igniters,

please review release notes for Ignite 2.7.6 (-rc0), tickets:
https://issues.apache.org/jira/issues/?jql=labels%20%3D%202.7.6-rc0 :

Text version:
https://github.com/apache/ignite/pull/6788/files

And corresponding HTML version (will be available at SVN once vote passes):

   - Ignite work directory is set to current user's home directory by
   default, native persistence files aren't stored in Temp anymore
   [#IGNITE-12057] 
   - Fixed the bug when SELECT with an equality predicate on the part of a
   primary compound key returned a single row result while multiple matching
   rows existed in the table [#IGNITE-12068]
   
   - Fixed data corruption in the rare case when page replacement can
   reload an outdated page during checkpoint [#IGNITE-12081]
   
   - Fixed tree corruption caused by incorrect row size calculation for
   shared cache groups [#IGNITE-12060]
   
   - Java heap footprint reduced by optimizing GridDhtPartitionsFullMessage
   maps in exchange history [#IGNITE-11767]
   
   - .NET: Fix for native persistence, now it works with custom affinity
   function [#IGNITE-10451]
   


For remained tickets
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.7.6%20and%20(labels%20!%3D%202.7.6-rc0%20or%20labels%20is%20EMPTY%20)

please add desired release note as a comment (since I still not asked Infra
about a separate field).

Sincerely,
Dmitriy Pavlov

вс, 18 авг. 2019 г. в 12:59, Dmitriy Pavlov :

> Ok, Ivan, thank you for sharing this bit of info. I always prefer to avoid
> any rush. It may be reasonable to wait for 2.8 or maybe we'll decide to do
> 2.7.7. As the release is a trigger for activity in the community, it is
> always better to prepare releases.
>
> BTW, minor correction: ticket mentioned here as IGNITE-12507 (Persistence
> files are stored to temp dir) has
> actually is https://issues.apache.org/jira/browse/IGNITE-12057 Anyway,
> thanks to Anton K. & Dmitriy G., is already in the release branch.
>
> вс, 18 авг. 2019 г. в 06:27, Ivan Pavlukhina :
>
>> Zhenya, Dmitriy,
>>
>> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
>> 2.7.6, i
>> >>> have no clue - why,
>>
>> The reason here is a lack of time to ensure that everything is fine
>> there. The patch is valuable but not so trivial. Honestly, I find it wrong
>> to merge a changes I am not sure with (yet). Especially in a hurry.
>>
>> Sent from my iPhone
>>
>> > On 17 Aug 2019, at 13:13, Zhenya Stanilovsky 
>> wrote:
>> >
>> > I hope there is no data loss here, but index tree corruption can be
>> easily obtained.
>> > Impact: someone believe that inline_size has been changed due to index
>> recreation but that`s not so.
>> >
>> >> Hi Evgeniy,
>> >>
>> >> I can't review this change. We need approve of a committer, who is  SQL
>> >> expert,  here.
>> >>
>> >> What would be an impact on users if we don' include it into 2.7.6?
>> >>
>> >> Is it a critical/data loss issue? If not, I agree it can wait for 2.8
>> >> release.
>> >>
>> >> Sincerely,
>> >> Dmitriy Pavlov
>> >>
>> >> сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :
>> >>
>> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from
>> 2.7.6, i
>> >>> have no clue - why, but seems i can`t merge it without his visa.
>> >>> thanks.
>> >>>
>> >>> > Hi Igniters,
>> >>> >
>> >>> > I also suggest adding newly created critical bug into scope
>> >>> > https://issues.apache.org/jira/browse/IGNITE-12081 (already
>> assigned
>> >>> > since
>> >>> > it was discussed before in private communication).
>> >>> >
>> >>> > It is not a regression but can cause data corruption, so I'd rather
>> wait
>> >>> > for the fix.
>> >>> >
>> >>> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the
>> first RC
>> >>> > during the weekend, so I would be grateful if fixes can be
>> cherry-piked
>> >>> > to
>> >>> > the branch today. Also, since narrow time limit, please trigger Run
>> All
>> >>> > after each commit in 2.7.6. This will allow to immediately locate
>> which
>> >>> > commit caused test failure.
>> >>> >
>> >>> > Sincerely,
>> >>> > Dmitriy Pavlov
>> >>> >
>> >>> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
>> >>> >
>> >>> >> Hi Ivan,
>> >>> >>
>> >>> >> yes, sure.
>> >>> >>
>> >>> >> If it is cherry-picked without conflicts, just push it.
>> >>> >>
>> >>> >>  If it contains conflicts it is better to push to 2.7.6-based
>> branch and
>> >>> >> start additional run-all, example
>> >>> >> https://github.com/apache/ignite/pull/6781 -it is PR for
>> ignite-9562,
>> >>> >> base: 2.7.6
>> >>> >>
>> >>> >> Sincerely,
>> >>> >> Dmitriy Pavlov
>> >>> >>
>> >>> >> пт, 16 авг. 2019 г. в 12:28, 

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

[Dmitriy Pavlov]

Ok, Ivan, thank you for sharing this bit of info. I always prefer to avoid
any rush. It may be reasonable to wait for 2.8 or maybe we'll decide to do
2.7.7. As the release is a trigger for activity in the community, it is
always better to prepare releases.

BTW, minor correction: ticket mentioned here as IGNITE-12507 (Persistence
files are stored to temp dir) has
actually is https://issues.apache.org/jira/browse/IGNITE-12057 Anyway,
thanks to Anton K. & Dmitriy G., is already in the release branch.

вс, 18 авг. 2019 г. в 06:27, Ivan Pavlukhina :

> Zhenya, Dmitriy,
>
> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6,
> i
> >>> have no clue - why,
>
> The reason here is a lack of time to ensure that everything is fine there.
> The patch is valuable but not so trivial. Honestly, I find it wrong to
> merge a changes I am not sure with (yet). Especially in a hurry.
>
> Sent from my iPhone
>
> > On 17 Aug 2019, at 13:13, Zhenya Stanilovsky 
> wrote:
> >
> > I hope there is no data loss here, but index tree corruption can be
> easily obtained.
> > Impact: someone believe that inline_size has been changed due to index
> recreation but that`s not so.
> >
> >> Hi Evgeniy,
> >>
> >> I can't review this change. We need approve of a committer, who is  SQL
> >> expert,  here.
> >>
> >> What would be an impact on users if we don' include it into 2.7.6?
> >>
> >> Is it a critical/data loss issue? If not, I agree it can wait for 2.8
> >> release.
> >>
> >> Sincerely,
> >> Dmitriy Pavlov
> >>
> >> сб, 17 авг. 2019 г. в 12:43, Zhenya Stanilovsky :
> >>
> >>> hi Dmitriy, Ivan Pavlukhin suggest to exclude IGNITE-12061 from 2.7.6,
> i
> >>> have no clue - why, but seems i can`t merge it without his visa.
> >>> thanks.
> >>>
> >>> > Hi Igniters,
> >>> >
> >>> > I also suggest adding newly created critical bug into scope
> >>> > https://issues.apache.org/jira/browse/IGNITE-12081 (already assigned
> >>> > since
> >>> > it was discussed before in private communication).
> >>> >
> >>> > It is not a regression but can cause data corruption, so I'd rather
> wait
> >>> > for the fix.
> >>> >
> >>> > Eduard Shangareev, Stanilovsky Evgeny I'm going to assemble the
> first RC
> >>> > during the weekend, so I would be grateful if fixes can be
> cherry-piked
> >>> > to
> >>> > the branch today. Also, since narrow time limit, please trigger Run
> All
> >>> > after each commit in 2.7.6. This will allow to immediately locate
> which
> >>> > commit caused test failure.
> >>> >
> >>> > Sincerely,
> >>> > Dmitriy Pavlov
> >>> >
> >>> > пт, 16 авг. 2019 г. в 13:33, Dmitriy Pavlov :
> >>> >
> >>> >> Hi Ivan,
> >>> >>
> >>> >> yes, sure.
> >>> >>
> >>> >> If it is cherry-picked without conflicts, just push it.
> >>> >>
> >>> >>  If it contains conflicts it is better to push to 2.7.6-based
> branch and
> >>> >> start additional run-all, example
> >>> >> https://github.com/apache/ignite/pull/6781 -it is PR for
> ignite-9562,
> >>> >> base: 2.7.6
> >>> >>
> >>> >> Sincerely,
> >>> >> Dmitriy Pavlov
> >>> >>
> >>> >> пт, 16 авг. 2019 г. в 12:28, Павлухин Иван :
> >>> >>
> >>> >>> Dmitriy,
> >>> >>>
> >>> >>> We accomplished with
> >>> https://issues.apache.org/jira/browse/IGNITE-12068
> >>> >>>
> >>> >>> Should I cherry-pick it to release branch?
> >>> >>>
> >>> >>> пт, 16 авг. 2019 г. в 11:28, Dmitriy Pavlov :
> >>> >>> >
> >>> >>> > Hi Igniters,
> >>> >>> >
> >>> >>> > Yesterday was a planned date of code freeze.
> >>> >>> >
> >>> >>> > So the scope (related both to features and to bugs) is final,
> we're
> >>> >>> > entering to stabilization phase. Nothing can be included into
> scope
> >>> >>> besides
> >>> >>> > blockers approved by the release manager.
> >>> >>> >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >>> >>> > <
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process>
> >>> >>> >
> >>> >>> > Unresolved tickets are:
> >>> >>> > IGNITE-12071  Eduard Shangareev
> >>> >>> > IGNITE-12068 Ivan Pavlukhin
> >>> >>> > IGNITE-9562 Eduard Shangareev
> >>> >>> > IGNITE-12057 Anton Kalashnikov
> >>> >>> > IGNITE-12061 Stanilovsky Evgeny
> >>> >>> >
> >>> >>> > Sincerely,
> >>> >>> > Dmitriy Pavlov
> >>> >>> >
> >>> >>> > чт, 15 авг. 2019 г. в 20:12, Zhenya Stanilovsky <
> arzamas...@mail.ru
> >>> >:
> >>> >>> >
> >>> >>> > > Dmitriy, review passed, plz proceed.
> >>> >>> > > thanks !
> >>> >>> > >
> >>> >>> > > > I removed
> https://issues.apache.org/jira/browse/IGNITE-12032
> >>> >>> until
> >>> >>> > > > nobody
> >>> >>> > > > volunteer to complete the task.
> >>> >>> > > >
> >>> >>> > > > Evgeniy, please keep me updated about IGNITE-12061.
> >>> >>> > > >
> >>> >>> > > > чт, 15 авг. 2019 г. в 16:56, Zhenya Stanilovsky
> >>> >>> > > >  >>> >>> > > >> :
> >>> >>> > > >
> >>> >>> > > >> yep, i`l try to call someone who probably familiar with this
> >>> >>> problem.
> >>> >>> > > >>
> >>> >>> > > >> >
> >>> >>> > > >> >
> >>> >>> > > >> >Ok, I've removed Spark from the scope.
> >>> >>> > 

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

[Dmitriy Govorukhin]

Hi all,
Can we include https://issues.apache.org/jira/browse/IGNITE-12060? This is
a https://issues.apache.org/jira/browse/IGNITE-11953

On Fri, Aug 9, 2019 at 10:04 AM Nikolay Izhikov  wrote:

> Hello, Deni.
>
> > Nickolay, could you check if that's a quick upgrade?
>
> Yes, I will take a look.
>
>
> В Чт, 08/08/2019 в 11:08 -0700, Denis Magda пишет:
> > Dmitry,
> >
> > Please add this BTree corruption fix to the scope:
> > https://issues.apache.org/jira/browse/IGNITE-11953
> >
> > Plus, I would upgrade our Spark integration to version 2.4 as long as 2.3
> > goes with limitations reported by our users:
> > https://issues.apache.org/jira/browse/IGNITE-12054
> >
> > Nickolay, could you check if that's a quick upgrade?
> >
> > -
> > Denis
> >
> >
> > On Thu, Aug 8, 2019 at 10:40 AM Dmitriy Pavlov 
> wrote:
> >
> > > Hi Ivan, Ilya, Igniters,
> > >
> > >
> > >
> > > I would like this release would be as minimal as possible.
> > >
> > >
> > >
> > > According to dates proposed we could freeze scope at 12.08, 4 days is
> more
> > > than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is
> > > also ok for me if we decide to have more relaxed dates.
> > >
> > >
> > >
> > > For now, I suppose the following fixed should be cherry-picked:
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker)
> > > GridDhtPartitionsFullMessage retains huge maps on heap in exchange
> history
> > >
> > >
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET:
> > > Persistence does not work with custom affinity function
> > >
> > >
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug)
> Destroyed
> > > cache that resurrected on an old offline node breaks PME
> > >
> > >
> > >
> > > But I will continue to research JIRA.
> > >
> > >
> > >
> > > Sincerely,
> > >
> > > Dmitriy Pavlov
> > >
> > >
> > > чт, 8 авг. 2019 г. в 17:30, Павлухин Иван :
> > >
> > > > > What's the scope for this release?
> > > >
> > > > Same question.
> > > >
> > > > On the other hand an idea of 2.7.6 release attracts me because having
> > > > a practice of doing frequent minor releases can help us to build
> > > > reliable and predictable release rails.
> > > >
> > > > чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev <
> ilya.kasnach...@gmail.com>:
> > > > >
> > > > > Hello!
> > > > >
> > > > > What's the scope for this release?
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
> > > > >
> > > > > > Hi Apache Ignite Developers,
> > > > > >
> > > > > >
> > > > > >
> > > > > > We seem to be on the same page about 2.8 release, but we’ve
> started
> > >
> > > new
> > > > > > practice - minor releases, the first release was 2.7.5.
> > >
> > > Unfortunately,
> > > > > > there is a couple of issues still not fixed in that release, so I
> > >
> > > would
> > > > > > like to propose to prepare one more minor release for Apache
> Ignite.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I propose my candidacy to be release manager once again.
> > > > > >
> > > > > >
> > > > > >
> > > > > > I could (of course with help from Peter Ivanov) do some
> additional
> > > >
> > > > efforts
> > > > > > to complete and improve process doc
> > > > > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > > > >
> > > > > >
> > > > > >
> > > > > > I propose (most optimistic) dates for release stages:
> > > > > >
> > > > > > Scope Freeze: August 12, 2019
> > > > > >
> > > > > > Code Freeze: August 15, 2019
> > > > > >
> > > > > > Voting Date: August 22, 2019
> > > > > >
> > > > > > Release Date: August 27, 2019
> > > > > >
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > > >
> > > > > > If nobody minds, I will create branch 2.7.6 based on 2.7.5 and
> set up
> > > >
> > > > in
> > > > > > the TC Bot during the weekend.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Sincerely,
> > > > > >
> > > > > > Dmitriy Pavlov
> > > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > > >
>

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

[Nikolay Izhikov]

Hello, Deni.

> Nickolay, could you check if that's a quick upgrade?

Yes, I will take a look.


В Чт, 08/08/2019 в 11:08 -0700, Denis Magda пишет:
> Dmitry,
> 
> Please add this BTree corruption fix to the scope:
> https://issues.apache.org/jira/browse/IGNITE-11953
> 
> Plus, I would upgrade our Spark integration to version 2.4 as long as 2.3
> goes with limitations reported by our users:
> https://issues.apache.org/jira/browse/IGNITE-12054
> 
> Nickolay, could you check if that's a quick upgrade?
> 
> -
> Denis
> 
> 
> On Thu, Aug 8, 2019 at 10:40 AM Dmitriy Pavlov  wrote:
> 
> > Hi Ivan, Ilya, Igniters,
> > 
> > 
> > 
> > I would like this release would be as minimal as possible.
> > 
> > 
> > 
> > According to dates proposed we could freeze scope at 12.08, 4 days is more
> > than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is
> > also ok for me if we decide to have more relaxed dates.
> > 
> > 
> > 
> > For now, I suppose the following fixed should be cherry-picked:
> > 
> > https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker)
> > GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
> > 
> > 
> > 
> > https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET:
> > Persistence does not work with custom affinity function
> > 
> > 
> > 
> > https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug) Destroyed
> > cache that resurrected on an old offline node breaks PME
> > 
> > 
> > 
> > But I will continue to research JIRA.
> > 
> > 
> > 
> > Sincerely,
> > 
> > Dmitriy Pavlov
> > 
> > 
> > чт, 8 авг. 2019 г. в 17:30, Павлухин Иван :
> > 
> > > > What's the scope for this release?
> > > 
> > > Same question.
> > > 
> > > On the other hand an idea of 2.7.6 release attracts me because having
> > > a practice of doing frequent minor releases can help us to build
> > > reliable and predictable release rails.
> > > 
> > > чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev :
> > > > 
> > > > Hello!
> > > > 
> > > > What's the scope for this release?
> > > > 
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > > 
> > > > 
> > > > чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
> > > > 
> > > > > Hi Apache Ignite Developers,
> > > > > 
> > > > > 
> > > > > 
> > > > > We seem to be on the same page about 2.8 release, but we’ve started
> > 
> > new
> > > > > practice - minor releases, the first release was 2.7.5.
> > 
> > Unfortunately,
> > > > > there is a couple of issues still not fixed in that release, so I
> > 
> > would
> > > > > like to propose to prepare one more minor release for Apache Ignite.
> > > > > 
> > > > > 
> > > > > 
> > > > > I propose my candidacy to be release manager once again.
> > > > > 
> > > > > 
> > > > > 
> > > > > I could (of course with help from Peter Ivanov) do some additional
> > > 
> > > efforts
> > > > > to complete and improve process doc
> > > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > > > 
> > > > > 
> > > > > 
> > > > > I propose (most optimistic) dates for release stages:
> > > > > 
> > > > > Scope Freeze: August 12, 2019
> > > > > 
> > > > > Code Freeze: August 15, 2019
> > > > > 
> > > > > Voting Date: August 22, 2019
> > > > > 
> > > > > Release Date: August 27, 2019
> > > > > 
> > > > > 
> > > > > WDYT?
> > > > > 
> > > > > 
> > > > > If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up
> > > 
> > > in
> > > > > the TC Bot during the weekend.
> > > > > 
> > > > > 
> > > > > 
> > > > > Sincerely,
> > > > > 
> > > > > Dmitriy Pavlov
> > > > > 
> > > 
> > > 
> > > 
> > > --
> > > Best regards,
> > > Ivan Pavlukhin
> > > 


signature.asc
Description: This is a digitally signed message part

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

[Dmitriy Pavlov]

Hi Denis, sure, we can include. Just one point, a wider scope can move very
optimistic dates from the first letter little bit forward.

But since Apache communities are about solutions made without time bounds,
it is perfectly ok for me.

чт, 8 авг. 2019 г. в 22:46, Raymond Wilson :

> +1 for IGNITE-10451
>
> Thanks,
> Raymond.
>
> Sent from my iPhone
>
> > On 9/08/2019, at 5:40 AM, Dmitriy Pavlov  wrote:
> >
> > Hi Ivan, Ilya, Igniters,
> >
> >
> >
> > I would like this release would be as minimal as possible.
> >
> >
> >
> > According to dates proposed we could freeze scope at 12.08, 4 days is
> more
> > than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is
> > also ok for me if we decide to have more relaxed dates.
> >
> >
> >
> > For now, I suppose the following fixed should be cherry-picked:
> >
> > https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker)
> > GridDhtPartitionsFullMessage retains huge maps on heap in exchange
> history
> >
> >
> >
> > https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET:
> > Persistence does not work with custom affinity function
> >
> >
> >
> > https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug)
> Destroyed
> > cache that resurrected on an old offline node breaks PME
> >
> >
> >
> > But I will continue to research JIRA.
> >
> >
> >
> > Sincerely,
> >
> > Dmitriy Pavlov
> >
> >
> > чт, 8 авг. 2019 г. в 17:30, Павлухин Иван :
> >
> >>> What's the scope for this release?
> >>
> >> Same question.
> >>
> >> On the other hand an idea of 2.7.6 release attracts me because having
> >> a practice of doing frequent minor releases can help us to build
> >> reliable and predictable release rails.
> >>
> >> чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev  >:
> >>>
> >>> Hello!
> >>>
> >>> What's the scope for this release?
> >>>
> >>> Regards,
> >>> --
> >>> Ilya Kasnacheev
> >>>
> >>>
> >>> чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
> >>>
>  Hi Apache Ignite Developers,
> 
> 
> 
>  We seem to be on the same page about 2.8 release, but we’ve started
> new
>  practice - minor releases, the first release was 2.7.5. Unfortunately,
>  there is a couple of issues still not fixed in that release, so I
> would
>  like to propose to prepare one more minor release for Apache Ignite.
> 
> 
> 
>  I propose my candidacy to be release manager once again.
> 
> 
> 
>  I could (of course with help from Peter Ivanov) do some additional
> >> efforts
>  to complete and improve process doc
>  https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> 
> 
> 
>  I propose (most optimistic) dates for release stages:
> 
>  Scope Freeze: August 12, 2019
> 
>  Code Freeze: August 15, 2019
> 
>  Voting Date: August 22, 2019
> 
>  Release Date: August 27, 2019
> 
> 
>  WDYT?
> 
> 
>  If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up
> >> in
>  the TC Bot during the weekend.
> 
> 
> 
>  Sincerely,
> 
>  Dmitriy Pavlov
> 
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> Ivan Pavlukhin
> >>
>

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

[Raymond Wilson]

+1 for IGNITE-10451

Thanks,
Raymond.

Sent from my iPhone

> On 9/08/2019, at 5:40 AM, Dmitriy Pavlov  wrote:
>
> Hi Ivan, Ilya, Igniters,
>
>
>
> I would like this release would be as minimal as possible.
>
>
>
> According to dates proposed we could freeze scope at 12.08, 4 days is more
> than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is
> also ok for me if we decide to have more relaxed dates.
>
>
>
> For now, I suppose the following fixed should be cherry-picked:
>
> https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker)
> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
>
>
>
> https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET:
> Persistence does not work with custom affinity function
>
>
>
> https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug) Destroyed
> cache that resurrected on an old offline node breaks PME
>
>
>
> But I will continue to research JIRA.
>
>
>
> Sincerely,
>
> Dmitriy Pavlov
>
>
> чт, 8 авг. 2019 г. в 17:30, Павлухин Иван :
>
>>> What's the scope for this release?
>>
>> Same question.
>>
>> On the other hand an idea of 2.7.6 release attracts me because having
>> a practice of doing frequent minor releases can help us to build
>> reliable and predictable release rails.
>>
>> чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev :
>>>
>>> Hello!
>>>
>>> What's the scope for this release?
>>>
>>> Regards,
>>> --
>>> Ilya Kasnacheev
>>>
>>>
>>> чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
>>>
 Hi Apache Ignite Developers,



 We seem to be on the same page about 2.8 release, but we’ve started new
 practice - minor releases, the first release was 2.7.5. Unfortunately,
 there is a couple of issues still not fixed in that release, so I would
 like to propose to prepare one more minor release for Apache Ignite.



 I propose my candidacy to be release manager once again.



 I could (of course with help from Peter Ivanov) do some additional
>> efforts
 to complete and improve process doc
 https://cwiki.apache.org/confluence/display/IGNITE/Release+Process



 I propose (most optimistic) dates for release stages:

 Scope Freeze: August 12, 2019

 Code Freeze: August 15, 2019

 Voting Date: August 22, 2019

 Release Date: August 27, 2019


 WDYT?


 If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up
>> in
 the TC Bot during the weekend.



 Sincerely,

 Dmitriy Pavlov

>>
>>
>>
>> --
>> Best regards,
>> Ivan Pavlukhin
>>

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

[Denis Magda]

Dmitry,

Please add this BTree corruption fix to the scope:
https://issues.apache.org/jira/browse/IGNITE-11953

Plus, I would upgrade our Spark integration to version 2.4 as long as 2.3
goes with limitations reported by our users:
https://issues.apache.org/jira/browse/IGNITE-12054

Nickolay, could you check if that's a quick upgrade?

-
Denis


On Thu, Aug 8, 2019 at 10:40 AM Dmitriy Pavlov  wrote:

> Hi Ivan, Ilya, Igniters,
>
>
>
> I would like this release would be as minimal as possible.
>
>
>
> According to dates proposed we could freeze scope at 12.08, 4 days is more
> than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is
> also ok for me if we decide to have more relaxed dates.
>
>
>
> For now, I suppose the following fixed should be cherry-picked:
>
> https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker)
> GridDhtPartitionsFullMessage retains huge maps on heap in exchange history
>
>
>
> https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET:
> Persistence does not work with custom affinity function
>
>
>
> https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug) Destroyed
> cache that resurrected on an old offline node breaks PME
>
>
>
> But I will continue to research JIRA.
>
>
>
> Sincerely,
>
> Dmitriy Pavlov
>
>
> чт, 8 авг. 2019 г. в 17:30, Павлухин Иван :
>
> > > What's the scope for this release?
> >
> > Same question.
> >
> > On the other hand an idea of 2.7.6 release attracts me because having
> > a practice of doing frequent minor releases can help us to build
> > reliable and predictable release rails.
> >
> > чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev :
> > >
> > > Hello!
> > >
> > > What's the scope for this release?
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
> > >
> > > > Hi Apache Ignite Developers,
> > > >
> > > >
> > > >
> > > > We seem to be on the same page about 2.8 release, but we’ve started
> new
> > > > practice - minor releases, the first release was 2.7.5.
> Unfortunately,
> > > > there is a couple of issues still not fixed in that release, so I
> would
> > > > like to propose to prepare one more minor release for Apache Ignite.
> > > >
> > > >
> > > >
> > > > I propose my candidacy to be release manager once again.
> > > >
> > > >
> > > >
> > > > I could (of course with help from Peter Ivanov) do some additional
> > efforts
> > > > to complete and improve process doc
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > >
> > > >
> > > >
> > > > I propose (most optimistic) dates for release stages:
> > > >
> > > > Scope Freeze: August 12, 2019
> > > >
> > > > Code Freeze: August 15, 2019
> > > >
> > > > Voting Date: August 22, 2019
> > > >
> > > > Release Date: August 27, 2019
> > > >
> > > >
> > > > WDYT?
> > > >
> > > >
> > > > If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up
> > in
> > > > the TC Bot during the weekend.
> > > >
> > > >
> > > >
> > > > Sincerely,
> > > >
> > > > Dmitriy Pavlov
> > > >
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>

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

[Dmitriy Pavlov]

Hi Ivan, Ilya, Igniters,



I would like this release would be as minimal as possible.



According to dates proposed we could freeze scope at 12.08, 4 days is more
than enough to stand up and say, ‘Hey, I have an urgent fix’. But it is
also ok for me if we decide to have more relaxed dates.



For now, I suppose the following fixed should be cherry-picked:

https://issues.apache.org/jira/browse/IGNITE-11767 (Blocker)
GridDhtPartitionsFullMessage retains huge maps on heap in exchange history



https://issues.apache.org/jira/browse/IGNITE-10451 (Major Bug) .NET:
Persistence does not work with custom affinity function



https://issues.apache.org/jira/browse/IGNITE-9562 (Critical Bug) Destroyed
cache that resurrected on an old offline node breaks PME



But I will continue to research JIRA.



Sincerely,

Dmitriy Pavlov


чт, 8 авг. 2019 г. в 17:30, Павлухин Иван :

> > What's the scope for this release?
>
> Same question.
>
> On the other hand an idea of 2.7.6 release attracts me because having
> a practice of doing frequent minor releases can help us to build
> reliable and predictable release rails.
>
> чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev :
> >
> > Hello!
> >
> > What's the scope for this release?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
> >
> > > Hi Apache Ignite Developers,
> > >
> > >
> > >
> > > We seem to be on the same page about 2.8 release, but we’ve started new
> > > practice - minor releases, the first release was 2.7.5. Unfortunately,
> > > there is a couple of issues still not fixed in that release, so I would
> > > like to propose to prepare one more minor release for Apache Ignite.
> > >
> > >
> > >
> > > I propose my candidacy to be release manager once again.
> > >
> > >
> > >
> > > I could (of course with help from Peter Ivanov) do some additional
> efforts
> > > to complete and improve process doc
> > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >
> > >
> > >
> > > I propose (most optimistic) dates for release stages:
> > >
> > > Scope Freeze: August 12, 2019
> > >
> > > Code Freeze: August 15, 2019
> > >
> > > Voting Date: August 22, 2019
> > >
> > > Release Date: August 27, 2019
> > >
> > >
> > > WDYT?
> > >
> > >
> > > If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up
> in
> > > the TC Bot during the weekend.
> > >
> > >
> > >
> > > Sincerely,
> > >
> > > Dmitriy Pavlov
> > >
>
>
>
> --
> Best regards,
> Ivan Pavlukhin
>

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

[Павлухин Иван]

> What's the scope for this release?

Same question.

On the other hand an idea of 2.7.6 release attracts me because having
a practice of doing frequent minor releases can help us to build
reliable and predictable release rails.

чт, 8 авг. 2019 г. в 15:09, Ilya Kasnacheev :
>
> Hello!
>
> What's the scope for this release?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :
>
> > Hi Apache Ignite Developers,
> >
> >
> >
> > We seem to be on the same page about 2.8 release, but we’ve started new
> > practice - minor releases, the first release was 2.7.5. Unfortunately,
> > there is a couple of issues still not fixed in that release, so I would
> > like to propose to prepare one more minor release for Apache Ignite.
> >
> >
> >
> > I propose my candidacy to be release manager once again.
> >
> >
> >
> > I could (of course with help from Peter Ivanov) do some additional efforts
> > to complete and improve process doc
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >
> >
> >
> > I propose (most optimistic) dates for release stages:
> >
> > Scope Freeze: August 12, 2019
> >
> > Code Freeze: August 15, 2019
> >
> > Voting Date: August 22, 2019
> >
> > Release Date: August 27, 2019
> >
> >
> > WDYT?
> >
> >
> > If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up in
> > the TC Bot during the weekend.
> >
> >
> >
> > Sincerely,
> >
> > Dmitriy Pavlov
> >



-- 
Best regards,
Ivan Pavlukhin

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

[Ilya Kasnacheev]

Hello!

What's the scope for this release?

Regards,
-- 
Ilya Kasnacheev


чт, 8 авг. 2019 г. в 15:07, Dmitriy Pavlov :

> Hi Apache Ignite Developers,
>
>
>
> We seem to be on the same page about 2.8 release, but we’ve started new
> practice - minor releases, the first release was 2.7.5. Unfortunately,
> there is a couple of issues still not fixed in that release, so I would
> like to propose to prepare one more minor release for Apache Ignite.
>
>
>
> I propose my candidacy to be release manager once again.
>
>
>
> I could (of course with help from Peter Ivanov) do some additional efforts
> to complete and improve process doc
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>
>
>
> I propose (most optimistic) dates for release stages:
>
> Scope Freeze: August 12, 2019
>
> Code Freeze: August 15, 2019
>
> Voting Date: August 22, 2019
>
> Release Date: August 27, 2019
>
>
> WDYT?
>
>
> If nobody minds, I will create branch 2.7.6 based on 2.7.5 and set up in
> the TC Bot during the weekend.
>
>
>
> Sincerely,
>
> Dmitriy Pavlov
>