[VOTE] Apache Ignite 2.6.0 RC1

[agura]

Igniters,

We've uploaded a 2.6.0 release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/

Git tag name is 2.6.0-rc1.

This release includes the following changes:

Ignite:
* Fixed incorrect calculation of client affinity assignment with baseline.
* Fixed incorrect calculation of switch segment record in WAL.
* Fixed JVM crush during in-progress eviction and cache group stop.

REST:
* Fixed serialization of BinaryObjects to JSON.

Complete list of closed issues:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.6%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)

DEVNOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1

RELEASE NOTES
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1

Please start voting.

+1 - to accept Apache Ignite 2.6.0-RC1
0 - don't care either way
-1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)

This vote will go for 72 hours.

[dmagda]

+1 (binding)

--
Denis

On Tue, Jul 10, 2018 at 10:02 AM Andrey Gura <[hidden email]> wrote:

> Igniters,
>
> We've uploaded a 2.6.0 release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
>
> Git tag name is 2.6.0-rc1.
>
> This release includes the following changes:
>
> Ignite:
> * Fixed incorrect calculation of client affinity assignment with baseline.
> * Fixed incorrect calculation of switch segment record in WAL.
> * Fixed JVM crush during in-progress eviction and cache group stop.
>
> REST:
> * Fixed serialization of BinaryObjects to JSON.
>
> Complete list of closed issues:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%20fixVersion%20%3D%202.6%20AND%20(status%20%3D%20closed%20or%20status%20%3D%20resolved)
>
> DEVNOTES
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
>
> RELEASE NOTES
>
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
>
> Please start voting.
>
> +1 - to accept Apache Ignite 2.6.0-RC1
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
>
> This vote will go for 72 hours.
>

[dsetrakyan]

Not sure if this is worth a down vote, but the release notes seem like a
copy of 2.5 release. I think 2.6 should have its own release notes.

D.

On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]> wrote:

> Igniters,
>
> We've uploaded a 2.6.0 release candidate to
> https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
>
> Git tag name is 2.6.0-rc1.
>
> This release includes the following changes:
>
> Ignite:
> * Fixed incorrect calculation of client affinity assignment with baseline.
> * Fixed incorrect calculation of switch segment record in WAL.
> * Fixed JVM crush during in-progress eviction and cache group stop.
>
> REST:
> * Fixed serialization of BinaryObjects to JSON.
>
> Complete list of closed issues:
> <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%">https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> 20closed%20or%20status%20%3D%20resolved)
>
> DEVNOTES
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
>
> RELEASE NOTES
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
>
> Please start voting.
>
> +1 - to accept Apache Ignite 2.6.0-RC1
> 0 - don't care either way
> -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
>
> This vote will go for 72 hours.
>

[agura]

Dmitry,

It is emergency release so we have very short list of changes. You could
check it using provided links.


ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan <[hidden email]>:

> Not sure if this is worth a down vote, but the release notes seem like a
> copy of 2.5 release. I think 2.6 should have its own release notes.
>
> D.
>
> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]> wrote:
>
> > Igniters,
> >
> > We've uploaded a 2.6.0 release candidate to
> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
> >
> > Git tag name is 2.6.0-rc1.
> >
> > This release includes the following changes:
> >
> > Ignite:
> > * Fixed incorrect calculation of client affinity assignment with
> baseline.
> > * Fixed incorrect calculation of switch segment record in WAL.
> > * Fixed JVM crush during in-progress eviction and cache group stop.
> >
> > REST:
> > * Fixed serialization of BinaryObjects to JSON.
> >
> > Complete list of closed issues:
> > <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%">https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> > 20closed%20or%20status%20%3D%20resolved)
> >
> > DEVNOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> >
> > RELEASE NOTES
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> >
> > Please start voting.
> >
> > +1 - to accept Apache Ignite 2.6.0-RC1
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> >
> > This vote will go for 72 hours.
> >
>

[agura]

Sorry,

You could check it using provided links.



ср, 11 июл. 2018 г., 5:41 Andrey Gura <[hidden email]>:

> Dmitry,
>
> It is emergency release so we have very short list of changes. You could
> check it using provided links.
>
>
> ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan <[hidden email]>:
>
>> Not sure if this is worth a down vote, but the release notes seem like a
>> copy of 2.5 release. I think 2.6 should have its own release notes.
>>
>> D.
>>
>> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]> wrote:
>>
>> > Igniters,
>> >
>> > We've uploaded a 2.6.0 release candidate to
>> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
>> >
>> > Git tag name is 2.6.0-rc1.
>> >
>> > This release includes the following changes:
>> >
>> > Ignite:
>> > * Fixed incorrect calculation of client affinity assignment with
>> baseline.
>> > * Fixed incorrect calculation of switch segment record in WAL.
>> > * Fixed JVM crush during in-progress eviction and cache group stop.
>> >
>> > REST:
>> > * Fixed serialization of BinaryObjects to JSON.
>> >
>> > Complete list of closed issues:
>> >
>> <a href="https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%">https://issues.apache.org/jira/issues/?jql=project%20%3D%20IGNITE%20AND%
>> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
>> > 20closed%20or%20status%20%3D%20resolved)
>> >
>> > DEVNOTES
>> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
>> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
>> >
>> > RELEASE NOTES
>> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
>> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
>> >
>> > Please start voting.
>> >
>> > +1 - to accept Apache Ignite 2.6.0-RC1
>> > 0 - don't care either way
>> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
>> >
>> > This vote will go for 72 hours.
>> >
>>
>

[dsetrakyan]

Andrey, this is the link I have:
https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1

This list does not look short. It looks like a copy of 2.5.

D.

On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura <[hidden email]> wrote:

> Sorry,
>
> You could check it using provided links.
>
>
>
> ср, 11 июл. 2018 г., 5:41 Andrey Gura <[hidden email]>:
>
> > Dmitry,
> >
> > It is emergency release so we have very short list of changes. You could
> > check it using provided links.
> >
> >
> > ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan <[hidden email]>:
> >
> >> Not sure if this is worth a down vote, but the release notes seem like a
> >> copy of 2.5 release. I think 2.6 should have its own release notes.
> >>
> >> D.
> >>
> >> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]> wrote:
> >>
> >> > Igniters,
> >> >
> >> > We've uploaded a 2.6.0 release candidate to
> >> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
> >> >
> >> > Git tag name is 2.6.0-rc1.
> >> >
> >> > This release includes the following changes:
> >> >
> >> > Ignite:
> >> > * Fixed incorrect calculation of client affinity assignment with
> >> baseline.
> >> > * Fixed incorrect calculation of switch segment record in WAL.
> >> > * Fixed JVM crush during in-progress eviction and cache group stop.
> >> >
> >> > REST:
> >> > * Fixed serialization of BinaryObjects to JSON.
> >> >
> >> > Complete list of closed issues:
> >> >
> >> <a href="https://issues.apache.org/jira/issues/?jql=project%20%">https://issues.apache.org/jira/issues/?jql=project%20%
> 3D%20IGNITE%20AND%
> >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> >> > 20closed%20or%20status%20%3D%20resolved)
> >> >
> >> > DEVNOTES
> >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> >> >
> >> > RELEASE NOTES
> >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> >> >
> >> > Please start voting.
> >> >
> >> > +1 - to accept Apache Ignite 2.6.0-RC1
> >> > 0 - don't care either way
> >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> >> >
> >> > This vote will go for 72 hours.
> >> >
> >>
> >
>

[Ilya Suntsov]

Dmitry,

I see 2.6 changes above 2.5:

Apache Ignite Release Notes

> ===========================
> Apache Ignite In-Memory Data Fabric 2.6
> ---------------------------------------
> Ignite:
> * Fixed incorrect calculation of client affinity assignment with baseline.
> * Fixed incorrect calculation of switch segment record in WAL.
> * Fixed JVM crush during in-progress eviction and cache group stop.
> REST:
> * Fixed serialization of BinaryObjects to JSON.
>

Apache Ignite In-Memory Data Fabric 2.5

---------------------------------------


2018-07-11 9:54 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:

> Andrey, this is the link I have:
> https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
>
> This list does not look short. It looks like a copy of 2.5.
>
> D.
>
> On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura <[hidden email]> wrote:
>
> > Sorry,
> >
> > You could check it using provided links.
> >
> >
> >
> > ср, 11 июл. 2018 г., 5:41 Andrey Gura <[hidden email]>:
> >
> > > Dmitry,
> > >
> > > It is emergency release so we have very short list of changes. You
> could
> > > check it using provided links.
> > >
> > >
> > > ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan <[hidden email]>:
> > >
> > >> Not sure if this is worth a down vote, but the release notes seem
> like a
> > >> copy of 2.5 release. I think 2.6 should have its own release notes.
> > >>
> > >> D.
> > >>
> > >> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]>
> wrote:
> > >>
> > >> > Igniters,
> > >> >
> > >> > We've uploaded a 2.6.0 release candidate to
> > >> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
> > >> >
> > >> > Git tag name is 2.6.0-rc1.
> > >> >
> > >> > This release includes the following changes:
> > >> >
> > >> > Ignite:
> > >> > * Fixed incorrect calculation of client affinity assignment with
> > >> baseline.
> > >> > * Fixed incorrect calculation of switch segment record in WAL.
> > >> > * Fixed JVM crush during in-progress eviction and cache group stop.
> > >> >
> > >> > REST:
> > >> > * Fixed serialization of BinaryObjects to JSON.
> > >> >
> > >> > Complete list of closed issues:
> > >> >
> > >> <a href="https://issues.apache.org/jira/issues/?jql=project%20%">https://issues.apache.org/jira/issues/?jql=project%20%
> > 3D%20IGNITE%20AND%
> > >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> > >> > 20closed%20or%20status%20%3D%20resolved)
> > >> >
> > >> > DEVNOTES
> > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> > >> >
> > >> > RELEASE NOTES
> > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> > >> >
> > >> > Please start voting.
> > >> >
> > >> > +1 - to accept Apache Ignite 2.6.0-RC1
> > >> > 0 - don't care either way
> > >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> > >> >
> > >> > This vote will go for 72 hours.
> > >> >
> > >>
> > >
> >
>

--
Best Regards,
Ilya Suntsov
email: [hidden email]
*GridGain Systems*
www.gridgain.com

[dsetrakyan]

Got it. I did not see the section up top. No more questions.

On Wed, Jul 11, 2018 at 11:21 AM, Ilya Suntsov <[hidden email]>
wrote:

> Dmitry,
>
> I see 2.6 changes above 2.5:
>
> Apache Ignite Release Notes
> > ===========================
> > Apache Ignite In-Memory Data Fabric 2.6
> > ---------------------------------------
> > Ignite:
> > * Fixed incorrect calculation of client affinity assignment with
> baseline.
> > * Fixed incorrect calculation of switch segment record in WAL.
> > * Fixed JVM crush during in-progress eviction and cache group stop.
> > REST:
> > * Fixed serialization of BinaryObjects to JSON.
> >
>
>
> Apache Ignite In-Memory Data Fabric 2.5
>
> ---------------------------------------
>
>
> 2018-07-11 9:54 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
>
> > Andrey, this is the link I have:
> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> >
> > This list does not look short. It looks like a copy of 2.5.
> >
> > D.
> >
> > On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura <[hidden email]> wrote:
> >
> > > Sorry,
> > >
> > > You could check it using provided links.
> > >
> > >
> > >
> > > ср, 11 июл. 2018 г., 5:41 Andrey Gura <[hidden email]>:
> > >
> > > > Dmitry,
> > > >
> > > > It is emergency release so we have very short list of changes. You
> > could
> > > > check it using provided links.
> > > >
> > > >
> > > > ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan <[hidden email]>:
> > > >
> > > >> Not sure if this is worth a down vote, but the release notes seem
> > like a
> > > >> copy of 2.5 release. I think 2.6 should have its own release notes.
> > > >>
> > > >> D.
> > > >>
> > > >> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]>
> > wrote:
> > > >>
> > > >> > Igniters,
> > > >> >
> > > >> > We've uploaded a 2.6.0 release candidate to
> > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
> > > >> >
> > > >> > Git tag name is 2.6.0-rc1.
> > > >> >
> > > >> > This release includes the following changes:
> > > >> >
> > > >> > Ignite:
> > > >> > * Fixed incorrect calculation of client affinity assignment with
> > > >> baseline.
> > > >> > * Fixed incorrect calculation of switch segment record in WAL.
> > > >> > * Fixed JVM crush during in-progress eviction and cache group
> stop.
> > > >> >
> > > >> > REST:
> > > >> > * Fixed serialization of BinaryObjects to JSON.
> > > >> >
> > > >> > Complete list of closed issues:
> > > >> >
> > > >> <a href="https://issues.apache.org/jira/issues/?jql=project%20%">https://issues.apache.org/jira/issues/?jql=project%20%
> > > 3D%20IGNITE%20AND%
> > > >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> > > >> > 20closed%20or%20status%20%3D%20resolved)
> > > >> >
> > > >> > DEVNOTES
> > > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> > > >> >
> > > >> > RELEASE NOTES
> > > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> > > >> >
> > > >> > Please start voting.
> > > >> >
> > > >> > +1 - to accept Apache Ignite 2.6.0-RC1
> > > >> > 0 - don't care either way
> > > >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> > > >> >
> > > >> > This vote will go for 72 hours.
> > > >> >
> > > >>
> > > >
> > >
> >
>
>
>
> --
> Best Regards,
> Ilya Suntsov
> email: [hidden email]
> *GridGain Systems*
> www.gridgain.com
>

[Alexey Goncharuk]

+1

Checked src archive signature, verified build from source, started a node
with and without persistence.

ср, 11 июл. 2018 г. в 11:24, Dmitriy Setrakyan <[hidden email]>:

> Got it. I did not see the section up top. No more questions.
>
> On Wed, Jul 11, 2018 at 11:21 AM, Ilya Suntsov <[hidden email]>
> wrote:
>
> > Dmitry,
> >
> > I see 2.6 changes above 2.5:
> >
> > Apache Ignite Release Notes
> > > ===========================
> > > Apache Ignite In-Memory Data Fabric 2.6
> > > ---------------------------------------
> > > Ignite:
> > > * Fixed incorrect calculation of client affinity assignment with
> > baseline.
> > > * Fixed incorrect calculation of switch segment record in WAL.
> > > * Fixed JVM crush during in-progress eviction and cache group stop.
> > > REST:
> > > * Fixed serialization of BinaryObjects to JSON.
> > >
> >
> >
> > Apache Ignite In-Memory Data Fabric 2.5
> >
> > ---------------------------------------
> >
> >
> > 2018-07-11 9:54 GMT+03:00 Dmitriy Setrakyan <[hidden email]>:
> >
> > > Andrey, this is the link I have:
> > > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> > >
> > > This list does not look short. It looks like a copy of 2.5.
> > >
> > > D.
> > >
> > > On Wed, Jul 11, 2018 at 5:48 AM, Andrey Gura <[hidden email]> wrote:
> > >
> > > > Sorry,
> > > >
> > > > You could check it using provided links.
> > > >
> > > >
> > > >
> > > > ср, 11 июл. 2018 г., 5:41 Andrey Gura <[hidden email]>:
> > > >
> > > > > Dmitry,
> > > > >
> > > > > It is emergency release so we have very short list of changes. You
> > > could
> > > > > check it using provided links.
> > > > >
> > > > >
> > > > > ср, 11 июл. 2018 г., 3:01 Dmitriy Setrakyan <[hidden email]
> >:
> > > > >
> > > > >> Not sure if this is worth a down vote, but the release notes seem
> > > like a
> > > > >> copy of 2.5 release. I think 2.6 should have its own release
> notes.
> > > > >>
> > > > >> D.
> > > > >>
> > > > >> On Tue, Jul 10, 2018 at 8:02 PM, Andrey Gura <[hidden email]>
> > > wrote:
> > > > >>
> > > > >> > Igniters,
> > > > >> >
> > > > >> > We've uploaded a 2.6.0 release candidate to
> > > > >> > https://dist.apache.org/repos/dist/dev/ignite/2.6.0-rc1/
> > > > >> >
> > > > >> > Git tag name is 2.6.0-rc1.
> > > > >> >
> > > > >> > This release includes the following changes:
> > > > >> >
> > > > >> > Ignite:
> > > > >> > * Fixed incorrect calculation of client affinity assignment with
> > > > >> baseline.
> > > > >> > * Fixed incorrect calculation of switch segment record in WAL.
> > > > >> > * Fixed JVM crush during in-progress eviction and cache group
> > stop.
> > > > >> >
> > > > >> > REST:
> > > > >> > * Fixed serialization of BinaryObjects to JSON.
> > > > >> >
> > > > >> > Complete list of closed issues:
> > > > >> >
> > > > >> <a href="https://issues.apache.org/jira/issues/?jql=project%20%">https://issues.apache.org/jira/issues/?jql=project%20%
> > > > 3D%20IGNITE%20AND%
> > > > >> > 20fixVersion%20%3D%202.6%20AND%20(status%20%3D%
> > > > >> > 20closed%20or%20status%20%3D%20resolved)
> > > > >> >
> > > > >> > DEVNOTES
> > > > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > >> > plain;f=DEVNOTES.txt;hb=refs/tags/2.6.0-rc1
> > > > >> >
> > > > >> > RELEASE NOTES
> > > > >> > https://git-wip-us.apache.org/repos/asf?p=ignite.git;a=blob_
> > > > >> > plain;f=RELEASE_NOTES.txt;hb=refs/tags/2.6.0-rc1
> > > > >> >
> > > > >> > Please start voting.
> > > > >> >
> > > > >> > +1 - to accept Apache Ignite 2.6.0-RC1
> > > > >> > 0 - don't care either way
> > > > >> > -1 - DO NOT accept Apache Ignite 2.6.0-RC1 (explain why)
> > > > >> >
> > > > >> > This vote will go for 72 hours.
> > > > >> >
> > > > >>
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Ilya Suntsov
> > email: [hidden email]
> > *GridGain Systems*
> > www.gridgain.com
> >
>

[Alexey Kuznetsov]

+1 (binding)

Download sources:   OK
Build from sources: OK
Run ignite.bat:     OK

--
Alexey Kuznetsov

[Anton Vinogradov-2]

I do NOT see that API was checked [1] and automated check [2] performed

[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
[2]
https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__

ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <[hidden email]>:

> +1 (binding)
>
> Download sources:   OK
> Build from sources: OK
> Run ignite.bat:     OK
>
> --
> Alexey Kuznetsov
>

[Dmitriy Pavlov]

I thought these steps are to be run automatically within chain and no
manual steps are required.

Petr, please step in.

ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:

> I do NOT see that API was checked [1] and automated check [2] performed
>
> [1]
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> [2]
>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
>
> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <[hidden email]>:
>
> > +1 (binding)
> >
> > Download sources:   OK
> > Build from sources: OK
> > Run ignite.bat:     OK
> >
> > --
> > Alexey Kuznetsov
> >
>

[vveider]

Currently, I have no knowledge about this build types and theirs purpose.

I guess release engineer has to run them manually with ignite-2.6 branch or with 2.6.0-rc1 build result.
Should I do it?

> On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]> wrote:
>
> I thought these steps are to be run automatically within chain and no manual steps are required.
>
> Petr, please step in.
>
> ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email] <mailto:[hidden email]>>:
> I do NOT see that API was checked [1] and automated check [2] performed
>
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__ <https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__>
> [2]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__ <https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__>
>
> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <[hidden email] <mailto:[hidden email]>>:
>
> > +1 (binding)
> >
> > Download sources:   OK
> > Build from sources: OK
> > Run ignite.bat:     OK
> >
> > --
> > Alexey Kuznetsov
> >

[Dmitriy Pavlov]

No, I just wondering if it could be in chain. If manual run is requires I
guess we could document it somewhere, so everyone in community will be
aware what should be done.

ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:

> Currently, I have no knowledge about this build types and theirs purpose.
>
> I guess release engineer has to run them manually with ignite-2.6 branch
> or with 2.6.0-rc1 build result.
> Should I do it?
>
>
>
>
> On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]> wrote:
>
> I thought these steps are to be run automatically within chain and no
> manual steps are required.
>
> Petr, please step in.
>
> ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
>
>> I do NOT see that API was checked [1] and automated check [2] performed
>>
>> [1]
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
>> [2]
>>
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
>>
>> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <[hidden email]>:
>>
>> > +1 (binding)
>> >
>> > Download sources:   OK
>> > Build from sources: OK
>> > Run ignite.bat:     OK
>> >
>> > --
>> > Alexey Kuznetsov
>> >
>>
>
>

[Anton Vinogradov-2]

Automation possible, but it's hard to determine previous version
automatically (especially when you have 2.x and 3.x releasing concurrently)
for API check [1],
but RC check [1] can be chained.

[1]
https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
[2]
https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__

ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov <[hidden email]>:

> No, I just wondering if it could be in chain. If manual run is requires I
> guess we could document it somewhere, so everyone in community will be
> aware what should be done.
>
> ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:
>
> > Currently, I have no knowledge about this build types and theirs purpose.
> >
> > I guess release engineer has to run them manually with ignite-2.6 branch
> > or with 2.6.0-rc1 build result.
> > Should I do it?
> >
> >
> >
> >
> > On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]> wrote:
> >
> > I thought these steps are to be run automatically within chain and no
> > manual steps are required.
> >
> > Petr, please step in.
> >
> > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
> >
> >> I do NOT see that API was checked [1] and automated check [2] performed
> >>
> >> [1]
> >>
> >>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> >> [2]
> >>
> >>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> >>
> >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <[hidden email]>:
> >>
> >> > +1 (binding)
> >> >
> >> > Download sources:   OK
> >> > Build from sources: OK
> >> > Run ignite.bat:     OK
> >> >
> >> > --
> >> > Alexey Kuznetsov
> >> >
> >>
> >
> >
>

[Ilya Suntsov]

Anton,

Please take a look at:
https://ci.ignite.apache.org/viewLog.html?buildId=1478134&tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency
https://ci.ignite.apache.org/viewLog.html?buildId=1478557&tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum

Dmitry,

These steps should be outside the chain.

2018-07-11 14:49 GMT+03:00 Anton Vinogradov <[hidden email]>:

> Automation possible, but it's hard to determine previous version
> automatically (especially when you have 2.x and 3.x releasing concurrently)
> for API check [1],
> but RC check [1] can be chained.
>
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> [2]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
>
> ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov <[hidden email]>:
>
> > No, I just wondering if it could be in chain. If manual run is requires I
> > guess we could document it somewhere, so everyone in community will be
> > aware what should be done.
> >
> > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:
> >
> > > Currently, I have no knowledge about this build types and theirs
> purpose.
> > >
> > > I guess release engineer has to run them manually with ignite-2.6
> branch
> > > or with 2.6.0-rc1 build result.
> > > Should I do it?
> > >
> > >
> > >
> > >
> > > On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]> wrote:
> > >
> > > I thought these steps are to be run automatically within chain and no
> > > manual steps are required.
> > >
> > > Petr, please step in.
> > >
> > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
> > >
> > >> I do NOT see that API was checked [1] and automated check [2]
> performed
> > >>
> > >> [1]
> > >>
> > >>
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > >> [2]
> > >>
> > >>
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > >>
> > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <[hidden email]
> >:
> > >>
> > >> > +1 (binding)
> > >> >
> > >> > Download sources:   OK
> > >> > Build from sources: OK
> > >> > Run ignite.bat:     OK
> > >> >
> > >> > --
> > >> > Alexey Kuznetsov
> > >> >
> > >>
> > >
> > >
> >
>

--
Best Regards,
Ilya Suntsov
email: [hidden email]
*GridGain Systems*
www.gridgain.com

[Anton Vinogradov-2]

Ilya,

Please confirm that all changes [1] expected
[1]
https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/1478134:id/results/result.log

ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov <[hidden email]>:

> Anton,
>
> Please take a look at:
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1478134&tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1478557&tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum
>
> Dmitry,
>
> These steps should be outside the chain.
>
> 2018-07-11 14:49 GMT+03:00 Anton Vinogradov <[hidden email]>:
>
> > Automation possible, but it's hard to determine previous version
> > automatically (especially when you have 2.x and 3.x releasing
> concurrently)
> > for API check [1],
> > but RC check [1] can be chained.
> >
> > [1]
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > [2]
> > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> >
> > ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov <[hidden email]>:
> >
> > > No, I just wondering if it could be in chain. If manual run is
> requires I
> > > guess we could document it somewhere, so everyone in community will be
> > > aware what should be done.
> > >
> > > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:
> > >
> > > > Currently, I have no knowledge about this build types and theirs
> > purpose.
> > > >
> > > > I guess release engineer has to run them manually with ignite-2.6
> > branch
> > > > or with 2.6.0-rc1 build result.
> > > > Should I do it?
> > > >
> > > >
> > > >
> > > >
> > > > On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]>
> wrote:
> > > >
> > > > I thought these steps are to be run automatically within chain and no
> > > > manual steps are required.
> > > >
> > > > Petr, please step in.
> > > >
> > > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
> > > >
> > > >> I do NOT see that API was checked [1] and automated check [2]
> > performed
> > > >>
> > > >> [1]
> > > >>
> > > >>
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > >> [2]
> > > >>
> > > >>
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > >>
> > > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <
> [hidden email]
> > >:
> > > >>
> > > >> > +1 (binding)
> > > >> >
> > > >> > Download sources:   OK
> > > >> > Build from sources: OK
> > > >> > Run ignite.bat:     OK
> > > >> >
> > > >> > --
> > > >> > Alexey Kuznetsov
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
>
>
> --
> Best Regards,
> Ilya Suntsov
> email: [hidden email]
> *GridGain Systems*
> www.gridgain.com
>

[Ilya Suntsov]

Anton,

Module spark-2.10 and optional lib ignite-spark_2.10 were removed during
the work on IGNITE-8534 <https://issues.apache.org/jira/browse/IGNITE-8534>

IGNITE-8768 <https://issues.apache.org/jira/browse/IGNITE-8768>:

+ modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/EvictionContext.java

IGNITE-8804 <https://issues.apache.org/jira/browse/IGNITE-8804>:

+ config/wsl-default-config.xml

IGNITE-8685 <https://issues.apache.org/jira/browse/IGNITE-8685?src=confmacro>:

- modules/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java

- modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java


Other changes are tests that were added.


2018-07-11 16:28 GMT+03:00 Anton Vinogradov <[hidden email]>:

> Ilya,
>
> Please confirm that all changes [1] expected
> [1]
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
>
> ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov <[hidden email]>:
>
> > Anton,
> >
> > Please take a look at:
> >
> > https://ci.ignite.apache.org/viewLog.html?buildId=1478134&
> tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_
> IgniteRelease72CheckFileConsistency
> >
> > https://ci.ignite.apache.org/viewLog.html?buildId=1478557&
> tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_
> PrepareVote4CheckRcLicensesChecksum
> >
> > Dmitry,
> >
> > These steps should be outside the chain.
> >
> > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov <[hidden email]>:
> >
> > > Automation possible, but it's hard to determine previous version
> > > automatically (especially when you have 2.x and 3.x releasing
> > concurrently)
> > > for API check [1],
> > > but RC check [1] can be chained.
> > >
> > > [1]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > [2]
> > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > >
> > > ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov <[hidden email]>:
> > >
> > > > No, I just wondering if it could be in chain. If manual run is
> > requires I
> > > > guess we could document it somewhere, so everyone in community will
> be
> > > > aware what should be done.
> > > >
> > > > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:
> > > >
> > > > > Currently, I have no knowledge about this build types and theirs
> > > purpose.
> > > > >
> > > > > I guess release engineer has to run them manually with ignite-2.6
> > > branch
> > > > > or with 2.6.0-rc1 build result.
> > > > > Should I do it?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]>
> > wrote:
> > > > >
> > > > > I thought these steps are to be run automatically within chain and
> no
> > > > > manual steps are required.
> > > > >
> > > > > Petr, please step in.
> > > > >
> > > > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
> > > > >
> > > > >> I do NOT see that API was checked [1] and automated check [2]
> > > performed
> > > > >>
> > > > >> [1]
> > > > >>
> > > > >>
> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > >> [2]
> > > > >>
> > > > >>
> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > >>
> > > > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <
> > [hidden email]
> > > >:
> > > > >>
> > > > >> > +1 (binding)
> > > > >> >
> > > > >> > Download sources:   OK
> > > > >> > Build from sources: OK
> > > > >> > Run ignite.bat:     OK
> > > > >> >
> > > > >> > --
> > > > >> > Alexey Kuznetsov
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Ilya Suntsov
> > email: [hidden email]
> > *GridGain Systems*
> > www.gridgain.com
> >
>

--
Best Regards,
Ilya Suntsov
email: [hidden email]
*GridGain Systems*
www.gridgain.com

[Anton Vinogradov-2]

Ilya,

thanks for detailed explanation.

+1 now (binding).

Dmitry Pavlov,

could you please accumulate discussed and prepare documentation about "how
to release Apache Ignite step by step"?


ср, 11 июл. 2018 г. в 16:57, Ilya Suntsov <[hidden email]>:

> Anton,
>
> Module spark-2.10 and optional lib ignite-spark_2.10 were removed during
> the work on IGNITE-8534 <https://issues.apache.org/jira/browse/IGNITE-8534
> >
>
> IGNITE-8768 <https://issues.apache.org/jira/browse/IGNITE-8768>:
>
> +
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/EvictionContext.java
>
> IGNITE-8804 <https://issues.apache.org/jira/browse/IGNITE-8804>:
>
> + config/wsl-default-config.xml
>
> IGNITE-8685 <
> https://issues.apache.org/jira/browse/IGNITE-8685?src=confmacro>:
>
> -
> modules/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java
>
> -
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java
>
>
> Other changes are tests that were added.
>
>
> 2018-07-11 16:28 GMT+03:00 Anton Vinogradov <[hidden email]>:
>
> > Ilya,
> >
> > Please confirm that all changes [1] expected
> > [1]
> >
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> > IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
> >
> > ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov <[hidden email]>:
> >
> > > Anton,
> > >
> > > Please take a look at:
> > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1478134&
> > tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_
> > IgniteRelease72CheckFileConsistency
> > >
> > > https://ci.ignite.apache.org/viewLog.html?buildId=1478557&
> > tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_
> > PrepareVote4CheckRcLicensesChecksum
> > >
> > > Dmitry,
> > >
> > > These steps should be outside the chain.
> > >
> > > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov <[hidden email]>:
> > >
> > > > Automation possible, but it's hard to determine previous version
> > > > automatically (especially when you have 2.x and 3.x releasing
> > > concurrently)
> > > > for API check [1],
> > > > but RC check [1] can be chained.
> > > >
> > > > [1]
> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > [2]
> > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > >
> > > > ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov <[hidden email]>:
> > > >
> > > > > No, I just wondering if it could be in chain. If manual run is
> > > requires I
> > > > > guess we could document it somewhere, so everyone in community will
> > be
> > > > > aware what should be done.
> > > > >
> > > > > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:
> > > > >
> > > > > > Currently, I have no knowledge about this build types and theirs
> > > > purpose.
> > > > > >
> > > > > > I guess release engineer has to run them manually with ignite-2.6
> > > > branch
> > > > > > or with 2.6.0-rc1 build result.
> > > > > > Should I do it?
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]>
> > > wrote:
> > > > > >
> > > > > > I thought these steps are to be run automatically within chain
> and
> > no
> > > > > > manual steps are required.
> > > > > >
> > > > > > Petr, please step in.
> > > > > >
> > > > > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
> > > > > >
> > > > > >> I do NOT see that API was checked [1] and automated check [2]
> > > > performed
> > > > > >>
> > > > > >> [1]
> > > > > >>
> > > > > >>
> > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > > >> [2]
> > > > > >>
> > > > > >>
> > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > > > buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > > >>
> > > > > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <
> > > [hidden email]
> > > > >:
> > > > > >>
> > > > > >> > +1 (binding)
> > > > > >> >
> > > > > >> > Download sources:   OK
> > > > > >> > Build from sources: OK
> > > > > >> > Run ignite.bat:     OK
> > > > > >> >
> > > > > >> > --
> > > > > >> > Alexey Kuznetsov
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Best Regards,
> > > Ilya Suntsov
> > > email: [hidden email]
> > > *GridGain Systems*
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Best Regards,
> Ilya Suntsov
> email: [hidden email]
> *GridGain Systems*
> www.gridgain.com
>

[Dmitriy Pavlov]

Anton, I totally agree it is needed, but not sure I'll have free time to do
it soon. I will keep community posted.

ср, 11 июл. 2018 г. в 17:01, Anton Vinogradov <[hidden email]>:

> Ilya,
>
> thanks for detailed explanation.
>
> +1 now (binding).
>
> Dmitry Pavlov,
>
> could you please accumulate discussed and prepare documentation about "how
> to release Apache Ignite step by step"?
>
>
> ср, 11 июл. 2018 г. в 16:57, Ilya Suntsov <[hidden email]>:
>
> > Anton,
> >
> > Module spark-2.10 and optional lib ignite-spark_2.10 were removed during
> > the work on IGNITE-8534 <
> https://issues.apache.org/jira/browse/IGNITE-8534
> > >
> >
> > IGNITE-8768 <https://issues.apache.org/jira/browse/IGNITE-8768>:
> >
> > +
> >
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/distributed/dht/EvictionContext.java
> >
> > IGNITE-8804 <https://issues.apache.org/jira/browse/IGNITE-8804>:
> >
> > + config/wsl-default-config.xml
> >
> > IGNITE-8685 <
> > https://issues.apache.org/jira/browse/IGNITE-8685?src=confmacro>:
> >
> > -
> >
> modules/core/src/main/java/org/apache/ignite/internal/pagemem/wal/record/BaselineTopologyRecord.java
> >
> > -
> >
> modules/core/src/main/java/org/apache/ignite/internal/processors/cache/persistence/wal/serializer/BaselineTopologyRecordSerializer.java
> >
> >
> > Other changes are tests that were added.
> >
> >
> > 2018-07-11 16:28 GMT+03:00 Anton Vinogradov <[hidden email]>:
> >
> > > Ilya,
> > >
> > > Please confirm that all changes [1] expected
> > > [1]
> > >
> >
> https://ci.ignite.apache.org/repository/download/ApacheIgniteReleaseJava8_
> > > IgniteRelease72CheckFileConsistency/1478134:id/results/result.log
> > >
> > > ср, 11 июл. 2018 г. в 16:23, Ilya Suntsov <[hidden email]>:
> > >
> > > > Anton,
> > > >
> > > > Please take a look at:
> > > >
> > > > https://ci.ignite.apache.org/viewLog.html?buildId=1478134&
> > > tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_
> > > IgniteRelease72CheckFileConsistency
> > > >
> > > > https://ci.ignite.apache.org/viewLog.html?buildId=1478557&
> > > tab=buildResultsDiv&buildTypeId=ApacheIgniteReleaseJava8_
> > > PrepareVote4CheckRcLicensesChecksum
> > > >
> > > > Dmitry,
> > > >
> > > > These steps should be outside the chain.
> > > >
> > > > 2018-07-11 14:49 GMT+03:00 Anton Vinogradov <[hidden email]>:
> > > >
> > > > > Automation possible, but it's hard to determine previous version
> > > > > automatically (especially when you have 2.x and 3.x releasing
> > > > concurrently)
> > > > > for API check [1],
> > > > > but RC check [1] can be chained.
> > > > >
> > > > > [1]
> > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > > > >
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > > [2]
> > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > > > >
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > >
> > > > > ср, 11 июл. 2018 г. в 14:44, Dmitry Pavlov <[hidden email]
> >:
> > > > >
> > > > > > No, I just wondering if it could be in chain. If manual run is
> > > > requires I
> > > > > > guess we could document it somewhere, so everyone in community
> will
> > > be
> > > > > > aware what should be done.
> > > > > >
> > > > > > ср, 11 июл. 2018 г. в 14:41, Petr Ivanov <[hidden email]>:
> > > > > >
> > > > > > > Currently, I have no knowledge about this build types and
> theirs
> > > > > purpose.
> > > > > > >
> > > > > > > I guess release engineer has to run them manually with
> ignite-2.6
> > > > > branch
> > > > > > > or with 2.6.0-rc1 build result.
> > > > > > > Should I do it?
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 11 Jul 2018, at 14:36, Dmitry Pavlov <[hidden email]
> >
> > > > wrote:
> > > > > > >
> > > > > > > I thought these steps are to be run automatically within chain
> > and
> > > no
> > > > > > > manual steps are required.
> > > > > > >
> > > > > > > Petr, please step in.
> > > > > > >
> > > > > > > ср, 11 июл. 2018 г. в 14:30, Anton Vinogradov <[hidden email]>:
> > > > > > >
> > > > > > >> I do NOT see that API was checked [1] and automated check [2]
> > > > > performed
> > > > > > >>
> > > > > > >> [1]
> > > > > > >>
> > > > > > >>
> > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=
> > > > >
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > > > >> [2]
> > > > > > >>
> > > > > > >>
> > > > > > https://ci.ignite.apache.org/viewType.html?buildTypeId=
> > > > > ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=
> > > > >
> buildTypeHistoryList&branch_ApacheIgniteReleaseJava8=__all_branches__
> > > > > > >>
> > > > > > >> ср, 11 июл. 2018 г. в 14:25, Alexey Kuznetsov <
> > > > [hidden email]
> > > > > >:
> > > > > > >>
> > > > > > >> > +1 (binding)
> > > > > > >> >
> > > > > > >> > Download sources:   OK
> > > > > > >> > Build from sources: OK
> > > > > > >> > Run ignite.bat:     OK
> > > > > > >> >
> > > > > > >> > --
> > > > > > >> > Alexey Kuznetsov
> > > > > > >> >
> > > > > > >>
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Best Regards,
> > > > Ilya Suntsov
> > > > email: [hidden email]
> > > > *GridGain Systems*
> > > > www.gridgain.com
> > > >
> > >
> >
> >
> >
> > --
> > Best Regards,
> > Ilya Suntsov
> > email: [hidden email]
> > *GridGain Systems*
> > www.gridgain.com
> >
>