Apache Ignite 2.8 RELEASE [Time, Scope, Manager]

[Alexey Zinoviev]

All ML bugs are fixed, tested on TC and merged to 2.8 release branch.
Hope I'm not a blocker man now.



вт, 11 февр. 2020 г. в 17:23, Alexey Zinoviev <[hidden email]>:

> Hello, Igniters
>
> Stepan found and reported bug related to lambda
> serialization/deserialization
> https://issues.apache.org/jira/browse/IGNITE-12657
> The problem is the next: the ParamGrid object has a lambda in interface
> and this is an very bad for ML component, I've created a blocker bug
> https://issues.apache.org/jira/browse/IGNITE-12660
>
> Also as a result of good testing from both side (from me and Stepan) we
> found a lot of bugs and CVEs in hadoop related components that should be
> removed in release branch too.
>
> I'll notify then it will be finished
>
> Will work hardly on these bugs.
>
>
>
> вт, 11 февр. 2020 г. в 15:08, Ivan Bessonov <[hidden email]>:
>
>> Hello Igniters,
>>
>> I'd like to add one more fix to the release: [1]
>> It adds versioning to internal classes of distributed metastorage
>> component.
>> Without this fix it would be much harder to update these classes without
>> breaking binary compatibility.
>>
>> [1] https://issues.apache.org/jira/browse/IGNITE-12638
>>
>> ср, 5 февр. 2020 г. в 22:33, Maxim Muzafarov <[hidden email]>:
>>
>> > Ivan,
>> >
>> > > Should not we state in release notes what new experimental API was
>> added?
>> >
>> > I think we should. Will do.
>> > Just not to miss anything that we should mark with
>> > @IgniteExperimental: Consistency Check [1], Monitoring [2] anything
>> > else?
>> >
>> > > As Flink integration was moved to external repository how Ignite 2.8
>> > users will be able to use that integration?
>> >
>> > Since ignite-extension has a separate release cycle (right?), it is
>> > better to release ignite-extension rather than cherry-pick this change
>> > back to 2.8. I also think it is not a blocker for the release, but we
>> > should do our best make the first ignite-extension release as earlier
>> > as possible.
>> >
>> >
>> > [1] https://issues.apache.org/jira/browse/IGNITE-10663
>> > [2] https://issues.apache.org/jira/browse/IGNITE-11848
>> >
>> > On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <[hidden email]>
>> wrote:
>> > >
>> > > Maxim,
>> > >
>> > > A couple of questions:
>> > > 1. We added an annotation to designate experimental API. Should not we
>> > > state in release notes what new experimental API was added? Perhaps in
>> > > a separate block.
>> > > 2. As Flink integration was moved to external repository how Ignite
>> > > 2.8 users will be able to use that integration?
>> > >
>> > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <[hidden email]>:
>> > > >
>> > > > Igniters,
>> > > >
>> > > >
>> > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8 release.
>> > > >
>> > > > Currently, IEP-35 monitoring issues are not included in this PR.
>> Will
>> > > > do it soon.
>> > > > Please, take a look.
>> > > >
>> > > >
>> > > > [1] https://github.com/apache/ignite/pull/7367/files
>> > > >
>> > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <[hidden email]>
>> > wrote:
>> > > > >
>> > > > > Igniters,
>> > > > >
>> > > > >
>> > > > > Let me share the current status of the release.
>> > > > >
>> > > > > 1.
>> > > > > Waiting for the issues [1] [2] (discussed previously this thread)
>> to
>> > > > > be tested by TC.Bot and merged to the 2.8 release branch.
>> > > > >
>> > > > > 2.
>> > > > > Only 2 release BLOCKER issues left. I'm planning to move these
>> issues
>> > > > > to 2.8.1 release.
>> > > > > The issue [4] (Error during purges by expiration: Unknown page
>> type)
>> > > > > will be covered by [1] [2].
>> > > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based Discovery)
>> Nodes
>> > > > > getting down) probably require additional info to reproduce the
>> > issue.
>> > > > >
>> > > > > 3.
>> > > > > A potential performance drop on `putAll` operations on an
>> in-memory
>> > > > > cluster (see [5] for details).
>> > > > > I'll try to reproduce in another test environment.
>> > > > >
>> > > > >
>> > > > > Will keep you posted.
>> > > > >
>> > > > >
>> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
>> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
>> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
>> > > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
>> > > > > [5]
>> >
>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
>> > > > >
>> > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
>> > > > > <[hidden email]> wrote:
>> > > > > >
>> > > > > > Sounds good, will do!
>> > >
>> > >
>> > >
>> > > --
>> > > Best regards,
>> > > Ivan Pavlukhin
>> >
>>
>>
>> --
>> Sincerely yours,
>> Ivan Bessonov
>>
>

[dmagda]

Hi Maxim,

Do you have any understanding in regards to documentation readiness? I do
remember Nikolay was creating a page for the new metrics framework and
Artem stepped in as a reviewer. But not sure if that supposedly the largest
item is completed and if the other pages need to be updated.

-
Denis


On Tue, Feb 11, 2020 at 6:19 AM Maxim Muzafarov <[hidden email]> wrote:

> Igniters,
>
>
> Current the 2.8 release status
>
>
> 1. The PR with RELEASE_NOTES fully updated [1].
>
> 2. Previously mentioned performance drop has not been confirmed. Run
> many times in different environments. All test results within the
> margin of error.
> In-memory, putAll, 4 nodes, 1 client
> IgnitePutAllBenchmark: +1%
> IgnitePutAllTxBenchmark: -6%
>
> 3. Waiting for the vote completion
> (Allow or prohibit a joint use of @deprecated and @IgniteExperimental)
>
> 4. Mark MVCC with IgniteExperimental [2].
>
> 5. Wait for ML examples to be fixed [3].
>
> [1] https://github.com/apache/ignite/pull/7367/files
> [2]
> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
> [3] https://issues.apache.org/jira/browse/IGNITE-12657
>
> On Tue, 11 Feb 2020 at 15:08, Ivan Bessonov <[hidden email]> wrote:
> >
> > Hello Igniters,
> >
> > I'd like to add one more fix to the release: [1]
> > It adds versioning to internal classes of distributed metastorage
> component.
> > Without this fix it would be much harder to update these classes without
> > breaking binary compatibility.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12638
> >
> > ср, 5 февр. 2020 г. в 22:33, Maxim Muzafarov <[hidden email]>:
> >
> > > Ivan,
> > >
> > > > Should not we state in release notes what new experimental API was
> added?
> > >
> > > I think we should. Will do.
> > > Just not to miss anything that we should mark with
> > > @IgniteExperimental: Consistency Check [1], Monitoring [2] anything
> > > else?
> > >
> > > > As Flink integration was moved to external repository how Ignite 2.8
> > > users will be able to use that integration?
> > >
> > > Since ignite-extension has a separate release cycle (right?), it is
> > > better to release ignite-extension rather than cherry-pick this change
> > > back to 2.8. I also think it is not a blocker for the release, but we
> > > should do our best make the first ignite-extension release as earlier
> > > as possible.
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-10663
> > > [2] https://issues.apache.org/jira/browse/IGNITE-11848
> > >
> > > On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <[hidden email]>
> wrote:
> > > >
> > > > Maxim,
> > > >
> > > > A couple of questions:
> > > > 1. We added an annotation to designate experimental API. Should not
> we
> > > > state in release notes what new experimental API was added? Perhaps
> in
> > > > a separate block.
> > > > 2. As Flink integration was moved to external repository how Ignite
> > > > 2.8 users will be able to use that integration?
> > > >
> > > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <[hidden email]>:
> > > > >
> > > > > Igniters,
> > > > >
> > > > >
> > > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8 release.
> > > > >
> > > > > Currently, IEP-35 monitoring issues are not included in this PR.
> Will
> > > > > do it soon.
> > > > > Please, take a look.
> > > > >
> > > > >
> > > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > >
> > > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <[hidden email]>
> > > wrote:
> > > > > >
> > > > > > Igniters,
> > > > > >
> > > > > >
> > > > > > Let me share the current status of the release.
> > > > > >
> > > > > > 1.
> > > > > > Waiting for the issues [1] [2] (discussed previously this
> thread) to
> > > > > > be tested by TC.Bot and merged to the 2.8 release branch.
> > > > > >
> > > > > > 2.
> > > > > > Only 2 release BLOCKER issues left. I'm planning to move these
> issues
> > > > > > to 2.8.1 release.
> > > > > > The issue [4] (Error during purges by expiration: Unknown page
> type)
> > > > > > will be covered by [1] [2].
> > > > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based Discovery)
> Nodes
> > > > > > getting down) probably require additional info to reproduce the
> > > issue.
> > > > > >
> > > > > > 3.
> > > > > > A potential performance drop on `putAll` operations on an
> in-memory
> > > > > > cluster (see [5] for details).
> > > > > > I'll try to reproduce in another test environment.
> > > > > >
> > > > > >
> > > > > > Will keep you posted.
> > > > > >
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
> > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
> > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
> > > > > > [5]
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
> > > > > >
> > > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
> > > > > > <[hidden email]> wrote:
> > > > > > >
> > > > > > > Sounds good, will do!
> > > >
> > > >
> > > >
> > > > --
> > > > Best regards,
> > > > Ivan Pavlukhin
> > >
> >
> >
> > --
> > Sincerely yours,
> > Ivan Bessonov
>

[Maxim Muzafarov]

Denis,


We still need additional work over the whole documentation, not only
resolving comments for the new monitoring feature [2].
Here is the full list of issues related to documentation - [1].

Examples need to be extended too. For instance,
- suspend/resume for pessimistic transactions
- default Ignite work dir location (changed in 2.7.6 right?)
- baseline auto-adjustment feature


[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
[2] https://issues.apache.org/jira/browse/IGNITE-12408

On Thu, 13 Feb 2020 at 00:48, Denis Magda <[hidden email]> wrote:

>
> Hi Maxim,
>
> Do you have any understanding in regards to documentation readiness? I do
> remember Nikolay was creating a page for the new metrics framework and
> Artem stepped in as a reviewer. But not sure if that supposedly the largest
> item is completed and if the other pages need to be updated.
>
> -
> Denis
>
>
> On Tue, Feb 11, 2020 at 6:19 AM Maxim Muzafarov <[hidden email]> wrote:
>
> > Igniters,
> >
> >
> > Current the 2.8 release status
> >
> >
> > 1. The PR with RELEASE_NOTES fully updated [1].
> >
> > 2. Previously mentioned performance drop has not been confirmed. Run
> > many times in different environments. All test results within the
> > margin of error.
> > In-memory, putAll, 4 nodes, 1 client
> > IgnitePutAllBenchmark: +1%
> > IgnitePutAllTxBenchmark: -6%
> >
> > 3. Waiting for the vote completion
> > (Allow or prohibit a joint use of @deprecated and @IgniteExperimental)
> >
> > 4. Mark MVCC with IgniteExperimental [2].
> >
> > 5. Wait for ML examples to be fixed [3].
> >
> > [1] https://github.com/apache/ignite/pull/7367/files
> > [2]
> > http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
> > [3] https://issues.apache.org/jira/browse/IGNITE-12657
> >
> > On Tue, 11 Feb 2020 at 15:08, Ivan Bessonov <[hidden email]> wrote:
> > >
> > > Hello Igniters,
> > >
> > > I'd like to add one more fix to the release: [1]
> > > It adds versioning to internal classes of distributed metastorage
> > component.
> > > Without this fix it would be much harder to update these classes without
> > > breaking binary compatibility.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-12638
> > >
> > > ср, 5 февр. 2020 г. в 22:33, Maxim Muzafarov <[hidden email]>:
> > >
> > > > Ivan,
> > > >
> > > > > Should not we state in release notes what new experimental API was
> > added?
> > > >
> > > > I think we should. Will do.
> > > > Just not to miss anything that we should mark with
> > > > @IgniteExperimental: Consistency Check [1], Monitoring [2] anything
> > > > else?
> > > >
> > > > > As Flink integration was moved to external repository how Ignite 2.8
> > > > users will be able to use that integration?
> > > >
> > > > Since ignite-extension has a separate release cycle (right?), it is
> > > > better to release ignite-extension rather than cherry-pick this change
> > > > back to 2.8. I also think it is not a blocker for the release, but we
> > > > should do our best make the first ignite-extension release as earlier
> > > > as possible.
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-10663
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-11848
> > > >
> > > > On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <[hidden email]>
> > wrote:
> > > > >
> > > > > Maxim,
> > > > >
> > > > > A couple of questions:
> > > > > 1. We added an annotation to designate experimental API. Should not
> > we
> > > > > state in release notes what new experimental API was added? Perhaps
> > in
> > > > > a separate block.
> > > > > 2. As Flink integration was moved to external repository how Ignite
> > > > > 2.8 users will be able to use that integration?
> > > > >
> > > > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <[hidden email]>:
> > > > > >
> > > > > > Igniters,
> > > > > >
> > > > > >
> > > > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8 release.
> > > > > >
> > > > > > Currently, IEP-35 monitoring issues are not included in this PR.
> > Will
> > > > > > do it soon.
> > > > > > Please, take a look.
> > > > > >
> > > > > >
> > > > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > > >
> > > > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <[hidden email]>
> > > > wrote:
> > > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > >
> > > > > > > Let me share the current status of the release.
> > > > > > >
> > > > > > > 1.
> > > > > > > Waiting for the issues [1] [2] (discussed previously this
> > thread) to
> > > > > > > be tested by TC.Bot and merged to the 2.8 release branch.
> > > > > > >
> > > > > > > 2.
> > > > > > > Only 2 release BLOCKER issues left. I'm planning to move these
> > issues
> > > > > > > to 2.8.1 release.
> > > > > > > The issue [4] (Error during purges by expiration: Unknown page
> > type)
> > > > > > > will be covered by [1] [2].
> > > > > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based Discovery)
> > Nodes
> > > > > > > getting down) probably require additional info to reproduce the
> > > > issue.
> > > > > > >
> > > > > > > 3.
> > > > > > > A potential performance drop on `putAll` operations on an
> > in-memory
> > > > > > > cluster (see [5] for details).
> > > > > > > I'll try to reproduce in another test environment.
> > > > > > >
> > > > > > >
> > > > > > > Will keep you posted.
> > > > > > >
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
> > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
> > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
> > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
> > > > > > > [5]
> > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
> > > > > > >
> > > > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
> > > > > > > <[hidden email]> wrote:
> > > > > > > >
> > > > > > > > Sounds good, will do!
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Ivan Pavlukhin
> > > >
> > >
> > >
> > > --
> > > Sincerely yours,
> > > Ivan Bessonov
> >

[dmagda]

Maxim,

Thanks for the list. How many of those tickets relate to new capabilities
or changed behavior in 2.8? You can probably come up with such a sub-list.
This filter returns all the documentation tickets we have in JIRA, and,
indeed, many of them can be pushed to further releases.

-
Denis


On Thu, Feb 13, 2020 at 3:19 AM Maxim Muzafarov <[hidden email]> wrote:

> Denis,
>
>
> We still need additional work over the whole documentation, not only
> resolving comments for the new monitoring feature [2].
> Here is the full list of issues related to documentation - [1].
>
> Examples need to be extended too. For instance,
> - suspend/resume for pessimistic transactions
> - default Ignite work dir location (changed in 2.7.6 right?)
> - baseline auto-adjustment feature
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
> [2] https://issues.apache.org/jira/browse/IGNITE-12408
>
> On Thu, 13 Feb 2020 at 00:48, Denis Magda <[hidden email]> wrote:
> >
> > Hi Maxim,
> >
> > Do you have any understanding in regards to documentation readiness? I do
> > remember Nikolay was creating a page for the new metrics framework and
> > Artem stepped in as a reviewer. But not sure if that supposedly the
> largest
> > item is completed and if the other pages need to be updated.
> >
> > -
> > Denis
> >
> >
> > On Tue, Feb 11, 2020 at 6:19 AM Maxim Muzafarov <[hidden email]>
> wrote:
> >
> > > Igniters,
> > >
> > >
> > > Current the 2.8 release status
> > >
> > >
> > > 1. The PR with RELEASE_NOTES fully updated [1].
> > >
> > > 2. Previously mentioned performance drop has not been confirmed. Run
> > > many times in different environments. All test results within the
> > > margin of error.
> > > In-memory, putAll, 4 nodes, 1 client
> > > IgnitePutAllBenchmark: +1%
> > > IgnitePutAllTxBenchmark: -6%
> > >
> > > 3. Waiting for the vote completion
> > > (Allow or prohibit a joint use of @deprecated and @IgniteExperimental)
> > >
> > > 4. Mark MVCC with IgniteExperimental [2].
> > >
> > > 5. Wait for ML examples to be fixed [3].
> > >
> > > [1] https://github.com/apache/ignite/pull/7367/files
> > > [2]
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
> > > [3] https://issues.apache.org/jira/browse/IGNITE-12657
> > >
> > > On Tue, 11 Feb 2020 at 15:08, Ivan Bessonov <[hidden email]>
> wrote:
> > > >
> > > > Hello Igniters,
> > > >
> > > > I'd like to add one more fix to the release: [1]
> > > > It adds versioning to internal classes of distributed metastorage
> > > component.
> > > > Without this fix it would be much harder to update these classes
> without
> > > > breaking binary compatibility.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12638
> > > >
> > > > ср, 5 февр. 2020 г. в 22:33, Maxim Muzafarov <[hidden email]>:
> > > >
> > > > > Ivan,
> > > > >
> > > > > > Should not we state in release notes what new experimental API
> was
> > > added?
> > > > >
> > > > > I think we should. Will do.
> > > > > Just not to miss anything that we should mark with
> > > > > @IgniteExperimental: Consistency Check [1], Monitoring [2] anything
> > > > > else?
> > > > >
> > > > > > As Flink integration was moved to external repository how Ignite
> 2.8
> > > > > users will be able to use that integration?
> > > > >
> > > > > Since ignite-extension has a separate release cycle (right?), it is
> > > > > better to release ignite-extension rather than cherry-pick this
> change
> > > > > back to 2.8. I also think it is not a blocker for the release, but
> we
> > > > > should do our best make the first ignite-extension release as
> earlier
> > > > > as possible.
> > > > >
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-10663
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-11848
> > > > >
> > > > > On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <[hidden email]>
> > > wrote:
> > > > > >
> > > > > > Maxim,
> > > > > >
> > > > > > A couple of questions:
> > > > > > 1. We added an annotation to designate experimental API. Should
> not
> > > we
> > > > > > state in release notes what new experimental API was added?
> Perhaps
> > > in
> > > > > > a separate block.
> > > > > > 2. As Flink integration was moved to external repository how
> Ignite
> > > > > > 2.8 users will be able to use that integration?
> > > > > >
> > > > > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <[hidden email]
> >:
> > > > > > >
> > > > > > > Igniters,
> > > > > > >
> > > > > > >
> > > > > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8
> release.
> > > > > > >
> > > > > > > Currently, IEP-35 monitoring issues are not included in this
> PR.
> > > Will
> > > > > > > do it soon.
> > > > > > > Please, take a look.
> > > > > > >
> > > > > > >
> > > > > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > > > >
> > > > > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <
> [hidden email]>
> > > > > wrote:
> > > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > >
> > > > > > > > Let me share the current status of the release.
> > > > > > > >
> > > > > > > > 1.
> > > > > > > > Waiting for the issues [1] [2] (discussed previously this
> > > thread) to
> > > > > > > > be tested by TC.Bot and merged to the 2.8 release branch.
> > > > > > > >
> > > > > > > > 2.
> > > > > > > > Only 2 release BLOCKER issues left. I'm planning to move
> these
> > > issues
> > > > > > > > to 2.8.1 release.
> > > > > > > > The issue [4] (Error during purges by expiration: Unknown
> page
> > > type)
> > > > > > > > will be covered by [1] [2].
> > > > > > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based
> Discovery)
> > > Nodes
> > > > > > > > getting down) probably require additional info to reproduce
> the
> > > > > issue.
> > > > > > > >
> > > > > > > > 3.
> > > > > > > > A potential performance drop on `putAll` operations on an
> > > in-memory
> > > > > > > > cluster (see [5] for details).
> > > > > > > > I'll try to reproduce in another test environment.
> > > > > > > >
> > > > > > > >
> > > > > > > > Will keep you posted.
> > > > > > > >
> > > > > > > >
> > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
> > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
> > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
> > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
> > > > > > > > [5]
> > > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
> > > > > > > >
> > > > > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
> > > > > > > > <[hidden email]> wrote:
> > > > > > > > >
> > > > > > > > > Sounds good, will do!
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best regards,
> > > > > > Ivan Pavlukhin
> > > > >
> > > >
> > > >
> > > > --
> > > > Sincerely yours,
> > > > Ivan Bessonov
> > >
>

[Maxim Muzafarov]

Denis,

Actually, I've already filtered documentation issues previously and
left only major documentation tasks. Should I shrink the list more?

On Thu, 13 Feb 2020 at 18:58, Denis Magda <[hidden email]> wrote:

>
> Maxim,
>
> Thanks for the list. How many of those tickets relate to new capabilities
> or changed behavior in 2.8? You can probably come up with such a sub-list.
> This filter returns all the documentation tickets we have in JIRA, and,
> indeed, many of them can be pushed to further releases.
>
> -
> Denis
>
>
> On Thu, Feb 13, 2020 at 3:19 AM Maxim Muzafarov <[hidden email]> wrote:
>
> > Denis,
> >
> >
> > We still need additional work over the whole documentation, not only
> > resolving comments for the new monitoring feature [2].
> > Here is the full list of issues related to documentation - [1].
> >
> > Examples need to be extended too. For instance,
> > - suspend/resume for pessimistic transactions
> > - default Ignite work dir location (changed in 2.7.6 right?)
> > - baseline auto-adjustment feature
> >
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
> > [2] https://issues.apache.org/jira/browse/IGNITE-12408
> >
> > On Thu, 13 Feb 2020 at 00:48, Denis Magda <[hidden email]> wrote:
> > >
> > > Hi Maxim,
> > >
> > > Do you have any understanding in regards to documentation readiness? I do
> > > remember Nikolay was creating a page for the new metrics framework and
> > > Artem stepped in as a reviewer. But not sure if that supposedly the
> > largest
> > > item is completed and if the other pages need to be updated.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Tue, Feb 11, 2020 at 6:19 AM Maxim Muzafarov <[hidden email]>
> > wrote:
> > >
> > > > Igniters,
> > > >
> > > >
> > > > Current the 2.8 release status
> > > >
> > > >
> > > > 1. The PR with RELEASE_NOTES fully updated [1].
> > > >
> > > > 2. Previously mentioned performance drop has not been confirmed. Run
> > > > many times in different environments. All test results within the
> > > > margin of error.
> > > > In-memory, putAll, 4 nodes, 1 client
> > > > IgnitePutAllBenchmark: +1%
> > > > IgnitePutAllTxBenchmark: -6%
> > > >
> > > > 3. Waiting for the vote completion
> > > > (Allow or prohibit a joint use of @deprecated and @IgniteExperimental)
> > > >
> > > > 4. Mark MVCC with IgniteExperimental [2].
> > > >
> > > > 5. Wait for ML examples to be fixed [3].
> > > >
> > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > [2]
> > > >
> > http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
> > > > [3] https://issues.apache.org/jira/browse/IGNITE-12657
> > > >
> > > > On Tue, 11 Feb 2020 at 15:08, Ivan Bessonov <[hidden email]>
> > wrote:
> > > > >
> > > > > Hello Igniters,
> > > > >
> > > > > I'd like to add one more fix to the release: [1]
> > > > > It adds versioning to internal classes of distributed metastorage
> > > > component.
> > > > > Without this fix it would be much harder to update these classes
> > without
> > > > > breaking binary compatibility.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12638
> > > > >
> > > > > ср, 5 февр. 2020 г. в 22:33, Maxim Muzafarov <[hidden email]>:
> > > > >
> > > > > > Ivan,
> > > > > >
> > > > > > > Should not we state in release notes what new experimental API
> > was
> > > > added?
> > > > > >
> > > > > > I think we should. Will do.
> > > > > > Just not to miss anything that we should mark with
> > > > > > @IgniteExperimental: Consistency Check [1], Monitoring [2] anything
> > > > > > else?
> > > > > >
> > > > > > > As Flink integration was moved to external repository how Ignite
> > 2.8
> > > > > > users will be able to use that integration?
> > > > > >
> > > > > > Since ignite-extension has a separate release cycle (right?), it is
> > > > > > better to release ignite-extension rather than cherry-pick this
> > change
> > > > > > back to 2.8. I also think it is not a blocker for the release, but
> > we
> > > > > > should do our best make the first ignite-extension release as
> > earlier
> > > > > > as possible.
> > > > > >
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-10663
> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-11848
> > > > > >
> > > > > > On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <[hidden email]>
> > > > wrote:
> > > > > > >
> > > > > > > Maxim,
> > > > > > >
> > > > > > > A couple of questions:
> > > > > > > 1. We added an annotation to designate experimental API. Should
> > not
> > > > we
> > > > > > > state in release notes what new experimental API was added?
> > Perhaps
> > > > in
> > > > > > > a separate block.
> > > > > > > 2. As Flink integration was moved to external repository how
> > Ignite
> > > > > > > 2.8 users will be able to use that integration?
> > > > > > >
> > > > > > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <[hidden email]
> > >:
> > > > > > > >
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > >
> > > > > > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8
> > release.
> > > > > > > >
> > > > > > > > Currently, IEP-35 monitoring issues are not included in this
> > PR.
> > > > Will
> > > > > > > > do it soon.
> > > > > > > > Please, take a look.
> > > > > > > >
> > > > > > > >
> > > > > > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > > > > >
> > > > > > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <
> > [hidden email]>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Let me share the current status of the release.
> > > > > > > > >
> > > > > > > > > 1.
> > > > > > > > > Waiting for the issues [1] [2] (discussed previously this
> > > > thread) to
> > > > > > > > > be tested by TC.Bot and merged to the 2.8 release branch.
> > > > > > > > >
> > > > > > > > > 2.
> > > > > > > > > Only 2 release BLOCKER issues left. I'm planning to move
> > these
> > > > issues
> > > > > > > > > to 2.8.1 release.
> > > > > > > > > The issue [4] (Error during purges by expiration: Unknown
> > page
> > > > type)
> > > > > > > > > will be covered by [1] [2].
> > > > > > > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based
> > Discovery)
> > > > Nodes
> > > > > > > > > getting down) probably require additional info to reproduce
> > the
> > > > > > issue.
> > > > > > > > >
> > > > > > > > > 3.
> > > > > > > > > A potential performance drop on `putAll` operations on an
> > > > in-memory
> > > > > > > > > cluster (see [5] for details).
> > > > > > > > > I'll try to reproduce in another test environment.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Will keep you posted.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
> > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
> > > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
> > > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
> > > > > > > > > [5]
> > > > > >
> > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
> > > > > > > > >
> > > > > > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
> > > > > > > > > <[hidden email]> wrote:
> > > > > > > > > >
> > > > > > > > > > Sounds good, will do!
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Best regards,
> > > > > > > Ivan Pavlukhin
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sincerely yours,
> > > > > Ivan Bessonov
> > > >
> >

[dmagda]

Maxim,

There are some of the tasks that are being moved from a release to a
release or exist for a while and might be skipped for 2.8 if nobody is
willing to document them. A could of examples of such tickets:
https://issues.apache.org/jira/browse/IGNITE-10331
https://issues.apache.org/jira/browse/IGNITE-7704

How about preparing a list of the tickets that represent either a new
functionality added in 2.8 (new metrics, service grid improvements, etc.)
or change in behavior (it might be the case we need to update the baseline
topology or rebalancing pages)? Once we get the list, we'll find the names
of contributors and they will be able to cooperate with Artem who agreed to
assist with this effort.

The docs are needed before we announce the release and start bragging about
new capabilities.

-
Denis


On Thu, Feb 13, 2020 at 8:46 AM Maxim Muzafarov <[hidden email]> wrote:

> Denis,
>
> Actually, I've already filtered documentation issues previously and
> left only major documentation tasks. Should I shrink the list more?
>
> On Thu, 13 Feb 2020 at 18:58, Denis Magda <[hidden email]> wrote:
> >
> > Maxim,
> >
> > Thanks for the list. How many of those tickets relate to new capabilities
> > or changed behavior in 2.8? You can probably come up with such a
> sub-list.
> > This filter returns all the documentation tickets we have in JIRA, and,
> > indeed, many of them can be pushed to further releases.
> >
> > -
> > Denis
> >
> >
> > On Thu, Feb 13, 2020 at 3:19 AM Maxim Muzafarov <[hidden email]>
> wrote:
> >
> > > Denis,
> > >
> > >
> > > We still need additional work over the whole documentation, not only
> > > resolving comments for the new monitoring feature [2].
> > > Here is the full list of issues related to documentation - [1].
> > >
> > > Examples need to be extended too. For instance,
> > > - suspend/resume for pessimistic transactions
> > > - default Ignite work dir location (changed in 2.7.6 right?)
> > > - baseline auto-adjustment feature
> > >
> > >
> > > [1]
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Unresolveddocumentationtasks
> > > [2] https://issues.apache.org/jira/browse/IGNITE-12408
> > >
> > > On Thu, 13 Feb 2020 at 00:48, Denis Magda <[hidden email]> wrote:
> > > >
> > > > Hi Maxim,
> > > >
> > > > Do you have any understanding in regards to documentation readiness?
> I do
> > > > remember Nikolay was creating a page for the new metrics framework
> and
> > > > Artem stepped in as a reviewer. But not sure if that supposedly the
> > > largest
> > > > item is completed and if the other pages need to be updated.
> > > >
> > > > -
> > > > Denis
> > > >
> > > >
> > > > On Tue, Feb 11, 2020 at 6:19 AM Maxim Muzafarov <[hidden email]>
> > > wrote:
> > > >
> > > > > Igniters,
> > > > >
> > > > >
> > > > > Current the 2.8 release status
> > > > >
> > > > >
> > > > > 1. The PR with RELEASE_NOTES fully updated [1].
> > > > >
> > > > > 2. Previously mentioned performance drop has not been confirmed.
> Run
> > > > > many times in different environments. All test results within the
> > > > > margin of error.
> > > > > In-memory, putAll, 4 nodes, 1 client
> > > > > IgnitePutAllBenchmark: +1%
> > > > > IgnitePutAllTxBenchmark: -6%
> > > > >
> > > > > 3. Waiting for the vote completion
> > > > > (Allow or prohibit a joint use of @deprecated and
> @IgniteExperimental)
> > > > >
> > > > > 4. Mark MVCC with IgniteExperimental [2].
> > > > >
> > > > > 5. Wait for ML examples to be fixed [3].
> > > > >
> > > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > > [2]
> > > > >
> > >
> http://apache-ignite-developers.2346864.n4.nabble.com/Mark-MVCC-with-IgniteExperimental-td45669.html
> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12657
> > > > >
> > > > > On Tue, 11 Feb 2020 at 15:08, Ivan Bessonov <[hidden email]
> >
> > > wrote:
> > > > > >
> > > > > > Hello Igniters,
> > > > > >
> > > > > > I'd like to add one more fix to the release: [1]
> > > > > > It adds versioning to internal classes of distributed metastorage
> > > > > component.
> > > > > > Without this fix it would be much harder to update these classes
> > > without
> > > > > > breaking binary compatibility.
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12638
> > > > > >
> > > > > > ср, 5 февр. 2020 г. в 22:33, Maxim Muzafarov <[hidden email]
> >:
> > > > > >
> > > > > > > Ivan,
> > > > > > >
> > > > > > > > Should not we state in release notes what new experimental
> API
> > > was
> > > > > added?
> > > > > > >
> > > > > > > I think we should. Will do.
> > > > > > > Just not to miss anything that we should mark with
> > > > > > > @IgniteExperimental: Consistency Check [1], Monitoring [2]
> anything
> > > > > > > else?
> > > > > > >
> > > > > > > > As Flink integration was moved to external repository how
> Ignite
> > > 2.8
> > > > > > > users will be able to use that integration?
> > > > > > >
> > > > > > > Since ignite-extension has a separate release cycle (right?),
> it is
> > > > > > > better to release ignite-extension rather than cherry-pick this
> > > change
> > > > > > > back to 2.8. I also think it is not a blocker for the release,
> but
> > > we
> > > > > > > should do our best make the first ignite-extension release as
> > > earlier
> > > > > > > as possible.
> > > > > > >
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-10663
> > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-11848
> > > > > > >
> > > > > > > On Wed, 5 Feb 2020 at 22:07, Ivan Pavlukhin <
> [hidden email]>
> > > > > wrote:
> > > > > > > >
> > > > > > > > Maxim,
> > > > > > > >
> > > > > > > > A couple of questions:
> > > > > > > > 1. We added an annotation to designate experimental API.
> Should
> > > not
> > > > > we
> > > > > > > > state in release notes what new experimental API was added?
> > > Perhaps
> > > > > in
> > > > > > > > a separate block.
> > > > > > > > 2. As Flink integration was moved to external repository how
> > > Ignite
> > > > > > > > 2.8 users will be able to use that integration?
> > > > > > > >
> > > > > > > > ср, 5 февр. 2020 г. в 21:21, Maxim Muzafarov <
> [hidden email]
> > > >:
> > > > > > > > >
> > > > > > > > > Igniters,
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I've prepared RELEASE_NOTES pull-request [1] to the 2.8
> > > release.
> > > > > > > > >
> > > > > > > > > Currently, IEP-35 monitoring issues are not included in
> this
> > > PR.
> > > > > Will
> > > > > > > > > do it soon.
> > > > > > > > > Please, take a look.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > [1] https://github.com/apache/ignite/pull/7367/files
> > > > > > > > >
> > > > > > > > > On Mon, 3 Feb 2020 at 14:38, Maxim Muzafarov <
> > > [hidden email]>
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > Igniters,
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Let me share the current status of the release.
> > > > > > > > > >
> > > > > > > > > > 1.
> > > > > > > > > > Waiting for the issues [1] [2] (discussed previously this
> > > > > thread) to
> > > > > > > > > > be tested by TC.Bot and merged to the 2.8 release branch.
> > > > > > > > > >
> > > > > > > > > > 2.
> > > > > > > > > > Only 2 release BLOCKER issues left. I'm planning to move
> > > these
> > > > > issues
> > > > > > > > > > to 2.8.1 release.
> > > > > > > > > > The issue [4] (Error during purges by expiration: Unknown
> > > page
> > > > > type)
> > > > > > > > > > will be covered by [1] [2].
> > > > > > > > > > The issue [3] (Apache Ignite Cluster(Amazon S3 Based
> > > Discovery)
> > > > > Nodes
> > > > > > > > > > getting down) probably require additional info to
> reproduce
> > > the
> > > > > > > issue.
> > > > > > > > > >
> > > > > > > > > > 3.
> > > > > > > > > > A potential performance drop on `putAll` operations on an
> > > > > in-memory
> > > > > > > > > > cluster (see [5] for details).
> > > > > > > > > > I'll try to reproduce in another test environment.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Will keep you posted.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12593
> > > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-12594
> > > > > > > > > > [3] https://issues.apache.org/jira/browse/IGNITE-12398
> > > > > > > > > > [4] https://issues.apache.org/jira/browse/IGNITE-12489
> > > > > > > > > > [5]
> > > > > > >
> > > > >
> > >
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.8#ApacheIgnite2.8-Benchmarks(LATEST)
> > > > > > > > > >
> > > > > > > > > > On Thu, 30 Jan 2020 at 15:02, Alexey Goncharuk
> > > > > > > > > > <[hidden email]> wrote:
> > > > > > > > > > >
> > > > > > > > > > > Sounds good, will do!
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Best regards,
> > > > > > > > Ivan Pavlukhin
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sincerely yours,
> > > > > > Ivan Bessonov
> > > > >
> > >
>

[Alexey Goncharuk]

Folks,

I have merged IGNITE-12650 (mark MVCC as experimental) to master and
ignite-2.8. What's left? Should we remove deprecation from the old metrics
and start the vote?

[Maxim Muzafarov]

Alexey,


Yes. I will remove @deprecation according to the vote results and will
go further with the release steps [1] since there no blockers left.


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

On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
<[hidden email]> wrote:
>
> Folks,
>
> I have merged IGNITE-12650 (mark MVCC as experimental) to master and
> ignite-2.8. What's left? Should we remove deprecation from the old metrics
> and start the vote?

[Ilya Kasnacheev]

Hello!

I have just merged a fix for embarrassing issue where you could UPDATE
entries with Spring Data, but not "Update" or "update" them.

I suggest adding this fix to the scope of 2.8, since Spring Data is popular
and it does not in any way affect code outside of its modules.

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

WDYT?

Regards,
--
Ilya Kasnacheev


пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:

> Alexey,
>
>
> Yes. I will remove @deprecation according to the vote results and will
> go further with the release steps [1] since there no blockers left.
>
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>
> On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> <[hidden email]> wrote:
> >
> > Folks,
> >
> > I have merged IGNITE-12650 (mark MVCC as experimental) to master and
> > ignite-2.8. What's left? Should we remove deprecation from the old
> metrics
> > and start the vote?
>

[Maxim Muzafarov]

Igniters,


I've prepared the issue [1] and PR [2] with removing @deprecate
annotation on DataRegionMetrics and adding @IgniteExperimental to the
new metrics API.
Can anyone review my changes?


[1] https://issues.apache.org/jira/browse/IGNITE-12690
[2] https://github.com/apache/ignite/pull/7440

On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <[hidden email]> wrote:

>
> Hello!
>
> I have just merged a fix for embarrassing issue where you could UPDATE
> entries with Spring Data, but not "Update" or "update" them.
>
> I suggest adding this fix to the scope of 2.8, since Spring Data is popular
> and it does not in any way affect code outside of its modules.
>
> https://issues.apache.org/jira/browse/IGNITE-12672
>
> WDYT?
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:
>
> > Alexey,
> >
> >
> > Yes. I will remove @deprecation according to the vote results and will
> > go further with the release steps [1] since there no blockers left.
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >
> > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > <[hidden email]> wrote:
> > >
> > > Folks,
> > >
> > > I have merged IGNITE-12650 (mark MVCC as experimental) to master and
> > > ignite-2.8. What's left? Should we remove deprecation from the old
> > metrics
> > > and start the vote?
> >

[Maxim Muzafarov]

Ilya,


I think we must accept only blocker issues to the release branch.

My previous experience tells me that even a small change which seems
absolutely easy and clear can break everything. So, let's move this
issue [1] to the next release. Currently, it doesn't look like a
blocker.

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

On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]> wrote:

>
> Igniters,
>
>
> I've prepared the issue [1] and PR [2] with removing @deprecate
> annotation on DataRegionMetrics and adding @IgniteExperimental to the
> new metrics API.
> Can anyone review my changes?
>
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12690
> [2] https://github.com/apache/ignite/pull/7440
>
> On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <[hidden email]> wrote:
> >
> > Hello!
> >
> > I have just merged a fix for embarrassing issue where you could UPDATE
> > entries with Spring Data, but not "Update" or "update" them.
> >
> > I suggest adding this fix to the scope of 2.8, since Spring Data is popular
> > and it does not in any way affect code outside of its modules.
> >
> > https://issues.apache.org/jira/browse/IGNITE-12672
> >
> > WDYT?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:
> >
> > > Alexey,
> > >
> > >
> > > Yes. I will remove @deprecation according to the vote results and will
> > > go further with the release steps [1] since there no blockers left.
> > >
> > >
> > > [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >
> > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > > <[hidden email]> wrote:
> > > >
> > > > Folks,
> > > >
> > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master and
> > > > ignite-2.8. What's left? Should we remove deprecation from the old
> > > metrics
> > > > and start the vote?
> > >

[dmagda]

Folks,

Is there anything else apart from the open documentation tickets that
prevent us from starting the release vote? I think that it should take
around two weeks to run the release through the vote and announce it. The
top doc changes should be finished throughout that time already.

-
Denis


On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]> wrote:

> Ilya,
>
>
> I think we must accept only blocker issues to the release branch.
>
> My previous experience tells me that even a small change which seems
> absolutely easy and clear can break everything. So, let's move this
> issue [1] to the next release. Currently, it doesn't look like a
> blocker.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-12672
>
> On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]> wrote:
> >
> > Igniters,
> >
> >
> > I've prepared the issue [1] and PR [2] with removing @deprecate
> > annotation on DataRegionMetrics and adding @IgniteExperimental to the
> > new metrics API.
> > Can anyone review my changes?
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > [2] https://github.com/apache/ignite/pull/7440
> >
> > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <[hidden email]>
> wrote:
> > >
> > > Hello!
> > >
> > > I have just merged a fix for embarrassing issue where you could UPDATE
> > > entries with Spring Data, but not "Update" or "update" them.
> > >
> > > I suggest adding this fix to the scope of 2.8, since Spring Data is
> popular
> > > and it does not in any way affect code outside of its modules.
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-12672
> > >
> > > WDYT?
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:
> > >
> > > > Alexey,
> > > >
> > > >
> > > > Yes. I will remove @deprecation according to the vote results and
> will
> > > > go further with the release steps [1] since there no blockers left.
> > > >
> > > >
> > > > [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > >
> > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > > > <[hidden email]> wrote:
> > > > >
> > > > > Folks,
> > > > >
> > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master
> and
> > > > > ignite-2.8. What's left? Should we remove deprecation from the old
> > > > metrics
> > > > > and start the vote?
> > > >
>

[Maxim Muzafarov]

Denis,


Currently, we have no blockers. I'm preparing the build.

On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:

>
> Folks,
>
> Is there anything else apart from the open documentation tickets that
> prevent us from starting the release vote? I think that it should take
> around two weeks to run the release through the vote and announce it. The
> top doc changes should be finished throughout that time already.
>
> -
> Denis
>
>
> On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]> wrote:
>
> > Ilya,
> >
> >
> > I think we must accept only blocker issues to the release branch.
> >
> > My previous experience tells me that even a small change which seems
> > absolutely easy and clear can break everything. So, let's move this
> > issue [1] to the next release. Currently, it doesn't look like a
> > blocker.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-12672
> >
> > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]> wrote:
> > >
> > > Igniters,
> > >
> > >
> > > I've prepared the issue [1] and PR [2] with removing @deprecate
> > > annotation on DataRegionMetrics and adding @IgniteExperimental to the
> > > new metrics API.
> > > Can anyone review my changes?
> > >
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > > [2] https://github.com/apache/ignite/pull/7440
> > >
> > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <[hidden email]>
> > wrote:
> > > >
> > > > Hello!
> > > >
> > > > I have just merged a fix for embarrassing issue where you could UPDATE
> > > > entries with Spring Data, but not "Update" or "update" them.
> > > >
> > > > I suggest adding this fix to the scope of 2.8, since Spring Data is
> > popular
> > > > and it does not in any way affect code outside of its modules.
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > > >
> > > > WDYT?
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:
> > > >
> > > > > Alexey,
> > > > >
> > > > >
> > > > > Yes. I will remove @deprecation according to the vote results and
> > will
> > > > > go further with the release steps [1] since there no blockers left.
> > > > >
> > > > >
> > > > > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > > >
> > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > > > > <[hidden email]> wrote:
> > > > > >
> > > > > > Folks,
> > > > > >
> > > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master
> > and
> > > > > > ignite-2.8. What's left? Should we remove deprecation from the old
> > > > > metrics
> > > > > > and start the vote?
> > > > >
> >

[Maxim Muzafarov]

Pavel,


Can you assist me with preparing NuGet staging according to the
release steps [1]? I've double-checked everything related to the build
but suite [2] for preparing nuget package still fails (sorry for
running it multiple times).

I see some issues in the log which may be related to the file copy in
the build script which recently changed [4].
I'm still digging in, but anyway can you take a look and help?


Step 2:
Copy-Item : Cannot find path
'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
it does not exist.

Step 3:
Cannot find path
'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
because it does not exist.
At C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
char:47

pack: invalid arguments.


[1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
[2] https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
[3] https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
[4] https://issues.apache.org/jira/browse/IGNITE-12604

On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]> wrote:

>
> Denis,
>
>
> Currently, we have no blockers. I'm preparing the build.
>
> On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:
> >
> > Folks,
> >
> > Is there anything else apart from the open documentation tickets that
> > prevent us from starting the release vote? I think that it should take
> > around two weeks to run the release through the vote and announce it. The
> > top doc changes should be finished throughout that time already.
> >
> > -
> > Denis
> >
> >
> > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]> wrote:
> >
> > > Ilya,
> > >
> > >
> > > I think we must accept only blocker issues to the release branch.
> > >
> > > My previous experience tells me that even a small change which seems
> > > absolutely easy and clear can break everything. So, let's move this
> > > issue [1] to the next release. Currently, it doesn't look like a
> > > blocker.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
> > >
> > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]> wrote:
> > > >
> > > > Igniters,
> > > >
> > > >
> > > > I've prepared the issue [1] and PR [2] with removing @deprecate
> > > > annotation on DataRegionMetrics and adding @IgniteExperimental to the
> > > > new metrics API.
> > > > Can anyone review my changes?
> > > >
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > > > [2] https://github.com/apache/ignite/pull/7440
> > > >
> > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <[hidden email]>
> > > wrote:
> > > > >
> > > > > Hello!
> > > > >
> > > > > I have just merged a fix for embarrassing issue where you could UPDATE
> > > > > entries with Spring Data, but not "Update" or "update" them.
> > > > >
> > > > > I suggest adding this fix to the scope of 2.8, since Spring Data is
> > > popular
> > > > > and it does not in any way affect code outside of its modules.
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > > > >
> > > > > WDYT?
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:
> > > > >
> > > > > > Alexey,
> > > > > >
> > > > > >
> > > > > > Yes. I will remove @deprecation according to the vote results and
> > > will
> > > > > > go further with the release steps [1] since there no blockers left.
> > > > > >
> > > > > >
> > > > > > [1]
> > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > > > >
> > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > > > > > <[hidden email]> wrote:
> > > > > > >
> > > > > > > Folks,
> > > > > > >
> > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master
> > > and
> > > > > > > ignite-2.8. What's left? Should we remove deprecation from the old
> > > > > > metrics
> > > > > > > and start the vote?
> > > > > >
> > >

[Pavel Tupitsyn]

Maxim, I did a quick fix for the script, but it did not work.
Investigating further, will get back to you later today.

On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov <[hidden email]> wrote:

> Pavel,
>
>
> Can you assist me with preparing NuGet staging according to the
> release steps [1]? I've double-checked everything related to the build
> but suite [2] for preparing nuget package still fails (sorry for
> running it multiple times).
>
> I see some issues in the log which may be related to the file copy in
> the build script which recently changed [4].
> I'm still digging in, but anyway can you take a look and help?
>
>
> Step 2:
> Copy-Item : Cannot find path
>
> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
> it does not exist.
>
> Step 3:
> Cannot find path
>
> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
> because it does not exist.
> At
> C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
> char:47
>
> pack: invalid arguments.
>
>
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
> [2]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> [3]
> https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
> [4] https://issues.apache.org/jira/browse/IGNITE-12604
>
> On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]> wrote:
> >
> > Denis,
> >
> >
> > Currently, we have no blockers. I'm preparing the build.
> >
> > On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:
> > >
> > > Folks,
> > >
> > > Is there anything else apart from the open documentation tickets that
> > > prevent us from starting the release vote? I think that it should take
> > > around two weeks to run the release through the vote and announce it.
> The
> > > top doc changes should be finished throughout that time already.
> > >
> > > -
> > > Denis
> > >
> > >
> > > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]>
> wrote:
> > >
> > > > Ilya,
> > > >
> > > >
> > > > I think we must accept only blocker issues to the release branch.
> > > >
> > > > My previous experience tells me that even a small change which seems
> > > > absolutely easy and clear can break everything. So, let's move this
> > > > issue [1] to the next release. Currently, it doesn't look like a
> > > > blocker.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
> > > >
> > > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]>
> wrote:
> > > > >
> > > > > Igniters,
> > > > >
> > > > >
> > > > > I've prepared the issue [1] and PR [2] with removing @deprecate
> > > > > annotation on DataRegionMetrics and adding @IgniteExperimental to
> the
> > > > > new metrics API.
> > > > > Can anyone review my changes?
> > > > >
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > > > > [2] https://github.com/apache/ignite/pull/7440
> > > > >
> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> [hidden email]>
> > > > wrote:
> > > > > >
> > > > > > Hello!
> > > > > >
> > > > > > I have just merged a fix for embarrassing issue where you could
> UPDATE
> > > > > > entries with Spring Data, but not "Update" or "update" them.
> > > > > >
> > > > > > I suggest adding this fix to the scope of 2.8, since Spring Data
> is
> > > > popular
> > > > > > and it does not in any way affect code outside of its modules.
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > > > > >
> > > > > > WDYT?
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Ilya Kasnacheev
> > > > > >
> > > > > >
> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]
> >:
> > > > > >
> > > > > > > Alexey,
> > > > > > >
> > > > > > >
> > > > > > > Yes. I will remove @deprecation according to the vote results
> and
> > > > will
> > > > > > > go further with the release steps [1] since there no blockers
> left.
> > > > > > >
> > > > > > >
> > > > > > > [1]
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > > > > > >
> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > > > > > > <[hidden email]> wrote:
> > > > > > > >
> > > > > > > > Folks,
> > > > > > > >
> > > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to
> master
> > > > and
> > > > > > > > ignite-2.8. What's left? Should we remove deprecation from
> the old
> > > > > > > metrics
> > > > > > > > and start the vote?
> > > > > > >
> > > >
>

[Maxim Muzafarov]

Pavel,


Thank you for your help.
Please, let me know when I can proceed with a vote preparation.


Can you also provide some details - which exactly artefacts should I
check on staging resource after the [1] suite execution?

[1] https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages

On Wed, 26 Feb 2020 at 10:46, Pavel Tupitsyn <[hidden email]> wrote:

>
> Maxim, I did a quick fix for the script, but it did not work.
> Investigating further, will get back to you later today.
>
> On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov <[hidden email]> wrote:
>>
>> Pavel,
>>
>>
>> Can you assist me with preparing NuGet staging according to the
>> release steps [1]? I've double-checked everything related to the build
>> but suite [2] for preparing nuget package still fails (sorry for
>> running it multiple times).
>>
>> I see some issues in the log which may be related to the file copy in
>> the build script which recently changed [4].
>> I'm still digging in, but anyway can you take a look and help?
>>
>>
>> Step 2:
>> Copy-Item : Cannot find path
>> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
>> it does not exist.
>>
>> Step 3:
>> Cannot find path
>> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
>> because it does not exist.
>> At C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
>> char:47
>>
>> pack: invalid arguments.
>>
>>
>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
>> [2] https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
>> [3] https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
>> [4] https://issues.apache.org/jira/browse/IGNITE-12604
>>
>> On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]> wrote:
>> >
>> > Denis,
>> >
>> >
>> > Currently, we have no blockers. I'm preparing the build.
>> >
>> > On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:
>> > >
>> > > Folks,
>> > >
>> > > Is there anything else apart from the open documentation tickets that
>> > > prevent us from starting the release vote? I think that it should take
>> > > around two weeks to run the release through the vote and announce it. The
>> > > top doc changes should be finished throughout that time already.
>> > >
>> > > -
>> > > Denis
>> > >
>> > >
>> > > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]> wrote:
>> > >
>> > > > Ilya,
>> > > >
>> > > >
>> > > > I think we must accept only blocker issues to the release branch.
>> > > >
>> > > > My previous experience tells me that even a small change which seems
>> > > > absolutely easy and clear can break everything. So, let's move this
>> > > > issue [1] to the next release. Currently, it doesn't look like a
>> > > > blocker.
>> > > >
>> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
>> > > >
>> > > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]> wrote:
>> > > > >
>> > > > > Igniters,
>> > > > >
>> > > > >
>> > > > > I've prepared the issue [1] and PR [2] with removing @deprecate
>> > > > > annotation on DataRegionMetrics and adding @IgniteExperimental to the
>> > > > > new metrics API.
>> > > > > Can anyone review my changes?
>> > > > >
>> > > > >
>> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
>> > > > > [2] https://github.com/apache/ignite/pull/7440
>> > > > >
>> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <[hidden email]>
>> > > > wrote:
>> > > > > >
>> > > > > > Hello!
>> > > > > >
>> > > > > > I have just merged a fix for embarrassing issue where you could UPDATE
>> > > > > > entries with Spring Data, but not "Update" or "update" them.
>> > > > > >
>> > > > > > I suggest adding this fix to the scope of 2.8, since Spring Data is
>> > > > popular
>> > > > > > and it does not in any way affect code outside of its modules.
>> > > > > >
>> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
>> > > > > >
>> > > > > > WDYT?
>> > > > > >
>> > > > > > Regards,
>> > > > > > --
>> > > > > > Ilya Kasnacheev
>> > > > > >
>> > > > > >
>> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <[hidden email]>:
>> > > > > >
>> > > > > > > Alexey,
>> > > > > > >
>> > > > > > >
>> > > > > > > Yes. I will remove @deprecation according to the vote results and
>> > > > will
>> > > > > > > go further with the release steps [1] since there no blockers left.
>> > > > > > >
>> > > > > > >
>> > > > > > > [1]
>> > > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>> > > > > > >
>> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
>> > > > > > > <[hidden email]> wrote:
>> > > > > > > >
>> > > > > > > > Folks,
>> > > > > > > >
>> > > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to master
>> > > > and
>> > > > > > > > ignite-2.8. What's left? Should we remove deprecation from the old
>> > > > > > > metrics
>> > > > > > > > and start the vote?
>> > > > > > >
>> > > >

[Pavel Tupitsyn]

I'm running a final check in branch ignite-2.8-dotnet-build-fix, should be
done soon.
After that I'll merge the changes into ignite-2.8 (and backport to master),
and we can proceed.

I had to fix both TC project and the build script.
There were a few regressions introduced by various recent changes.

> Can you also provide some details - which exactly artefacts should I
check on staging resource after the [1] suite execution?
We are supposed to verify that NuGet packages are valid by installing them
and starting Ignite.
However, we added an automatic check recently: `Run NuGet verification
script` build step.
So the only thing to check is that new package appears on MyGet [1] (scroll
down to see versions and dates)

[1]
https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite


On Wed, Feb 26, 2020 at 7:42 PM Maxim Muzafarov <[hidden email]> wrote:

> Pavel,
>
>
> Thank you for your help.
> Please, let me know when I can proceed with a vote preparation.
>
>
> Can you also provide some details - which exactly artefacts should I
> check on staging resource after the [1] suite execution?
>
> [1]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
>
> On Wed, 26 Feb 2020 at 10:46, Pavel Tupitsyn <[hidden email]> wrote:
> >
> > Maxim, I did a quick fix for the script, but it did not work.
> > Investigating further, will get back to you later today.
> >
> > On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov <[hidden email]>
> wrote:
> >>
> >> Pavel,
> >>
> >>
> >> Can you assist me with preparing NuGet staging according to the
> >> release steps [1]? I've double-checked everything related to the build
> >> but suite [2] for preparing nuget package still fails (sorry for
> >> running it multiple times).
> >>
> >> I see some issues in the log which may be related to the file copy in
> >> the build script which recently changed [4].
> >> I'm still digging in, but anyway can you take a look and help?
> >>
> >>
> >> Step 2:
> >> Copy-Item : Cannot find path
> >>
> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
> >> it does not exist.
> >>
> >> Step 3:
> >> Cannot find path
> >>
> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
> >> because it does not exist.
> >> At
> C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
> >> char:47
> >>
> >> pack: invalid arguments.
> >>
> >>
> >> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
> >> [2]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> >> [3]
> https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
> >> [4] https://issues.apache.org/jira/browse/IGNITE-12604
> >>
> >> On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]>
> wrote:
> >> >
> >> > Denis,
> >> >
> >> >
> >> > Currently, we have no blockers. I'm preparing the build.
> >> >
> >> > On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:
> >> > >
> >> > > Folks,
> >> > >
> >> > > Is there anything else apart from the open documentation tickets
> that
> >> > > prevent us from starting the release vote? I think that it should
> take
> >> > > around two weeks to run the release through the vote and announce
> it. The
> >> > > top doc changes should be finished throughout that time already.
> >> > >
> >> > > -
> >> > > Denis
> >> > >
> >> > >
> >> > > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]>
> wrote:
> >> > >
> >> > > > Ilya,
> >> > > >
> >> > > >
> >> > > > I think we must accept only blocker issues to the release branch.
> >> > > >
> >> > > > My previous experience tells me that even a small change which
> seems
> >> > > > absolutely easy and clear can break everything. So, let's move
> this
> >> > > > issue [1] to the next release. Currently, it doesn't look like a
> >> > > > blocker.
> >> > > >
> >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
> >> > > >
> >> > > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]>
> wrote:
> >> > > > >
> >> > > > > Igniters,
> >> > > > >
> >> > > > >
> >> > > > > I've prepared the issue [1] and PR [2] with removing @deprecate
> >> > > > > annotation on DataRegionMetrics and adding @IgniteExperimental
> to the
> >> > > > > new metrics API.
> >> > > > > Can anyone review my changes?
> >> > > > >
> >> > > > >
> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> >> > > > > [2] https://github.com/apache/ignite/pull/7440
> >> > > > >
> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> [hidden email]>
> >> > > > wrote:
> >> > > > > >
> >> > > > > > Hello!
> >> > > > > >
> >> > > > > > I have just merged a fix for embarrassing issue where you
> could UPDATE
> >> > > > > > entries with Spring Data, but not "Update" or "update" them.
> >> > > > > >
> >> > > > > > I suggest adding this fix to the scope of 2.8, since Spring
> Data is
> >> > > > popular
> >> > > > > > and it does not in any way affect code outside of its modules.
> >> > > > > >
> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> >> > > > > >
> >> > > > > > WDYT?
> >> > > > > >
> >> > > > > > Regards,
> >> > > > > > --
> >> > > > > > Ilya Kasnacheev
> >> > > > > >
> >> > > > > >
> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
> [hidden email]>:
> >> > > > > >
> >> > > > > > > Alexey,
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > Yes. I will remove @deprecation according to the vote
> results and
> >> > > > will
> >> > > > > > > go further with the release steps [1] since there no
> blockers left.
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > [1]
> >> > > >
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >> > > > > > >
> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> >> > > > > > > <[hidden email]> wrote:
> >> > > > > > > >
> >> > > > > > > > Folks,
> >> > > > > > > >
> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental) to
> master
> >> > > > and
> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
> from the old
> >> > > > > > > metrics
> >> > > > > > > > and start the vote?
> >> > > > > > >
> >> > > >
>

[Pavel Tupitsyn]

Maxim,

Fixes are in ignite-2.8 now, and builds have passed [1].
I think we can proceed.

Thank you and sorry for the broken build.

[1]
https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/5083539?buildTab=overview

On Wed, Feb 26, 2020 at 8:46 PM Pavel Tupitsyn <[hidden email]> wrote:

> I'm running a final check in branch ignite-2.8-dotnet-build-fix, should be
> done soon.
> After that I'll merge the changes into ignite-2.8 (and backport to
> master), and we can proceed.
>
> I had to fix both TC project and the build script.
> There were a few regressions introduced by various recent changes.
>
> > Can you also provide some details - which exactly artefacts should I
> check on staging resource after the [1] suite execution?
> We are supposed to verify that NuGet packages are valid by installing them
> and starting Ignite.
> However, we added an automatic check recently: `Run NuGet verification
> script` build step.
> So the only thing to check is that new package appears on MyGet [1]
> (scroll down to see versions and dates)
>
> [1]
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
>
>
> On Wed, Feb 26, 2020 at 7:42 PM Maxim Muzafarov <[hidden email]> wrote:
>
>> Pavel,
>>
>>
>> Thank you for your help.
>> Please, let me know when I can proceed with a vote preparation.
>>
>>
>> Can you also provide some details - which exactly artefacts should I
>> check on staging resource after the [1] suite execution?
>>
>> [1]
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
>>
>> On Wed, 26 Feb 2020 at 10:46, Pavel Tupitsyn <[hidden email]>
>> wrote:
>> >
>> > Maxim, I did a quick fix for the script, but it did not work.
>> > Investigating further, will get back to you later today.
>> >
>> > On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov <[hidden email]>
>> wrote:
>> >>
>> >> Pavel,
>> >>
>> >>
>> >> Can you assist me with preparing NuGet staging according to the
>> >> release steps [1]? I've double-checked everything related to the build
>> >> but suite [2] for preparing nuget package still fails (sorry for
>> >> running it multiple times).
>> >>
>> >> I see some issues in the log which may be related to the file copy in
>> >> the build script which recently changed [4].
>> >> I'm still digging in, but anyway can you take a look and help?
>> >>
>> >>
>> >> Step 2:
>> >> Copy-Item : Cannot find path
>> >>
>> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
>> >> it does not exist.
>> >>
>> >> Step 3:
>> >> Cannot find path
>> >>
>> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
>> >> because it does not exist.
>> >> At
>> C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
>> >> char:47
>> >>
>> >> pack: invalid arguments.
>> >>
>> >>
>> >> [1]
>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
>> >> [2]
>> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
>> >> [3]
>> https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
>> >> [4] https://issues.apache.org/jira/browse/IGNITE-12604
>> >>
>> >> On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]>
>> wrote:
>> >> >
>> >> > Denis,
>> >> >
>> >> >
>> >> > Currently, we have no blockers. I'm preparing the build.
>> >> >
>> >> > On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:
>> >> > >
>> >> > > Folks,
>> >> > >
>> >> > > Is there anything else apart from the open documentation tickets
>> that
>> >> > > prevent us from starting the release vote? I think that it should
>> take
>> >> > > around two weeks to run the release through the vote and announce
>> it. The
>> >> > > top doc changes should be finished throughout that time already.
>> >> > >
>> >> > > -
>> >> > > Denis
>> >> > >
>> >> > >
>> >> > > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]>
>> wrote:
>> >> > >
>> >> > > > Ilya,
>> >> > > >
>> >> > > >
>> >> > > > I think we must accept only blocker issues to the release branch.
>> >> > > >
>> >> > > > My previous experience tells me that even a small change which
>> seems
>> >> > > > absolutely easy and clear can break everything. So, let's move
>> this
>> >> > > > issue [1] to the next release. Currently, it doesn't look like a
>> >> > > > blocker.
>> >> > > >
>> >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
>> >> > > >
>> >> > > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]>
>> wrote:
>> >> > > > >
>> >> > > > > Igniters,
>> >> > > > >
>> >> > > > >
>> >> > > > > I've prepared the issue [1] and PR [2] with removing @deprecate
>> >> > > > > annotation on DataRegionMetrics and adding @IgniteExperimental
>> to the
>> >> > > > > new metrics API.
>> >> > > > > Can anyone review my changes?
>> >> > > > >
>> >> > > > >
>> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
>> >> > > > > [2] https://github.com/apache/ignite/pull/7440
>> >> > > > >
>> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
>> [hidden email]>
>> >> > > > wrote:
>> >> > > > > >
>> >> > > > > > Hello!
>> >> > > > > >
>> >> > > > > > I have just merged a fix for embarrassing issue where you
>> could UPDATE
>> >> > > > > > entries with Spring Data, but not "Update" or "update" them.
>> >> > > > > >
>> >> > > > > > I suggest adding this fix to the scope of 2.8, since Spring
>> Data is
>> >> > > > popular
>> >> > > > > > and it does not in any way affect code outside of its
>> modules.
>> >> > > > > >
>> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
>> >> > > > > >
>> >> > > > > > WDYT?
>> >> > > > > >
>> >> > > > > > Regards,
>> >> > > > > > --
>> >> > > > > > Ilya Kasnacheev
>> >> > > > > >
>> >> > > > > >
>> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
>> [hidden email]>:
>> >> > > > > >
>> >> > > > > > > Alexey,
>> >> > > > > > >
>> >> > > > > > >
>> >> > > > > > > Yes. I will remove @deprecation according to the vote
>> results and
>> >> > > > will
>> >> > > > > > > go further with the release steps [1] since there no
>> blockers left.
>> >> > > > > > >
>> >> > > > > > >
>> >> > > > > > > [1]
>> >> > > >
>> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
>> >> > > > > > >
>> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
>> >> > > > > > > <[hidden email]> wrote:
>> >> > > > > > > >
>> >> > > > > > > > Folks,
>> >> > > > > > > >
>> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental)
>> to master
>> >> > > > and
>> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
>> from the old
>> >> > > > > > > metrics
>> >> > > > > > > > and start the vote?
>> >> > > > > > >
>> >> > > >
>>
>

[Maxim Muzafarov]

Igniters,


I've prepared everything to start a vote.
Are we ready to go on?


I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.8.0-rc1/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.0-rc1/

The following staging can be used for testing:
https://repository.apache.org/content/repositories/orgapacheignite-1474/

Tag with name 2.8.0-rc1 created:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=341b01dfd8abf2d9b01d468ad1bb26dfe84ac4f6


TC [Check RC: Licenses, compile, chksum]
https://ci.ignite.apache.org/viewLog.html?buildId=5085462&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildResultsDiv

TC [3] Build & Upload Nuget Staging Packages
https://ci.ignite.apache.org/viewLog.html?buildId=5085460&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv

TC [2] Compare w/ Previous Release
https://ci.ignite.apache.org/viewLog.html?buildId=5085458&buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildResultsDiv

On Wed, 26 Feb 2020 at 22:44, Pavel Tupitsyn <[hidden email]> wrote:

>
> Maxim,
>
> Fixes are in ignite-2.8 now, and builds have passed [1].
> I think we can proceed.
>
> Thank you and sorry for the broken build.
>
> [1]
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/5083539?buildTab=overview
>
> On Wed, Feb 26, 2020 at 8:46 PM Pavel Tupitsyn <[hidden email]> wrote:
>
> > I'm running a final check in branch ignite-2.8-dotnet-build-fix, should be
> > done soon.
> > After that I'll merge the changes into ignite-2.8 (and backport to
> > master), and we can proceed.
> >
> > I had to fix both TC project and the build script.
> > There were a few regressions introduced by various recent changes.
> >
> > > Can you also provide some details - which exactly artefacts should I
> > check on staging resource after the [1] suite execution?
> > We are supposed to verify that NuGet packages are valid by installing them
> > and starting Ignite.
> > However, we added an automatic check recently: `Run NuGet verification
> > script` build step.
> > So the only thing to check is that new package appears on MyGet [1]
> > (scroll down to see versions and dates)
> >
> > [1]
> > https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> >
> >
> > On Wed, Feb 26, 2020 at 7:42 PM Maxim Muzafarov <[hidden email]> wrote:
> >
> >> Pavel,
> >>
> >>
> >> Thank you for your help.
> >> Please, let me know when I can proceed with a vote preparation.
> >>
> >>
> >> Can you also provide some details - which exactly artefacts should I
> >> check on staging resource after the [1] suite execution?
> >>
> >> [1]
> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> >>
> >> On Wed, 26 Feb 2020 at 10:46, Pavel Tupitsyn <[hidden email]>
> >> wrote:
> >> >
> >> > Maxim, I did a quick fix for the script, but it did not work.
> >> > Investigating further, will get back to you later today.
> >> >
> >> > On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov <[hidden email]>
> >> wrote:
> >> >>
> >> >> Pavel,
> >> >>
> >> >>
> >> >> Can you assist me with preparing NuGet staging according to the
> >> >> release steps [1]? I've double-checked everything related to the build
> >> >> but suite [2] for preparing nuget package still fails (sorry for
> >> >> running it multiple times).
> >> >>
> >> >> I see some issues in the log which may be related to the file copy in
> >> >> the build script which recently changed [4].
> >> >> I'm still digging in, but anyway can you take a look and help?
> >> >>
> >> >>
> >> >> Step 2:
> >> >> Copy-Item : Cannot find path
> >> >>
> >> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
> >> >> it does not exist.
> >> >>
> >> >> Step 3:
> >> >> Cannot find path
> >> >>
> >> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
> >> >> because it does not exist.
> >> >> At
> >> C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
> >> >> char:47
> >> >>
> >> >> pack: invalid arguments.
> >> >>
> >> >>
> >> >> [1]
> >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
> >> >> [2]
> >> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> >> >> [3]
> >> https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
> >> >> [4] https://issues.apache.org/jira/browse/IGNITE-12604
> >> >>
> >> >> On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]>
> >> wrote:
> >> >> >
> >> >> > Denis,
> >> >> >
> >> >> >
> >> >> > Currently, we have no blockers. I'm preparing the build.
> >> >> >
> >> >> > On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]> wrote:
> >> >> > >
> >> >> > > Folks,
> >> >> > >
> >> >> > > Is there anything else apart from the open documentation tickets
> >> that
> >> >> > > prevent us from starting the release vote? I think that it should
> >> take
> >> >> > > around two weeks to run the release through the vote and announce
> >> it. The
> >> >> > > top doc changes should be finished throughout that time already.
> >> >> > >
> >> >> > > -
> >> >> > > Denis
> >> >> > >
> >> >> > >
> >> >> > > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <[hidden email]>
> >> wrote:
> >> >> > >
> >> >> > > > Ilya,
> >> >> > > >
> >> >> > > >
> >> >> > > > I think we must accept only blocker issues to the release branch.
> >> >> > > >
> >> >> > > > My previous experience tells me that even a small change which
> >> seems
> >> >> > > > absolutely easy and clear can break everything. So, let's move
> >> this
> >> >> > > > issue [1] to the next release. Currently, it doesn't look like a
> >> >> > > > blocker.
> >> >> > > >
> >> >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
> >> >> > > >
> >> >> > > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <[hidden email]>
> >> wrote:
> >> >> > > > >
> >> >> > > > > Igniters,
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > I've prepared the issue [1] and PR [2] with removing @deprecate
> >> >> > > > > annotation on DataRegionMetrics and adding @IgniteExperimental
> >> to the
> >> >> > > > > new metrics API.
> >> >> > > > > Can anyone review my changes?
> >> >> > > > >
> >> >> > > > >
> >> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> >> >> > > > > [2] https://github.com/apache/ignite/pull/7440
> >> >> > > > >
> >> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> >> [hidden email]>
> >> >> > > > wrote:
> >> >> > > > > >
> >> >> > > > > > Hello!
> >> >> > > > > >
> >> >> > > > > > I have just merged a fix for embarrassing issue where you
> >> could UPDATE
> >> >> > > > > > entries with Spring Data, but not "Update" or "update" them.
> >> >> > > > > >
> >> >> > > > > > I suggest adding this fix to the scope of 2.8, since Spring
> >> Data is
> >> >> > > > popular
> >> >> > > > > > and it does not in any way affect code outside of its
> >> modules.
> >> >> > > > > >
> >> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> >> >> > > > > >
> >> >> > > > > > WDYT?
> >> >> > > > > >
> >> >> > > > > > Regards,
> >> >> > > > > > --
> >> >> > > > > > Ilya Kasnacheev
> >> >> > > > > >
> >> >> > > > > >
> >> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
> >> [hidden email]>:
> >> >> > > > > >
> >> >> > > > > > > Alexey,
> >> >> > > > > > >
> >> >> > > > > > >
> >> >> > > > > > > Yes. I will remove @deprecation according to the vote
> >> results and
> >> >> > > > will
> >> >> > > > > > > go further with the release steps [1] since there no
> >> blockers left.
> >> >> > > > > > >
> >> >> > > > > > >
> >> >> > > > > > > [1]
> >> >> > > >
> >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> >> >> > > > > > >
> >> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> >> >> > > > > > > <[hidden email]> wrote:
> >> >> > > > > > > >
> >> >> > > > > > > > Folks,
> >> >> > > > > > > >
> >> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as experimental)
> >> to master
> >> >> > > > and
> >> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
> >> from the old
> >> >> > > > > > > metrics
> >> >> > > > > > > > and start the vote?
> >> >> > > > > > >
> >> >> > > >
> >>
> >

[antonovsergey93]

Hello, Maxim!

All your links to ci.ignite.apache.org/ return 404 http code. It's okay?

чт, 27 февр. 2020 г. в 19:06, Maxim Muzafarov <[hidden email]>:

> Igniters,
>
>
> I've prepared everything to start a vote.
> Are we ready to go on?
>
>
> I have uploaded a release candidate to:
> https://dist.apache.org/repos/dist/dev/ignite/2.8.0-rc1/
> https://dist.apache.org/repos/dist/dev/ignite/packages_2.8.0-rc1/
>
> The following staging can be used for testing:
> https://repository.apache.org/content/repositories/orgapacheignite-1474/
>
> Tag with name 2.8.0-rc1 created:
>
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=341b01dfd8abf2d9b01d468ad1bb26dfe84ac4f6
>
>
> TC [Check RC: Licenses, compile, chksum]
>
> https://ci.ignite.apache.org/viewLog.html?buildId=5085462&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum&tab=buildResultsDiv
>
> TC [3] Build & Upload Nuget Staging Packages
>
> https://ci.ignite.apache.org/viewLog.html?buildId=5085460&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildResultsDiv
>
> TC [2] Compare w/ Previous Release
>
> https://ci.ignite.apache.org/viewLog.html?buildId=5085458&buildTypeId=ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency&tab=buildResultsDiv
>
> On Wed, 26 Feb 2020 at 22:44, Pavel Tupitsyn <[hidden email]> wrote:
> >
> > Maxim,
> >
> > Fixes are in ignite-2.8 now, and builds have passed [1].
> > I think we can proceed.
> >
> > Thank you and sorry for the broken build.
> >
> > [1]
> >
> https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/5083539?buildTab=overview
> >
> > On Wed, Feb 26, 2020 at 8:46 PM Pavel Tupitsyn <[hidden email]>
> wrote:
> >
> > > I'm running a final check in branch ignite-2.8-dotnet-build-fix,
> should be
> > > done soon.
> > > After that I'll merge the changes into ignite-2.8 (and backport to
> > > master), and we can proceed.
> > >
> > > I had to fix both TC project and the build script.
> > > There were a few regressions introduced by various recent changes.
> > >
> > > > Can you also provide some details - which exactly artefacts should I
> > > check on staging resource after the [1] suite execution?
> > > We are supposed to verify that NuGet packages are valid by installing
> them
> > > and starting Ignite.
> > > However, we added an automatic check recently: `Run NuGet verification
> > > script` build step.
> > > So the only thing to check is that new package appears on MyGet [1]
> > > (scroll down to see versions and dates)
> > >
> > > [1]
> > >
> https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite
> > >
> > >
> > > On Wed, Feb 26, 2020 at 7:42 PM Maxim Muzafarov <[hidden email]>
> wrote:
> > >
> > >> Pavel,
> > >>
> > >>
> > >> Thank you for your help.
> > >> Please, let me know when I can proceed with a vote preparation.
> > >>
> > >>
> > >> Can you also provide some details - which exactly artefacts should I
> > >> check on staging resource after the [1] suite execution?
> > >>
> > >> [1]
> > >>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> > >>
> > >> On Wed, 26 Feb 2020 at 10:46, Pavel Tupitsyn <[hidden email]>
> > >> wrote:
> > >> >
> > >> > Maxim, I did a quick fix for the script, but it did not work.
> > >> > Investigating further, will get back to you later today.
> > >> >
> > >> > On Tue, Feb 25, 2020 at 10:10 PM Maxim Muzafarov <[hidden email]
> >
> > >> wrote:
> > >> >>
> > >> >> Pavel,
> > >> >>
> > >> >>
> > >> >> Can you assist me with preparing NuGet staging according to the
> > >> >> release steps [1]? I've double-checked everything related to the
> build
> > >> >> but suite [2] for preparing nuget package still fails (sorry for
> > >> >> running it multiple times).
> > >> >>
> > >> >> I see some issues in the log which may be related to the file copy
> in
> > >> >> the build script which recently changed [4].
> > >> >> I'm still digging in, but anyway can you take a look and help?
> > >> >>
> > >> >>
> > >> >> Step 2:
> > >> >> Copy-Item : Cannot find path
> > >> >>
> > >>
> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core.dll'because
> > >> >> it does not exist.
> > >> >>
> > >> >> Step 3:
> > >> >> Cannot find path
> > >> >>
> > >>
> 'C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\Apache.Ignite.Core\bin\Release\Apache.Ignite.Core.dll'
> > >> >> because it does not exist.
> > >> >> At
> > >>
> C:\BuildAgent\work\3722fcb3466a49e6\src\modules\platforms\dotnet\build.ps1:283
> > >> >> char:47
> > >> >>
> > >> >> pack: invalid arguments.
> > >> >>
> > >> >>
> > >> >> [1]
> > >>
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.4.2.PrepareNuGetstaging
> > >> >> [2]
> > >>
> https://ci.ignite.apache.org/viewType.html?buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages
> > >> >> [3]
> > >>
> https://ci.ignite.apache.org/viewLog.html?buildId=5080553&buildTypeId=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages&tab=buildLog
> > >> >> [4] https://issues.apache.org/jira/browse/IGNITE-12604
> > >> >>
> > >> >> On Fri, 21 Feb 2020 at 10:36, Maxim Muzafarov <[hidden email]>
> > >> wrote:
> > >> >> >
> > >> >> > Denis,
> > >> >> >
> > >> >> >
> > >> >> > Currently, we have no blockers. I'm preparing the build.
> > >> >> >
> > >> >> > On Thu, 20 Feb 2020 at 21:10, Denis Magda <[hidden email]>
> wrote:
> > >> >> > >
> > >> >> > > Folks,
> > >> >> > >
> > >> >> > > Is there anything else apart from the open documentation
> tickets
> > >> that
> > >> >> > > prevent us from starting the release vote? I think that it
> should
> > >> take
> > >> >> > > around two weeks to run the release through the vote and
> announce
> > >> it. The
> > >> >> > > top doc changes should be finished throughout that time
> already.
> > >> >> > >
> > >> >> > > -
> > >> >> > > Denis
> > >> >> > >
> > >> >> > >
> > >> >> > > On Wed, Feb 19, 2020 at 9:55 AM Maxim Muzafarov <
> [hidden email]>
> > >> wrote:
> > >> >> > >
> > >> >> > > > Ilya,
> > >> >> > > >
> > >> >> > > >
> > >> >> > > > I think we must accept only blocker issues to the release
> branch.
> > >> >> > > >
> > >> >> > > > My previous experience tells me that even a small change
> which
> > >> seems
> > >> >> > > > absolutely easy and clear can break everything. So, let's
> move
> > >> this
> > >> >> > > > issue [1] to the next release. Currently, it doesn't look
> like a
> > >> >> > > > blocker.
> > >> >> > > >
> > >> >> > > > [1] https://issues.apache.org/jira/browse/IGNITE-12672
> > >> >> > > >
> > >> >> > > > On Tue, 18 Feb 2020 at 13:51, Maxim Muzafarov <
> [hidden email]>
> > >> wrote:
> > >> >> > > > >
> > >> >> > > > > Igniters,
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > I've prepared the issue [1] and PR [2] with removing
> @deprecate
> > >> >> > > > > annotation on DataRegionMetrics and adding
> @IgniteExperimental
> > >> to the
> > >> >> > > > > new metrics API.
> > >> >> > > > > Can anyone review my changes?
> > >> >> > > > >
> > >> >> > > > >
> > >> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-12690
> > >> >> > > > > [2] https://github.com/apache/ignite/pull/7440
> > >> >> > > > >
> > >> >> > > > > On Tue, 18 Feb 2020 at 13:42, Ilya Kasnacheev <
> > >> [hidden email]>
> > >> >> > > > wrote:
> > >> >> > > > > >
> > >> >> > > > > > Hello!
> > >> >> > > > > >
> > >> >> > > > > > I have just merged a fix for embarrassing issue where you
> > >> could UPDATE
> > >> >> > > > > > entries with Spring Data, but not "Update" or "update"
> them.
> > >> >> > > > > >
> > >> >> > > > > > I suggest adding this fix to the scope of 2.8, since
> Spring
> > >> Data is
> > >> >> > > > popular
> > >> >> > > > > > and it does not in any way affect code outside of its
> > >> modules.
> > >> >> > > > > >
> > >> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-12672
> > >> >> > > > > >
> > >> >> > > > > > WDYT?
> > >> >> > > > > >
> > >> >> > > > > > Regards,
> > >> >> > > > > > --
> > >> >> > > > > > Ilya Kasnacheev
> > >> >> > > > > >
> > >> >> > > > > >
> > >> >> > > > > > пн, 17 февр. 2020 г. в 12:44, Maxim Muzafarov <
> > >> [hidden email]>:
> > >> >> > > > > >
> > >> >> > > > > > > Alexey,
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > Yes. I will remove @deprecation according to the vote
> > >> results and
> > >> >> > > > will
> > >> >> > > > > > > go further with the release steps [1] since there no
> > >> blockers left.
> > >> >> > > > > > >
> > >> >> > > > > > >
> > >> >> > > > > > > [1]
> > >> >> > > >
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
> > >> >> > > > > > >
> > >> >> > > > > > > On Mon, 17 Feb 2020 at 11:48, Alexey Goncharuk
> > >> >> > > > > > > <[hidden email]> wrote:
> > >> >> > > > > > > >
> > >> >> > > > > > > > Folks,
> > >> >> > > > > > > >
> > >> >> > > > > > > > I have merged IGNITE-12650 (mark MVCC as
> experimental)
> > >> to master
> > >> >> > > > and
> > >> >> > > > > > > > ignite-2.8. What's left? Should we remove deprecation
> > >> from the old
> > >> >> > > > > > > metrics
> > >> >> > > > > > > > and start the vote?
> > >> >> > > > > > >
> > >> >> > > >
> > >>
> > >
>

--
BR, Sergey Antonov