Re: [DISCUSSION] IEP-114: Custom Metrics

[Nikita Amelchev]

Vladimir, good job. LGTM.

Igniters, if there are no objections, I will merge the PR soon.

https://github.com/apache/ignite/pull/11223

ср, 31 янв. 2024 г. в 13:45, Anton Vinogradov :
>
> +1, LGTM
>
> On Tue, Jan 30, 2024 at 11:36 PM Nikita Amelchev 
> wrote:
>
> > Hello, Vladimir.
> >
> > Thanks for the IEP. I have reviewed the proposal, good plan. Let's
> > implement this.
> >
> > ср, 17 янв. 2024 г. в 18:48, Vladimir Steshin :
> > >
> > > Hi, Igniters! I'd like to propose a new feature - Custom Metrics. This
> > > would allow a user to register his own measurement and monitoring values.
> > > Short IEP description: 1. Custom metrics are convenient to gather
> > > different application metrics using the same client/platform/API. Or
> > > when the existing metrics have no values that user would like to get. 2.
> > > Custom metrics are just the New Metric System. We only expose the APIs.
> > > 3. Custom metrics can be registered, for example, with services, tasks,
> > > computations.
> > > 4. Names of user's own metrics are required to start with "custom.". 5.
> > > Custom metrics aren't stored.
> > > IEP-114 [1] has more details. Please share your thoughts. Thanks!
> > > [1]
> > >
> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-114+Custom+metrics
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >



-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSSION] IEP-114: Custom Metrics

[Nikita Amelchev]

Hello, Vladimir.

Thanks for the IEP. I have reviewed the proposal, good plan. Let's
implement this.

ср, 17 янв. 2024 г. в 18:48, Vladimir Steshin :
>
> Hi, Igniters! I'd like to propose a new feature - Custom Metrics. This
> would allow a user to register his own measurement and monitoring values.
> Short IEP description: 1. Custom metrics are convenient to gather
> different application metrics using the same client/platform/API. Or
> when the existing metrics have no values that user would like to get. 2.
> Custom metrics are just the New Metric System. We only expose the APIs.
> 3. Custom metrics can be registered, for example, with services, tasks,
> computations.
> 4. Names of user's own metrics are required to start with "custom.". 5.
> Custom metrics aren't stored.
> IEP-114 [1] has more details. Please share your thoughts. Thanks!
> [1]
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-114+Custom+metrics



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite ML Extension 1.0.0 RC1

[Nikita Amelchev]

+1 (binding)

Checked compilation, tests and some examples.

вт, 23 янв. 2024 г. в 16:57, Ivan Daschinsky :
>
> Sorry for my mistake, this vote will be open till Jan 26, 2024
>
> вт, 23 янв. 2024 г. в 16:27, Ivan Daschinsky :
>
> > Dear Community,
> > I am happy to start this voting thread.
> >
> > The release candidate have been uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-ml-ext-1.0.0-rc1/
> >
> > The staging maven repository is here:
> > https://repository.apache.org/content/repositories/orgapacheignite-1560
> >
> > The release notes are here:
> >
> > https://github.com/apache/ignite-extensions/blob/ignite-ml-ext-1.0.0-rc1/modules/ml-ext/ml/RELEASE_NOTES.txt
> >
> > The release checker results are here:
> > https://github.com/apache/ignite-extensions/actions/runs/7626105841
> >
> > The TC run is here:
> >
> > https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Ml/7716025?hideProblemsFromDependencies=false=false
> >
> >
> >
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept
> > 0 - don't care either way
> > -1 - DO NOT accept (explain why)
> >
> > See notes on how to verify release here
> > https://www.apache.org/info/verification.html
> > and
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >
> >
> > This vote will be open for at least 4 days till Fri Jan 26, 2022,
> > 17:00 UTC+3. Please, write me down the thread if you need
> > additional time to check the release.
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy



-- 
Best wishes,
Amelchev Nikita

[ANNOUNCE] Apache Ignite 2.16.0 Released

[Nikita Amelchev]

The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.16.0.

Apache Ignite® is an in-memory computing platform for transactional,
analytical, and streaming workloads delivering in-memory speeds at a
petabyte scale.
https://ignite.apache.org

The Apache Ignite community has made a lot of changes in the 2.16.0
release. This blog post will help you to know about some valuable
improvements:
https://ignite.apache.org/blog/apache-ignite-2-16-0.html

For the full list of changes, you can refer to the RELEASE_NOTES list
which is trying to catalogue the most significant improvements for
this version of the platform.
https://ignite.apache.org/releases/2.16.0/release_notes.html

Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi

Please let us know if you encounter any problems:
https://ignite.apache.org/our-community.html#faq

Regards,
Nikita Amelchev on behalf of the Apache Ignite community.

[RESULT] [VOTE] Release Apache Ignite 2.16.0 RC0

[Nikita Amelchev]

Dear community,

The release of Apache Ignite 2.16.0 RC0 has been accepted.

Vote result: The vote PASSES with six +1 votes (5 bindings),
no 0 votes,
and no -1 votes.

+1 votes:
- Pavel Tupitsyn (binding)
- Zhenya Stanilovsky
- Ivan Daschinsky (binding)
- Nikolay Izhikov (binding)
- Anton Vinogradov (binding)
- Maxim Muzafarov (binding)

Here is the link to the vote thread:
https://lists.apache.org/thread/y4yxhgn9z1pkjrjzvjcyzbqobdl814lr

The new release will be announced soon.


-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.16.0 RC0

[Nikita Amelchev]

Hello, Zhenya.

Java profiles should be activated automatically (on reload maven
project). Which JDK are you using? Is the project built from maven?

I can't reproduce on HotSpot 1.8.0_201-b09, OpenJDK 21+35-2513.

вт, 19 дек. 2023 г. в 11:16, Zhenya Stanilovsky :
>
>
> Hi, probably it`s a kind of problem from my side, but cloning by tag and 
> further steps:
> *  change profile to java-8
> *  Reload all maven Projects
> *  Try to run: ScriptTestSuite will raise guava dependency problem:
> /ignite/internal/processors/query/calcite/sql/IgniteSqlRollback.java:20:33
> java: package com.google.common.collect does not exist
> ---
> *  change profile to java-9
> *  reload
> *  the same problem :
> modules/core/src/test/java/org/apache/ignite/testframework/GridTestUtils.java:79:33
> java: package com.google.common.collect does not exist
>
> probably i need to clean all and try to rebuild from scratch .. for now it`s 
> not clear for me.
>
> >+1
> >
> >- Started the node from binaries
> >- Tested .NET examples
> >- Tested NuGet packages
> >
> >On Sun, Dec 17, 2023 at 2:48PM Nikita Amelchev < namelc...@apache.org >
> >wrote:
> >
> >> Dear Community,
> >>
> >> The release candidate is ready.
> >>
> >> I have uploaded release candidate to
> >>  https://dist.apache.org/repos/dist/dev/ignite/2.16.0-rc0
> >>  https://dist.apache.org/repos/dist/dev/ignite/packages_2.16.0-rc0
> >>
> >> The following staging can be used for testing:
> >>  https://repository.apache.org/content/repositories/orgapacheignite-1559
> >>
> >> Tag name is 2.16.0-rc0:
> >>  https://github.com/apache/ignite/releases/tag/2.16.0-rc0
> >>
> >> 2.16.0 most important changes:
> >> * Cache dumps;
> >> * Calcite engine: added hints, became more stable, covered with
> >> diagnostic tools;
> >> * Fixes to support JDK 14-21;
> >> * Cluster Management API (IEP-81);
> >> * Java thin client: Service Awareness feature;
> >> etc.
> >>
> >> RELEASE NOTES:
> >>
> >>  
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.16
> >>
> >> Complete list of resolved issues:
> >>
> >>  
> >> https://issues.apache.org/jira/browse/IGNITE-19650?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> >>
> >> DEVNOTES
> >>
> >>  
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.16
> >>
> >> The vote is formal, see voting guidelines
> >>  https://www.apache.org/foundation/voting.html
> >>
> >> +1 - to accept Apache Ignite 2.16.0-rc0
> >> 0 - don't care either way
> >> -1 - DO NOT accept Apache Ignite 2.16.0-rc0 (explain why)
> >>
> >> See notes on how to verify release here
> >>  https://www.apache.org/info/verification.html
> >> and
> >>
> >>  
> >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >>
> >> This vote will be open till Sun December 24, 2023, 15:00 UTC.
> >>
> >>  
> >> https://www.timeanddate.com/countdown/vote?iso=20231224T15=0=VOTE+on+the+Apache+Ignite+Release+2.16.0+RC0=sanserif
> >>
> >> --
> >> Best wishes,
> >> Amelchev Nikita
> >>
>
>
>
>



-- 
Best wishes,
Amelchev Nikita

[VOTE] Release Apache Ignite 2.16.0 RC0

[Nikita Amelchev]

Dear Community,

The release candidate is ready.

I have uploaded release candidate to
https://dist.apache.org/repos/dist/dev/ignite/2.16.0-rc0
https://dist.apache.org/repos/dist/dev/ignite/packages_2.16.0-rc0

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

Tag name is 2.16.0-rc0:
https://github.com/apache/ignite/releases/tag/2.16.0-rc0

2.16.0 most important changes:
* Cache dumps;
* Calcite engine: added hints, became more stable, covered with
diagnostic tools;
* Fixes to support JDK 14-21;
* Cluster Management API (IEP-81);
* Java thin client: Service Awareness feature;
etc.

RELEASE NOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.16

Complete list of resolved issues:
https://issues.apache.org/jira/browse/IGNITE-19650?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority

DEVNOTES
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.16

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

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

See notes on how to verify release here
https://www.apache.org/info/verification.html
and
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open till Sun December 24, 2023, 15:00 UTC.
https://www.timeanddate.com/countdown/vote?iso=20231224T15=0=VOTE+on+the+Apache+Ignite+Release+2.16.0+RC0=sanserif

-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Slava.

Yes, let's add it to the 2.16 scope.

чт, 7 дек. 2023 г. в 13:20, Вячеслав Коптилин :
>
> Hi Nikita,
>
> Is it possible to add the following ticket to the scope of the release as
> well?
> https://issues.apache.org/jira/browse/IGNITE-21032
> GitHub issue: https://github.com/apache/ignite/issues/11045
>
> Thanks,
> S.
>
> пн, 4 дек. 2023 г. в 21:13, Nikita Amelchev :
>
> > Hello, Igniters.
> >
> > I had a private conversation with Nikolay Izhikov and Maksim Timonin.
> > I propose to include the realtime CDC back into the 2.16 scope [1].
> > And also a couple of important tickets related to the cache dumps
> > [2-4].
> >
> > They need an extra week of time to merge it.
> >
> > Any objections?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-17700
> > [2] https://issues.apache.org/jira/browse/IGNITE-21013
> > [3] https://issues.apache.org/jira/browse/IGNITE-20890
> > [4] https://issues.apache.org/jira/browse/IGNITE-20614
> >
> > пн, 27 нояб. 2023 г. в 17:18, Nikita Amelchev :
> > >
> > > Hello, Igniters.
> > >
> > > The release branch has been stabilized. I'm waiting for load tests.
> > >
> > > The RC will be prepared in the coming days.
> > >
> > > пн, 20 нояб. 2023 г. в 22:28, Nikita Amelchev :
> > > >
> > > > Hello, Igniters.
> > > >
> > > > I'm announcing a code freeze for the 2.16 release. Only blockers are
> > > > accepted to the release since this moment.
> > > >
> > > > пн, 13 нояб. 2023 г. в 19:13, Nikita Amelchev :
> > > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > I suggest moving the code freeze date to +1 week.
> > > > >
> > > > > We have several bug fixes ready to be merged [1], for example:
> > > > >
> > > > > IGNITE-19239 Checkpoint read lock acquisition timeouts during
> > snapshot restore
> > > > > IGNITE-20816 In-memory server node is crashed by
> > > > > TcpIgniteClient.putAllConflict() if cache objects transformation
> > > > > applied
> > > > >
> > > > > Updated dates:
> > > > >
> > > > > Code Freeze: November 20, 2023
> > > > > Voting Date: November 27, 2023
> > > > > Release Date: December 4, 2023
> > > > >
> > > > > [1]
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> > > > >
> > > > > пн, 6 нояб. 2023 г. в 12:36, Nikita Amelchev :
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Yes, they are marked with the 2.16 fix version. According to the
> > > > > > release process they will be cherry-picked to the release branch if
> > > > > > merged before code freeze.
> > > > > >
> > > > > > Documentation issues can be cherry-picked regardless of these
> > dates.
> > > > > >
> > > > > > пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>:
> > > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Can the following PR be included in the scope of 2.16.0 version?
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-10268
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-18038
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-18572
> > > > > > >
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-19436
> > > > > > >
> > > > > > >
> > > > > > > 在 2023/11/6 16:21, Nikita Amelchev 写道:
> > > > > > > > Igniters,
> > > > > > > >
> > > > > > > > I have cut the release branch: 'ignite-2.16'. Please,
> > cherry-pick new
> > > > > > > > issues if needed.
> > > > > > > >
> > > > > > > > The 2.16 scope is frozen. Unresolved not-blocking issues will
> > be moved
>

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Igniters.

I had a private conversation with Nikolay Izhikov and Maksim Timonin.
I propose to include the realtime CDC back into the 2.16 scope [1].
And also a couple of important tickets related to the cache dumps
[2-4].

They need an extra week of time to merge it.

Any objections?

[1] https://issues.apache.org/jira/browse/IGNITE-17700
[2] https://issues.apache.org/jira/browse/IGNITE-21013
[3] https://issues.apache.org/jira/browse/IGNITE-20890
[4] https://issues.apache.org/jira/browse/IGNITE-20614

пн, 27 нояб. 2023 г. в 17:18, Nikita Amelchev :
>
> Hello, Igniters.
>
> The release branch has been stabilized. I'm waiting for load tests.
>
> The RC will be prepared in the coming days.
>
> пн, 20 нояб. 2023 г. в 22:28, Nikita Amelchev :
> >
> > Hello, Igniters.
> >
> > I'm announcing a code freeze for the 2.16 release. Only blockers are
> > accepted to the release since this moment.
> >
> > пн, 13 нояб. 2023 г. в 19:13, Nikita Amelchev :
> > >
> > > Hello, Igniters.
> > >
> > > I suggest moving the code freeze date to +1 week.
> > >
> > > We have several bug fixes ready to be merged [1], for example:
> > >
> > > IGNITE-19239 Checkpoint read lock acquisition timeouts during snapshot 
> > > restore
> > > IGNITE-20816 In-memory server node is crashed by
> > > TcpIgniteClient.putAllConflict() if cache objects transformation
> > > applied
> > >
> > > Updated dates:
> > >
> > > Code Freeze: November 20, 2023
> > > Voting Date: November 27, 2023
> > > Release Date: December 4, 2023
> > >
> > > [1] 
> > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> > >
> > > пн, 6 нояб. 2023 г. в 12:36, Nikita Amelchev :
> > > >
> > > > Hi,
> > > >
> > > > Yes, they are marked with the 2.16 fix version. According to the
> > > > release process they will be cherry-picked to the release branch if
> > > > merged before code freeze.
> > > >
> > > > Documentation issues can be cherry-picked regardless of these dates.
> > > >
> > > > пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>:
> > > > >
> > > > > Hi,
> > > > >
> > > > > Can the following PR be included in the scope of 2.16.0 version?
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-10268
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-18038
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-18572
> > > > >
> > > > > https://issues.apache.org/jira/browse/IGNITE-19436
> > > > >
> > > > >
> > > > > 在 2023/11/6 16:21, Nikita Amelchev 写道:
> > > > > > Igniters,
> > > > > >
> > > > > > I have cut the release branch: 'ignite-2.16'. Please, cherry-pick 
> > > > > > new
> > > > > > issues if needed.
> > > > > >
> > > > > > The 2.16 scope is frozen. Unresolved not-blocking issues will be 
> > > > > > moved
> > > > > > on the code freeze stage.
> > > > > >
> > > > > > Code freeze is planned for November 13, 2023. Please, feel free to
> > > > > > write if some issues are critical to be in the 2.16.
> > > > > >
> > > > > > ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev:
> > > > > >> Hello Igniters,
> > > > > >>
> > > > > >> I have created the 2.16 release page [1].
> > > > > >>
> > > > > >> Also, I propose to cut the release branch on the scope freeze day
> > > > > >> (November 6, 2023).
> > > > > >>
> > > > > >> [1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16
> > > > > >>
> > > > > >> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov:
> > > > > >>> +1, fully support Nikita to be RM
> > > > > >>>
> > > > > >>>
> > > > > >>> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn:
> > &g

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Igniters.

The release branch has been stabilized. I'm waiting for load tests.

The RC will be prepared in the coming days.

пн, 20 нояб. 2023 г. в 22:28, Nikita Amelchev :
>
> Hello, Igniters.
>
> I'm announcing a code freeze for the 2.16 release. Only blockers are
> accepted to the release since this moment.
>
> пн, 13 нояб. 2023 г. в 19:13, Nikita Amelchev :
> >
> > Hello, Igniters.
> >
> > I suggest moving the code freeze date to +1 week.
> >
> > We have several bug fixes ready to be merged [1], for example:
> >
> > IGNITE-19239 Checkpoint read lock acquisition timeouts during snapshot 
> > restore
> > IGNITE-20816 In-memory server node is crashed by
> > TcpIgniteClient.putAllConflict() if cache objects transformation
> > applied
> >
> > Updated dates:
> >
> > Code Freeze: November 20, 2023
> > Voting Date: November 27, 2023
> > Release Date: December 4, 2023
> >
> > [1] 
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> >
> > пн, 6 нояб. 2023 г. в 12:36, Nikita Amelchev :
> > >
> > > Hi,
> > >
> > > Yes, they are marked with the 2.16 fix version. According to the
> > > release process they will be cherry-picked to the release branch if
> > > merged before code freeze.
> > >
> > > Documentation issues can be cherry-picked regardless of these dates.
> > >
> > > пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>:
> > > >
> > > > Hi,
> > > >
> > > > Can the following PR be included in the scope of 2.16.0 version?
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-10268
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-18038
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-18572
> > > >
> > > > https://issues.apache.org/jira/browse/IGNITE-19436
> > > >
> > > >
> > > > 在 2023/11/6 16:21, Nikita Amelchev 写道:
> > > > > Igniters,
> > > > >
> > > > > I have cut the release branch: 'ignite-2.16'. Please, cherry-pick new
> > > > > issues if needed.
> > > > >
> > > > > The 2.16 scope is frozen. Unresolved not-blocking issues will be moved
> > > > > on the code freeze stage.
> > > > >
> > > > > Code freeze is planned for November 13, 2023. Please, feel free to
> > > > > write if some issues are critical to be in the 2.16.
> > > > >
> > > > > ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev:
> > > > >> Hello Igniters,
> > > > >>
> > > > >> I have created the 2.16 release page [1].
> > > > >>
> > > > >> Also, I propose to cut the release branch on the scope freeze day
> > > > >> (November 6, 2023).
> > > > >>
> > > > >> [1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16
> > > > >>
> > > > >> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov:
> > > > >>> +1, fully support Nikita to be RM
> > > > >>>
> > > > >>>
> > > > >>> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn:
> > > > >>>
> > > > >>>> Sounds good, new JDK support seems to be in demand.
> > > > >>>>
> > > > >>>> On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov 
> > > > >>>>  wrote:
> > > > >>>>
> > > > >>>>> +1
> > > > >>>>>
> > > > >>>>> On Sun, Oct 22, 2023 at 12:29 PM Nikita 
> > > > >>>>> Amelchev
> > > > >>>>> wrote:
> > > > >>>>>
> > > > >>>>>> Dear Ignite Community!
> > > > >>>>>>
> > > > >>>>>> I suggest starting Apache Ignite 2.16 release activities.
> > > > >>>>>>
> > > > >>>>>> We've accumulated a hundred resolved [1] issues with new 
> > > > >>>>>> features and
> > > > >

Re: New Apache Ignite PMC member: Nikita Amelchev

[Nikita Amelchev]

Thank you everyone, I'm very pleased!

ср, 22 нояб. 2023 г. в 15:46, Ilya Shishkov :
>
> Congratulations, Nikita!
>
> ср, 22 нояб. 2023 г. в 14:53, Maksim Timonin :
> >
> > Congratulations!
> >
> > On Wed, Nov 22, 2023 at 2:29 PM Anton Vinogradov  wrote:
> >
> > > Welcome aboard :)
> > >
> > > On Wed, Nov 22, 2023 at 2:11 PM Maxim Muzafarov  wrote:
> > >
> > > > My congratulations, Nikita!
> > > >
> > > > On Tue, 21 Nov 2023 at 15:20, Dmitriy Pavlov  wrote:
> > > > >
> > > > > Hello Igniters,
> > > > >
> > > > > The Project Management Committee (PMC) for Apache Ignite
> > > > > has invited Nikita Amelchev to become a member of PMC and we are
> > > pleased
> > > > > to announce that he has accepted.
> > > > >
> > > > > We appreciate his constant efforts in improving Apache Ignite code, as
> > > > well
> > > > > as efforts in preparing 2 major releases.
> > > > >
> > > > > A PMC member helps manage and guide the direction of the project.
> > > > >
> > > > > Congratulations on your new role! Keep the pace!
> > > > >
> > > > > Best Regards
> > > > > Dmitriy Pavlov
> > > > > on behalf of Apache Ignite PMC
> > > >
> > >



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Igniters.

I'm announcing a code freeze for the 2.16 release. Only blockers are
accepted to the release since this moment.

пн, 13 нояб. 2023 г. в 19:13, Nikita Amelchev :
>
> Hello, Igniters.
>
> I suggest moving the code freeze date to +1 week.
>
> We have several bug fixes ready to be merged [1], for example:
>
> IGNITE-19239 Checkpoint read lock acquisition timeouts during snapshot restore
> IGNITE-20816 In-memory server node is crashed by
> TcpIgniteClient.putAllConflict() if cache objects transformation
> applied
>
> Updated dates:
>
> Code Freeze: November 20, 2023
> Voting Date: November 27, 2023
> Release Date: December 4, 2023
>
> [1] 
> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
>
> пн, 6 нояб. 2023 г. в 12:36, Nikita Amelchev :
> >
> > Hi,
> >
> > Yes, they are marked with the 2.16 fix version. According to the
> > release process they will be cherry-picked to the release branch if
> > merged before code freeze.
> >
> > Documentation issues can be cherry-picked regardless of these dates.
> >
> > пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>:
> > >
> > > Hi,
> > >
> > > Can the following PR be included in the scope of 2.16.0 version?
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-10268
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-18038
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-18572
> > >
> > > https://issues.apache.org/jira/browse/IGNITE-19436
> > >
> > >
> > > 在 2023/11/6 16:21, Nikita Amelchev 写道:
> > > > Igniters,
> > > >
> > > > I have cut the release branch: 'ignite-2.16'. Please, cherry-pick new
> > > > issues if needed.
> > > >
> > > > The 2.16 scope is frozen. Unresolved not-blocking issues will be moved
> > > > on the code freeze stage.
> > > >
> > > > Code freeze is planned for November 13, 2023. Please, feel free to
> > > > write if some issues are critical to be in the 2.16.
> > > >
> > > > ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev:
> > > >> Hello Igniters,
> > > >>
> > > >> I have created the 2.16 release page [1].
> > > >>
> > > >> Also, I propose to cut the release branch on the scope freeze day
> > > >> (November 6, 2023).
> > > >>
> > > >> [1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16
> > > >>
> > > >> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov:
> > > >>> +1, fully support Nikita to be RM
> > > >>>
> > > >>>
> > > >>> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn:
> > > >>>
> > > >>>> Sounds good, new JDK support seems to be in demand.
> > > >>>>
> > > >>>> On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  
> > > >>>> wrote:
> > > >>>>
> > > >>>>> +1
> > > >>>>>
> > > >>>>> On Sun, Oct 22, 2023 at 12:29 PM Nikita 
> > > >>>>> Amelchev
> > > >>>>> wrote:
> > > >>>>>
> > > >>>>>> Dear Ignite Community!
> > > >>>>>>
> > > >>>>>> I suggest starting Apache Ignite 2.16 release activities.
> > > >>>>>>
> > > >>>>>> We've accumulated a hundred resolved [1] issues with new features 
> > > >>>>>> and
> > > >>>>>> bug fixes which are waiting for their release date. For example:
> > > >>>>>>
> > > >>>>>> Calcite engine: added hints, became more stable, covered with
> > > >>>> diagnostic
> > > >>>>>> tools;
> > > >>>>>> Cluster Management API (IEP-81);
> > > >>>>>> Realtime CDC (IEP-104, ready to be merged);
> > > >>>>>> Fixes to support JDK 14-21;
> > > >>>>>> Several critical issues;
> > > >>>>>> etc.
> > > >>>>>>
> > > >>>>>> I want to propose myself to be the release manager of the planning
> > > >>>>> release.
> > > >>>>>> I propose the following timeline:
> > > >>>>>>
> > > >>>>>> Scope Freeze: November 6, 2023
> > > >>>>>> Code Freeze: November 13, 2022
> > > >>>>>> Voting Date: November 20, 2022
> > > >>>>>> Release Date: November 27, 2022
> > > >>>>>>
> > > >>>>>> WDYT?
> > > >>>>>>
> > > >>>>>> [1]
> > > >>>>>>
> > > >>>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > > >>>>>>
> > > >>>>>> --
> > > >>>>>> Best wishes,
> > > >>>>>> Amelchev Nikita
> > > >>>>>>
> > > >>
> > > >>
> > > >> --
> > > >> Best wishes,
> > > >> Amelchev Nikita
> > > >
> > > >
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>
>
>
> --
> Best wishes,
> Amelchev Nikita



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Igniters.

I suggest moving the code freeze date to +1 week.

We have several bug fixes ready to be merged [1], for example:

IGNITE-19239 Checkpoint read lock acquisition timeouts during snapshot restore
IGNITE-20816 In-memory server node is crashed by
TcpIgniteClient.putAllConflict() if cache objects transformation
applied

Updated dates:

Code Freeze: November 20, 2023
Voting Date: November 27, 2023
Release Date: December 4, 2023

[1] 
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

пн, 6 нояб. 2023 г. в 12:36, Nikita Amelchev :
>
> Hi,
>
> Yes, they are marked with the 2.16 fix version. According to the
> release process they will be cherry-picked to the release branch if
> merged before code freeze.
>
> Documentation issues can be cherry-picked regardless of these dates.
>
> пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>:
> >
> > Hi,
> >
> > Can the following PR be included in the scope of 2.16.0 version?
> >
> > https://issues.apache.org/jira/browse/IGNITE-10268
> >
> > https://issues.apache.org/jira/browse/IGNITE-18038
> >
> > https://issues.apache.org/jira/browse/IGNITE-18572
> >
> > https://issues.apache.org/jira/browse/IGNITE-19436
> >
> >
> > 在 2023/11/6 16:21, Nikita Amelchev 写道:
> > > Igniters,
> > >
> > > I have cut the release branch: 'ignite-2.16'. Please, cherry-pick new
> > > issues if needed.
> > >
> > > The 2.16 scope is frozen. Unresolved not-blocking issues will be moved
> > > on the code freeze stage.
> > >
> > > Code freeze is planned for November 13, 2023. Please, feel free to
> > > write if some issues are critical to be in the 2.16.
> > >
> > > ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev:
> > >> Hello Igniters,
> > >>
> > >> I have created the 2.16 release page [1].
> > >>
> > >> Also, I propose to cut the release branch on the scope freeze day
> > >> (November 6, 2023).
> > >>
> > >> [1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16
> > >>
> > >> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov:
> > >>> +1, fully support Nikita to be RM
> > >>>
> > >>>
> > >>> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn:
> > >>>
> > >>>> Sounds good, new JDK support seems to be in demand.
> > >>>>
> > >>>> On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  
> > >>>> wrote:
> > >>>>
> > >>>>> +1
> > >>>>>
> > >>>>> On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev
> > >>>>> wrote:
> > >>>>>
> > >>>>>> Dear Ignite Community!
> > >>>>>>
> > >>>>>> I suggest starting Apache Ignite 2.16 release activities.
> > >>>>>>
> > >>>>>> We've accumulated a hundred resolved [1] issues with new features and
> > >>>>>> bug fixes which are waiting for their release date. For example:
> > >>>>>>
> > >>>>>> Calcite engine: added hints, became more stable, covered with
> > >>>> diagnostic
> > >>>>>> tools;
> > >>>>>> Cluster Management API (IEP-81);
> > >>>>>> Realtime CDC (IEP-104, ready to be merged);
> > >>>>>> Fixes to support JDK 14-21;
> > >>>>>> Several critical issues;
> > >>>>>> etc.
> > >>>>>>
> > >>>>>> I want to propose myself to be the release manager of the planning
> > >>>>> release.
> > >>>>>> I propose the following timeline:
> > >>>>>>
> > >>>>>> Scope Freeze: November 6, 2023
> > >>>>>> Code Freeze: November 13, 2022
> > >>>>>> Voting Date: November 20, 2022
> > >>>>>> Release Date: November 27, 2022
> > >>>>>>
> > >>>>>> WDYT?
> > >>>>>>
> > >>>>>> [1]
> > >>>>>>
> > >>>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > >>>>>>
> > >>>>>> --
> > >>>>>> Best wishes,
> > >>>>>> Amelchev Nikita
> > >>>>>>
> > >>
> > >>
> > >> --
> > >> Best wishes,
> > >> Amelchev Nikita
> > >
> > >
>
>
>
> --
> Best wishes,
> Amelchev Nikita



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hi,

Yes, they are marked with the 2.16 fix version. According to the
release process they will be cherry-picked to the release branch if
merged before code freeze.

Documentation issues can be cherry-picked regardless of these dates.

пн, 6 нояб. 2023 г. в 11:47, 李玉珏 <18624049...@163.com>:
>
> Hi,
>
> Can the following PR be included in the scope of 2.16.0 version?
>
> https://issues.apache.org/jira/browse/IGNITE-10268
>
> https://issues.apache.org/jira/browse/IGNITE-18038
>
> https://issues.apache.org/jira/browse/IGNITE-18572
>
> https://issues.apache.org/jira/browse/IGNITE-19436
>
>
> 在 2023/11/6 16:21, Nikita Amelchev 写道:
> > Igniters,
> >
> > I have cut the release branch: 'ignite-2.16'. Please, cherry-pick new
> > issues if needed.
> >
> > The 2.16 scope is frozen. Unresolved not-blocking issues will be moved
> > on the code freeze stage.
> >
> > Code freeze is planned for November 13, 2023. Please, feel free to
> > write if some issues are critical to be in the 2.16.
> >
> > ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev:
> >> Hello Igniters,
> >>
> >> I have created the 2.16 release page [1].
> >>
> >> Also, I propose to cut the release branch on the scope freeze day
> >> (November 6, 2023).
> >>
> >> [1]https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16
> >>
> >> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov:
> >>> +1, fully support Nikita to be RM
> >>>
> >>>
> >>> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn:
> >>>
> >>>> Sounds good, new JDK support seems to be in demand.
> >>>>
> >>>> On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  
> >>>> wrote:
> >>>>
> >>>>> +1
> >>>>>
> >>>>> On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev
> >>>>> wrote:
> >>>>>
> >>>>>> Dear Ignite Community!
> >>>>>>
> >>>>>> I suggest starting Apache Ignite 2.16 release activities.
> >>>>>>
> >>>>>> We've accumulated a hundred resolved [1] issues with new features and
> >>>>>> bug fixes which are waiting for their release date. For example:
> >>>>>>
> >>>>>> Calcite engine: added hints, became more stable, covered with
> >>>> diagnostic
> >>>>>> tools;
> >>>>>> Cluster Management API (IEP-81);
> >>>>>> Realtime CDC (IEP-104, ready to be merged);
> >>>>>> Fixes to support JDK 14-21;
> >>>>>> Several critical issues;
> >>>>>> etc.
> >>>>>>
> >>>>>> I want to propose myself to be the release manager of the planning
> >>>>> release.
> >>>>>> I propose the following timeline:
> >>>>>>
> >>>>>> Scope Freeze: November 6, 2023
> >>>>>> Code Freeze: November 13, 2022
> >>>>>> Voting Date: November 20, 2022
> >>>>>> Release Date: November 27, 2022
> >>>>>>
> >>>>>> WDYT?
> >>>>>>
> >>>>>> [1]
> >>>>>>
> >>>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> >>>>>>
> >>>>>> --
> >>>>>> Best wishes,
> >>>>>> Amelchev Nikita
> >>>>>>
> >>
> >>
> >> --
> >> Best wishes,
> >> Amelchev Nikita
> >
> >



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Igniters,

I have cut the release branch: 'ignite-2.16'. Please, cherry-pick new
issues if needed.

The 2.16 scope is frozen. Unresolved not-blocking issues will be moved
on the code freeze stage.

Code freeze is planned for November 13, 2023. Please, feel free to
write if some issues are critical to be in the 2.16.

ср, 25 окт. 2023 г. в 15:00, Nikita Amelchev :
>
> Hello Igniters,
>
> I have created the 2.16 release page [1].
>
> Also, I propose to cut the release branch on the scope freeze day
> (November 6, 2023).
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16
>
> вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov :
> >
> > +1, fully support Nikita to be RM
> >
> >
> > пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn :
> >
> > > Sounds good, new JDK support seems to be in demand.
> > >
> > > On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  wrote:
> > >
> > > > +1
> > > >
> > > > On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev 
> > > > wrote:
> > > >
> > > > > Dear Ignite Community!
> > > > >
> > > > > I suggest starting Apache Ignite 2.16 release activities.
> > > > >
> > > > > We've accumulated a hundred resolved [1] issues with new features and
> > > > > bug fixes which are waiting for their release date. For example:
> > > > >
> > > > > Calcite engine: added hints, became more stable, covered with
> > > diagnostic
> > > > > tools;
> > > > > Cluster Management API (IEP-81);
> > > > > Realtime CDC (IEP-104, ready to be merged);
> > > > > Fixes to support JDK 14-21;
> > > > > Several critical issues;
> > > > > etc.
> > > > >
> > > > > I want to propose myself to be the release manager of the planning
> > > > release.
> > > > >
> > > > > I propose the following timeline:
> > > > >
> > > > > Scope Freeze: November 6, 2023
> > > > > Code Freeze: November 13, 2022
> > > > > Voting Date: November 20, 2022
> > > > > Release Date: November 27, 2022
> > > > >
> > > > > WDYT?
> > > > >
> > > > > [1]
> > > > >
> > > >
> > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > > > >
> > > > >
> > > > > --
> > > > > Best wishes,
> > > > > Amelchev Nikita
> > > > >
> > > >
> > >
>
>
>
> --
> Best wishes,
> Amelchev Nikita



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello Igniters,

I have created the 2.16 release page [1].

Also, I propose to cut the release branch on the scope freeze day
(November 6, 2023).

[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.16

вт, 24 окт. 2023 г. в 19:13, Dmitriy Pavlov :
>
> +1, fully support Nikita to be RM
>
>
> пн, 23 окт. 2023 г. в 13:29, Pavel Tupitsyn :
>
> > Sounds good, new JDK support seems to be in demand.
> >
> > On Mon, Oct 23, 2023 at 12:20 PM Anton Vinogradov  wrote:
> >
> > > +1
> > >
> > > On Sun, Oct 22, 2023 at 12:29 PM Nikita Amelchev 
> > > wrote:
> > >
> > > > Dear Ignite Community!
> > > >
> > > > I suggest starting Apache Ignite 2.16 release activities.
> > > >
> > > > We've accumulated a hundred resolved [1] issues with new features and
> > > > bug fixes which are waiting for their release date. For example:
> > > >
> > > > Calcite engine: added hints, became more stable, covered with
> > diagnostic
> > > > tools;
> > > > Cluster Management API (IEP-81);
> > > > Realtime CDC (IEP-104, ready to be merged);
> > > > Fixes to support JDK 14-21;
> > > > Several critical issues;
> > > > etc.
> > > >
> > > > I want to propose myself to be the release manager of the planning
> > > release.
> > > >
> > > > I propose the following timeline:
> > > >
> > > > Scope Freeze: November 6, 2023
> > > > Code Freeze: November 13, 2022
> > > > Voting Date: November 20, 2022
> > > > Release Date: November 27, 2022
> > > >
> > > > WDYT?
> > > >
> > > > [1]
> > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> > > >
> > > >
> > > > --
> > > > Best wishes,
> > > > Amelchev Nikita
> > > >
> > >
> >



-- 
Best wishes,
Amelchev Nikita

Apache Ignite 2.16 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Dear Ignite Community!

I suggest starting Apache Ignite 2.16 release activities.

We've accumulated a hundred resolved [1] issues with new features and
bug fixes which are waiting for their release date. For example:

Calcite engine: added hints, became more stable, covered with diagnostic tools;
Cluster Management API (IEP-81);
Realtime CDC (IEP-104, ready to be merged);
Fixes to support JDK 14-21;
Several critical issues;
etc.

I want to propose myself to be the release manager of the planning release.

I propose the following timeline:

Scope Freeze: November 6, 2023
Code Freeze: November 13, 2022
Voting Date: November 20, 2022
Release Date: November 27, 2022

WDYT?

[1] 
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.16%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority


-- 
Best wishes,
Amelchev Nikita

Re: Removal of ignite ml module (or moving it to extensions)

[Nikita Amelchev]

+1 for moving to extensions

This module is good as an extension:
- does not depend on the internal Ignite API,
- the released module will be compatible with any required version of
Ignite using the provided dependency scope.

Ivan, I have reviewed your patch, LGTM.

чт, 17 авг. 2023 г. в 17:06, Dmitry Pavlov :
>
> +1 for Apache Way in decision making (it states there should not be time 
> pressure for the decision making).
>
> 0 for removal
> 0 for moving to extensions
>
> but since Aleksei is an expert here, it makes sense to me to wait for him.
>
> Sincerely,
> Dmitriy Pavlov
>
> On 2023/08/16 17:32:55 Aleksei Zinovev wrote:
> > Hi, I have objection for fast merging, (not for moving) as a module
> > maintainer.
> >
> > I never used ignite extension, need a time to be familiar with it and test
> > the pr.
> >
> > Please postpone it till 10 september.
> >
> > I don't understand reasons to do it so fast. I suppose it's ok to wait
> > 15-20 days with PR
> >
> > Thanks for collaboration and doing this work.
> >



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.15.0 RC0

[Nikita Amelchev]

+1

Downloaded sources, binaries, tested node startup, command utility and
several examples.

пт, 28 апр. 2023 г. в 04:05, 18624049226 <18624049...@163.com>:
>
> The following PR should be merged.
>
> But I think this should not affect the voting.
>
> https://issues.apache.org/jira/browse/IGNITE-19378
>
> 在 2023/4/27 12:36, Pavel Tupitsyn 写道:
> > +1 (binding)
> >
> > Downloaded binaries, tested node startup, NuGet packages, .NET examples.
> >
> > On Wed, Apr 26, 2023 at 10:52 PM Alex Plehanov
> > wrote:
> >
> >> Dear Community,
> >>
> >> The release candidate is ready.
> >>
> >> I have uploaded release candidate to
> >> https://dist.apache.org/repos/dist/dev/ignite/2.15.0-rc0/
> >> https://dist.apache.org/repos/dist/dev/ignite/packages_2.15.0-rc0/
> >>
> >> The following staging can be used for testing:
> >> https://repository.apache.org/content/repositories/orgapacheignite-1558/
> >>
> >> Tag name is 2.15.0-rc0:
> >>
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.15.0-rc0
> >>
> >> 2.15.0 most important changes:
> >> * Implemented incremental snapshots.
> >> * Java thin client improvements (logging, connections balancing, events
> >> listening, endpoints discovery)
> >> * Calcite based SQL engine improvements (memory quotas, index scans
> >> optimisations).
> >> * Reworked permission management for system tasks.
> >> * Removed deprecated functionality (daemon nodes, visorcmd, legacy JMX
> >> beans).
> >>
> >> RELEASE NOTES:
> >>
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.15
> >>
> >> Complete list of resolved issues:
> >>
> >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20'Ignite'%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20('2.15'))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20('CLOSED'%2C%20'RESOLVED')%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> >> <
> >> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.15%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20AND%20resolution%20in(Fixed%2C%20Done%2C%20Implemented%2C%20Delivered)%20ORDER%20BY%20priority
> >>
> >> DEVNOTES
> >>
> >> https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.15
> >>
> >> The vote is formal, see voting guidelines
> >> https://www.apache.org/foundation/
> >> voting.html
> >>
> >> +1 - to accept Apache Ignite 2.15.0-rc0
> >> 0 - don't care either way
> >> -1 - DO NOT accept Apache Ignite Ignite 2.15.0-rc0 (explain why)
> >>
> >> See notes on how to verify release here
> >> https://www.apache.org/info/verification.html
> >> and
> >>
> >> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >>
> >> This vote will be open till Tue May 2, 2023, 07:00 UTC.
> >>
> >> https://www.timeanddate.com/countdown/vote?iso=20230502T07=0=VOTE+on+the+Apache+Ignite+Release+2.15.0+RC0=sanserif
> >>



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Extensions Ignite Spark 2.0.0 RC1, Ignite Spark 3.0.0 RC1

[Nikita Amelchev]

+1

Checked compilation, ran some examples.

пт, 9 дек. 2022 г. в 03:53, Alexandr Shapkin :
>
> Dear Community,
>
>
> The release candidates are ready.
>
> These are new Ignite Spark integrations based on Spark 2.4 and 3.2 
> dependencies respectively.
>
>
> See the links below.
>
>
> == Ignite Spark Extension Module 2.0.0 ==
>
> The release candidate is uploaded to:
> https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spark-ext-2.0.0-rc1/
>
> The following Maven staging can be used:
> https://repository.apache.org/content/repositories/orgapacheignite-1557/org/apache/ignite/ignite-spark-ext/
>
> Tag:
> https://github.com/apache/ignite-extensions/releases/tag/ignite-spark-ext-2.0.0-rc1
>
> RELEASE_NOTES:
> https://github.com/apache/ignite-extensions/blob/release/ignite-spark-ext-2.0.0/modules/spark-ext/spark/RELEASE_NOTES.txt
>
> DEVNOTES:
> https://github.com/apache/ignite-extensions/blob/release/ignite-spark-ext-2.0.0/DEVNOTES.md
>
> Release Checker Results:
> https://github.com/apache/ignite-extensions/actions/runs/3652976657
>
>
>
> == Ignite Spark Extension Module 3.0.0 ==
>
> The release candidate is uploaded to:
> https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spark-ext-3.0.0-rc1/
>
> The following Maven staging can be used:
> https://repository.apache.org/content/repositories/orgapacheignite-1557/org/apache/ignite/ignite-spark-ext/
>
> Tag:
> https://github.com/apache/ignite-extensions/releases/tag/ignite-spark-ext-3.0.0-rc1
>
> RELEASE_NOTES:
> https://github.com/apache/ignite-extensions/blob/release/ignite-spark-ext-3.0.0/modules/spark-ext/spark/RELEASE_NOTES.txt
>
> DEVNOTES:
> https://github.com/apache/ignite-extensions/blob/release/ignite-spark-ext-3.0.0/DEVNOTES.md
>
> Release Checker Results:
> https://github.com/apache/ignite-extensions/actions/runs/3634524603
>
>
>
> The vote is formal, see voting guidelines
> https://www.apache.org/foundation/voting.html
>
> +1 - to accept (Ignite Spark 3.0.0 RC1, Ignite Spark 2.0.0 RC1)
> 0 - don't care either way
> -1 - DO NOT accept (explain why)
>
> See notes on how to verify release here
> https://www.apache.org/info/verification.html
> and
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
>
>
> This vote will be open for at least 72 hours till Mon Dec, 12 2022, 02:00 CET 
> TZ.
> Please, write down the thread if you need additional time to check the 
> release.
>


-- 
Best wishes,
Amelchev Nikita

Re: [ANNOUNCE] Welcome Mikhail Petrov as a new Committer

[Nikita Amelchev]

My congratulations, Mikhail!

пт, 11 нояб. 2022 г. в 11:55, Maksim Timonin :
>
> Hi Mikhail! Congratulations!
>
> On Fri, Nov 11, 2022 at 11:30 AM Vladimir Steshin 
> wrote:
>
> > Mikhail, congratulations!
> >
> > 11.11.2022 11:20, Maxim Muzafarov пишет:
> > > The Project Management Committee (PMC) for Apache Ignite has invited
> > > Mikhail Petrov to become a committer and we are pleased to announce
> > > that they have accepted.
> > >
> > > Mikhail Petrov is an active contributor and community member, he made
> > > significant additions to Ignite and Ignite Extensions code bases, this
> > > client support for Spring Data, Spring Transactions, tracing of SQL
> > > queries etc.
> > >
> > > Being a committer enables easier contribution to the project since
> > > there is no need to go via the patch submission process. This should
> > > enable better productivity.
> > >
> > > Please join in welcoming Mikhail Petrov, and congratulating him on the
> > > new role in the Apache Ignite Community!
> > >
> > >
> > > Best Regards,
> > > Maxim Muzafarov
> > > on behalf of Apache Ignite PMC



-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

[Nikita Amelchev]

Stanislav,

2.15: The system property will be deprecated. Release notes will
contain warning info about deprecation and behavior in future
releases.

2.16: The system property will be removed. All atomic operations
within transactions will be forbidden.

See merged PR: https://github.com/apache/ignite/pull/10327/files

сб, 22 окт. 2022 г. в 17:42, Stanislav Lukyanov :
>
> Hi all,
>
> Can someone please clarify what specific changes will be implemented in 2.15 
> and 2.16? What will be in release notes in 2.15 and 2.16?
>
> Thanks,
> Stan
>
> > On 18 Oct 2022, at 21:50, Nikita Amelchev  wrote:
> >
> > Hi, Maksim.
> >
> > I think marking the issue as 'important' and filling out the release
> > notes field is enough to get the attention of a release manager.
> >
> > вт, 18 окт. 2022 г. в 20:26, Maksim Timonin :
> >>
> >> Hi guys,
> >>
> >> We agreed here [1] that all deprecations must be noted within release
> >> notes. Do we have an option to mark a jira ticket in such a way to fill the
> >> future release notes correctly?
> >>
> >> [1] https://lists.apache.org/thread/3ko0kjdv16o3oftsfh8z8nz0tyfvo13v
> >>
> >> On Mon, Oct 17, 2022 at 8:21 PM Anton Vinogradov  wrote:
> >>
> >>> Ok, let's do this.
> >>> And schedule the fix to the 2.16.
> >>>
> >>> On Mon, Oct 17, 2022 at 7:42 PM Alexei Scherbakov <
> >>> alexey.scherbak...@gmail.com> wrote:
> >>>
> >>>> By placing the @Deprecated annotation on the property.
> >>>>
> >>>> пн, 17 окт. 2022 г. в 19:07, Anton Vinogradov :
> >>>>
> >>>>> How can we deprecate this?
> >>>>>
> >>>>> On Mon, Oct 17, 2022 at 5:30 PM Alexei Scherbakov <
> >>>>> alexey.scherbak...@gmail.com> wrote:
> >>>>>
> >>>>>> We can do breaking changes by following the approved procedure: 1)
> >>>>>> deprecate in the next release 2) remove in the some release after the
> >>>>> next
> >>>>>>
> >>>>>> The ticket looks fine to me.
> >>>>>>
> >>>>>> пн, 17 окт. 2022 г. в 15:50, Anton Vinogradov :
> >>>>>>
> >>>>>>> We MUST break this, of course!
> >>>>>>> Atomic operations inside the transaction is a wrong and unexpected
> >>>>>>> behaviour and MUST be restricted for every user.
> >>>>>>>
> >>>>>>> On Mon, Oct 17, 2022 at 3:05 PM Julia Bakulina <
> >>>> julia.bak...@yandex.ru
> >>>>>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>> Hi Team,
> >>>>>>>>
> >>>>>>>> I have found this ticket
> >>>>>>> https://issues.apache.org/jira/browse/IGNITE-8801 -
> >>>>>>>> Change default behaviour of atomic operations inside
> >>> transactions -
> >>>>> in
> >>>>>>>> backlog and created a PR with changes. The ticket relates to
> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-2313.
> >>>>>>>> During the review process it appeared that probably there is no
> >>>> need
> >>>>> in
> >>>>>>>> this ticket as it includes the changes of the default API and we
> >>>>> should
> >>>>>>> not
> >>>>>>>> break backward compatibility.
> >>>>>>>>
> >>>>>>>> Do we need these changes? Should the ticket be closed with "won't
> >>>>> fix"?
> >>>>>>>>
> >>>>>>>> Have a nice day,
> >>>>>>>> Julia
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>>
> >>>>>> Best regards,
> >>>>>> Alexei Scherbakov
> >>>>>>
> >>>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> Best regards,
> >>>> Alexei Scherbakov
> >>>>
> >>>
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>


-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSSION] Change default behaviour of atomic operations inside transactions

[Nikita Amelchev]

Hi, Maksim.

I think marking the issue as 'important' and filling out the release
notes field is enough to get the attention of a release manager.

вт, 18 окт. 2022 г. в 20:26, Maksim Timonin :
>
> Hi guys,
>
> We agreed here [1] that all deprecations must be noted within release
> notes. Do we have an option to mark a jira ticket in such a way to fill the
> future release notes correctly?
>
> [1] https://lists.apache.org/thread/3ko0kjdv16o3oftsfh8z8nz0tyfvo13v
>
> On Mon, Oct 17, 2022 at 8:21 PM Anton Vinogradov  wrote:
>
> > Ok, let's do this.
> > And schedule the fix to the 2.16.
> >
> > On Mon, Oct 17, 2022 at 7:42 PM Alexei Scherbakov <
> > alexey.scherbak...@gmail.com> wrote:
> >
> > > By placing the @Deprecated annotation on the property.
> > >
> > > пн, 17 окт. 2022 г. в 19:07, Anton Vinogradov :
> > >
> > > > How can we deprecate this?
> > > >
> > > > On Mon, Oct 17, 2022 at 5:30 PM Alexei Scherbakov <
> > > > alexey.scherbak...@gmail.com> wrote:
> > > >
> > > > > We can do breaking changes by following the approved procedure: 1)
> > > > > deprecate in the next release 2) remove in the some release after the
> > > > next
> > > > >
> > > > > The ticket looks fine to me.
> > > > >
> > > > > пн, 17 окт. 2022 г. в 15:50, Anton Vinogradov :
> > > > >
> > > > > > We MUST break this, of course!
> > > > > > Atomic operations inside the transaction is a wrong and unexpected
> > > > > > behaviour and MUST be restricted for every user.
> > > > > >
> > > > > > On Mon, Oct 17, 2022 at 3:05 PM Julia Bakulina <
> > > julia.bak...@yandex.ru
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Team,
> > > > > > >
> > > > > > > I have found this ticket
> > > > > > https://issues.apache.org/jira/browse/IGNITE-8801 -
> > > > > > > Change default behaviour of atomic operations inside
> > transactions -
> > > > in
> > > > > > > backlog and created a PR with changes. The ticket relates to
> > > > > > > https://issues.apache.org/jira/browse/IGNITE-2313.
> > > > > > > During the review process it appeared that probably there is no
> > > need
> > > > in
> > > > > > > this ticket as it includes the changes of the default API and we
> > > > should
> > > > > > not
> > > > > > > break backward compatibility.
> > > > > > >
> > > > > > > Do we need these changes? Should the ticket be closed with "won't
> > > > fix"?
> > > > > > >
> > > > > > > Have a nice day,
> > > > > > > Julia
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Best regards,
> > > > > Alexei Scherbakov
> > > > >
> > > >
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Alexei Scherbakov
> > >
> >



-- 
Best wishes,
Amelchev Nikita

Re: [ANNOUNCE] New PMC member: Ivan Daschinsky

[Nikita Amelchev]

My congratulations, Ivan!

пн, 19 сент. 2022 г. в 11:28, Maksim Timonin :
>
> Hi, Ivan!
>
> Congratulations!
>
> On Mon, Sep 19, 2022 at 10:05 AM Вячеслав Коптилин 
> wrote:
>
> > Hi,
> >
> > Congratulations Ivan! Well-deserved!
> >
> > Thanks,
> > Slava.
> >
> >
> > вс, 18 сент. 2022 г. в 12:10, Zhenya Stanilovsky
> >  > >:
> >
> > >
> > > Join the congratulations !
> > >
> > >
> > >
> > >
> > > >Hi Igniters!
> > > >
> > > >The Project Management Committee (PMC) for Apache Ignite has invited
> > > >Ivan Daschinsky to become a member of the PMC and we are pleased to
> > > >announce that he has accepted.
> > > >
> > > >Ivan contributed the Ignite Python thin client. And he is still
> > > maintaining
> > > >it.
> > > >He is also actively supporting users.
> > > >
> > > >Please join me in congratulating Ivan on his new role.
> > > >
> > > >Best Regards,
> > > >Dmitriy Pavlov
> > > >on behalf of Apache Ignite PMC
> > >
> > >
> > >
> > >
> >



-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSS] Colorize Ignite test console output

[Nikita Amelchev]

Pavel, Looks cool.

+1 to add to the default log config.

вт, 6 сент. 2022 г. в 13:20, Pavel Tupitsyn :
>
> Thanks for the explanation.
>
> Yes, I think we can apply the same color scheme everywhere, but let's hear
> more opinions.
>
> On Tue, Sep 6, 2022 at 1:10 PM Pavel Pereslegin  wrote:
>
> > Hello Pavel,
> >
> > I decided that it's safer to apply this only to our tests first, and
> > then if everything is ok, apply the same logger pattern to the default
> > production log4j-config,
> > If you think it's worth applying them now to the production config - I
> > can do it.
> >
> > вт, 6 сент. 2022 г. в 12:33, Pavel Tupitsyn :
> > >
> > > Looks great!
> > >
> > > However, I'm a bit confused - does it apply to node output in production
> > > build?
> > > Why does it say "test console output"?
> > >
> > > On Tue, Sep 6, 2022 at 12:20 PM Mirza Aliev 
> > wrote:
> > >
> > > > Hello Pavel! Looks awesome! Thank you for the enhancement!
> > > >
> > > > вт, 6 сент. 2022 г. в 10:37, Pavel Pereslegin :
> > > >
> > > > > Hello Igniters!
> > > > >
> > > > > Recently completed Ignite migration to use log4j2 [1].
> > > > > Log4j2 supports ANSI colorization in the console [2], which can help
> > > > > in parsing log output.
> > > > > As an experiment, I would like to colorize the test console output
> > [3].
> > > > >
> > > > > The color palette is similar to spring boot, see light [4] and dark
> > > > > [5] console output example.
> > > > >
> > > > > If there are no objections, I will merge these changes soon [6].
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16650
> > > > > [2]
> > https://logging.apache.org/log4j/2.x/manual/layouts.html#Patterns
> > > > > [3] https://issues.apache.org/jira/browse/IGNITE-17442
> > > > > [4]
> > > > >
> > > >
> > https://issues.apache.org/jira/secure/attachment/13048986/light-console.jpg
> > > > > [5]
> > > > >
> > > >
> > https://issues.apache.org/jira/secure/attachment/13048991/dark-console-example.png
> > > > > [6] https://github.com/apache/ignite/pull/10229/files
> > > > >
> > > >
> >



-- 
Best wishes,
Amelchev Nikita

Re: [ANNOUNCE] New PMC member: Vyacheslav Koptilin

[Nikita Amelchev]

My congratulations, Slava!

чт, 18 авг. 2022 г. в 07:33, Ivan Pavlukhin :
>
> Congratulations, Slava!
>
> Best regards,
> Ivan Pavlukhin
>
> ср, 17 авг. 2022 г. в 21:11, Roman Puchkovskiy :
> >
> > Congratulations, Slava!
> >
> > ср, 17 авг. 2022 г. в 22:10, Aleksandr Pakhomov :
> > >
> > > Congratulations! Well-deserved.
> > >
> > >
> > > > On 17 Aug 2022, at 17:34, Kseniya Romanova  
> > > > wrote:
> > > >
> > > > Hi Igniters!
> > > >
> > > > The Project Management Committee (PMC) for Apache Ignite has invited
> > > > Vyacheslav Koptilin to become a member of the PMC and we are pleased to
> > > > announce that he has accepted.
> > > >
> > > > Vyacheslav is a veteran committer and contributes a lot to the Ignite
> > > > storage https://github.com/sk0x50.
> > > >
> > > > Please join me in congratulating Vyacheslav on his new role.
> > > >
> > > > Best Regards,
> > > > Kseniya Romanova
> > > > on behalf of Apache Ignite PMC
> > >



-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSS] Ignite service interceptor.

[Nikita Amelchev]

Hello,

The single method proposal looks good to me.

> But with this approach, a service can only have one interceptor, right?

Pavel, I think we can delegate interceptors as a chain. The last
delegate calls the service method.  In this way, multiple ordered
interceptors can be configured.

ср, 29 июн. 2022 г. в 12:13, Pavel Pereslegin :
>
> Hello Pavel,
>
> I think your suggestion is better because it seems more flexible to me
> and only one method needs to be implemented by the user. So we don't
> need a default (no-op) implementation.
> But with this approach, a service can only have one interceptor, right?
> It also seems to be more error prone from the user side. The user may
> return a result of the wrong type for example. But I think this is ok,
> so if there is no objection, I will update the IEP and prepare a patch
> using the suggested approach.
>
> вт, 28 июн. 2022 г. в 19:30, Pavel Tupitsyn :
> >
> > Hello Pavel,
> >
> > The IEP looks good to me in general. It is a good addition to the service
> > API.
> >
> > One suggestion is to improve control over service method execution within
> > the interceptor:
> > 1. Bypass service call without throwing an exception.
> > 2. Convert service call result in some way
> >
> > This can be achieved by a different interface, with a single method:
> >
> > public interface ServiceCallInterceptor extends Serializable {
> > public default Object onInvoke(Supplier delegate, String mtd, Object[]
> > args, ServiceContext ctx) throws ServiceInterceptException {
> > return delegate.get();
> > }
> > }
> >
> > which can be implemented like this:
> >
> > public class MyInterceptor implements ServiceCallInterceptor {
> > @Override
> > public Object onInvoke(Supplier delegate, String mtd, Object[] args,
> > ServiceContext ctx) throws Exception {
> > AuditProvider.get().recordStartEvent(mtd,
> > ctx.currentCallContext().attribute("sessionId"));
> > try {
> > if (!checkAuthorization(ctx))
> > return notAuthorizedResult();
> >
> > Object value = delegate.get();
> >
> > return convert(value);
> > }
> > catch (Exception e) {
> > // Log error
> > return errorResult(...);
> > }
> > finally {
> > AuditProvider.get().recordEndEvent(mtd,
> > ctx.currentCallContext().attribute("sessionId"));
> > }
> > }
> > }
> >
> >
> > As you can see, this way the user has full control over all aspects of the
> > service call.
> >
> > Thoughts?
> >
> > On Tue, Jun 28, 2022 at 6:33 PM Pavel Pereslegin  wrote:
> >
> > > Hello Igniters!
> > >
> > > I want to continue discussing a feature that allows users to create
> > > their own middleware for Ignite services [1].
> > > Earlier was added the ability to implicitly pass a set of user
> > > parameters (ServiceCallContext) to the service [2].
> > > This feature allows users to track the origin of a service call.
> > > Now I'd like to add a service call interceptor to allow the user to
> > > separate the "middleware" logic from the business code and reduce
> > > boilerplate code [3].
> > >
> > > I've prepared an IEP for this feature, please take a look [4].
> > > I will prepare patches for Java and .NET for this feature soon.
> > >
> > > [1] https://lists.apache.org/thread/wqlvskxr0fvdo6rbo64bnct4zz53kpr0
> > > [2] https://issues.apache.org/jira/browse/IGNITE-15572
> > > [3] https://issues.apache.org/jira/browse/IGNITE-17022
> > > [4]
> > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334119
> > >



-- 
Best wishes,
Amelchev Nikita

Re: The 'dev-tools' project directory usages

[Nikita Amelchev]

+1 to remove.

чт, 16 июн. 2022 г. в 07:46, Maxim Muzafarov :
>
> Folks,
>
> I've prepared the patch. Please, take a look.
>
> https://issues.apache.org/jira/browse/IGNITE-17180
> https://github.com/apache/ignite/pull/10096/files
>
> On Fri, 10 Jun 2022 at 19:21, Maxim Muzafarov  wrote:
> >
> > Folks,
> >
> > I've found the 'dev-tools' [1] directory in the projects root,
> > however, I'm not sure the reals usages of these scripts.
> >
> > Can anyone clarify the purpose of existing these scripts or can we
> > remove them instead?
> >
> > The facts about this directory:
> > - it hasn't been changed since 2015;
> > - the issue [2] which added these files doesn't seems to be actual;
> >
> > [1] https://github.com/apache/ignite/tree/master/dev-tools
> > [2] https://issues.apache.org/jira/browse/IGNITE-620



-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSSION] Update documentation with GitHub Actions

[Nikita Amelchev]

Hello, Igniters.

I have added the GitHub action to publish docs on a push event. [1]

So, any documentation updates in released branches will be published
automatically (2.x versions since 2.10).

Example of the documentation update: the issue (cherry-picked to the
2.13) [2], the action workflow [3], the result commit [4].

Thanks for your feedback.

[1] https://issues.apache.org/jira/browse/IGNITE-16895
[2] https://issues.apache.org/jira/browse/IGNITE-16239
[3] https://github.com/apache/ignite/actions/runs/2277640996
[4] 
https://github.com/apache/ignite-website/commit/179be7f4642dd6fc252f8271394e58a3954c155c

ср, 4 мая 2022 г. в 17:44, Andrey Gura :
>
> +1
>
> Great! Thanks!
>
> On Sun, May 1, 2022 at 8:51 AM Pavel Tupitsyn  wrote:
> >
> > +1, this is awesome
> >
> > On Fri, Apr 29, 2022 at 3:26 PM Nikita Safonov 
> > wrote:
> >
> > > +1
> > >
> > > Cannot but support!
> > >
> > > Thanks,
> > > Nikita
> > >
> > > сб, 23 апр. 2022 г. в 17:47, Maxim Muzafarov :
> > >
> > > > Hello,
> > > >
> > > > +1, great improvement.
> > > >
> > > > On Sat, 23 Apr 2022 at 17:26, Nikita Amelchev 
> > > > wrote:
> > > > >
> > > > > Hello, Igniters.
> > > > >
> > > > > I propose to add a GitHub action to update documentation for released
> > > > > Ignite versions by a click. [1]
> > > > >
> > > > > For now, this is a complex manual work that requires understanding all
> > > > > the intermediate steps. [2]
> > > > >
> > > > > New process to update documentation:
> > > > > 1. Commit documentation changes to a released branch.
> > > > > 2. Run the action with a click.
> > > > > 3. Check the result.
> > > > >
> > > > > Moreover, this will also simplify the process of publishing a new
> > > > release.
> > > > >
> > > > > ASF's GitHub Actions Policy allows automated services to push changes
> > > > > related to documentation. [3]
> > > > > Write access is required to run the workflow. So, only committers can
> > > > > run the action. [4]
> > > > >
> > > > > WDYT? Any objections?
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16895
> > > > > [2]
> > > >
> > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs
> > > > > [3] https://infra.apache.org/github-actions-policy.html
> > > > > [4]
> > > >
> > > https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow
> > > > >
> > > > > --
> > > > > Best wishes,
> > > > > Amelchev Nikita
> > > >
> > >



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Extensions Ignite Spring Data 2.2.0 RC1, Ignite Spring Session 1.0.0 RC1, Ignite Zookeeper IP Finder 1.0.0 RC1

[Nikita Amelchev]

+1

пт, 29 апр. 2022 г. в 17:54, Anton Vinogradov :
>
> +1
>
> On Fri, Apr 29, 2022 at 5:28 PM Maxim Muzafarov  wrote:
>
> > Dear Community,
> >
> >
> > The release candidates are ready. See the links below.
> >
> >
> > == Ignite Spring Data Extension Module 2.2.0 ==
> >
> > The release candidate is uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-ext-2.2.0-rc1/
> >
> > The following Maven staging can be used:
> >
> > https://repository.apache.org/content/repositories/orgapacheignite-1547/org/apache/ignite/ignite-spring-data-ext/
> >
> > Tag:
> >
> > https://github.com/apache/ignite-extensions/releases/tag/ignite-spring-data-ext-2.2.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://github.com/apache/ignite-extensions/blob/release/ignite-spring-data-ext-2.2.0/modules/spring-data-ext/spring-data/RELEASE_NOTES.txt
> >
> > DEVNOTES:
> > https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
> >
> > Release Checker Results:
> >
> > https://github.com/apache/ignite-extensions/runs/6229346844?check_suite_focus=true
> >
> >
> >
> > == Ignite Spring Session Extension Module 1.0.0 ==
> >
> > The release candidate is uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-session-ext-1.0.0-rc1/
> >
> > The following Maven staging can be used:
> >
> > https://repository.apache.org/content/repositories/orgapacheignite-1548/org/apache/ignite/ignite-spring-session-ext/
> >
> > Tag:
> >
> > https://github.com/apache/ignite-extensions/releases/tag/ignite-spring-session-ext-1.0.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://github.com/apache/ignite-extensions/blob/release/ignite-spring-session-ext-1.0.0/modules/spring-session-ext/RELEASE_NOTES.txt
> >
> > DEVNOTES:
> > https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
> >
> > Release Checker Results:
> >
> > https://github.com/apache/ignite-extensions/runs/6229613223?check_suite_focus=true
> >
> >
> > == Ignite Zookeeper Ip Finder Extension Module 1.0.0 ==
> >
> > The release candidate is uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-zookeeper-ip-finder-ext-1.0.0-rc1/
> >
> > The following Maven staging can be used:
> >
> > https://repository.apache.org/content/repositories/orgapacheignite-1549/org/apache/ignite/ignite-zookeeper-ip-finder-ext/
> >
> > Tag:
> >
> > https://github.com/apache/ignite-extensions/releases/tag/ignite-zookeeper-ip-finder-ext-1.0.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://github.com/apache/ignite-extensions/blob/release/ignite-zookeeper-ip-finder-ext-1.0.0/modules/zookeeper-ip-finder-ext/zookeeper-ip-finder/RELEASE_NOTES.txt
> >
> > DEVNOTES:
> > https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
> >
> > Release Checker Results:
> >
> > https://github.com/apache/ignite-extensions/runs/6210193576?check_suite_focus=true
> >
> >
> >
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept (Ignite Spring Data 2.2.0 RC1, Ignite Spring Session
> > 1.0.0 RC1, Ignite Zookeeper IP Finder 1.0.0 RC1)
> > 0 - don't care either way
> > -1 - DO NOT accept (explain why)
> >
> > See notes on how to verify release here
> > https://www.apache.org/info/verification.html
> > and
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >
> >
> > This vote will be open for at least 7 days till Sat May 7, 2022,
> > 14:00 Moscow TZ. Please, write me down the thread if you need
> > additional time to check the release.
> >
> >
> > https://www.timeanddate.com/countdown/vote?iso=20220507T14=166=%5BVOTE%5D+Release+Extensions+Ignite+Spring+Data+2.2.0+RC1%2C+Ignite+Spring+Session+1.0.0+RC1%2C+Ignite+Zookeeper+IP+Finder+1.0.0+RC1=sanserif
> >



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Ignite AWS 1.0.0 RC1, Ignite Azure 1.0.0 RC1, Ignite GCE 1.0.0 RC1

[Nikita Amelchev]

+1

пт, 29 апр. 2022 г. в 15:51, Anton Vinogradov :
>
> +1
>
> On Fri, Apr 29, 2022 at 3:48 PM Maxim Muzafarov  wrote:
>
> > Dear Community,
> >
> >
> > The release candidates are ready. See the links below.
> >
> >
> > == Ignite AWS Extension Module 1.0.0 ==
> >
> > The release candidate is uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-aws-ext-1.0.0-rc1
> >
> > The following Maven staging can be used:
> >
> > https://repository.apache.org/content/repositories/orgapacheignite-1543/org/apache/ignite/ignite-aws-ext/
> >
> > Tag:
> >
> > https://github.com/apache/ignite-extensions/releases/tag/ignite-aws-ext-1.0.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://github.com/apache/ignite-extensions/blob/release/ignite-aws-ext-1.0.0/modules/aws-ext/RELEASE_NOTES.txt
> >
> > DEVNOTES:
> > https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
> >
> > Release Checker Results:
> >
> > https://github.com/apache/ignite-extensions/runs/6227581198?check_suite_focus=true
> >
> >
> > == Ignite Azure Extension Module 1.0.0 ==
> >
> > The release candidate is uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-azure-ext-1.0.0-rc1/
> >
> > The following Maven staging can be used:
> >
> > https://repository.apache.org/content/repositories/orgapacheignite-1545/org/apache/ignite/ignite-azure-ext/
> >
> > Tag:
> >
> > https://github.com/apache/ignite-extensions/releases/tag/ignite-azure-ext-1.0.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://github.com/apache/ignite-extensions/blob/release/ignite-azure-ext-1.0.0/modules/azure-ext/RELEASE_NOTES.txt
> >
> > DEVNOTES:
> > https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
> >
> > Release Checker Results:
> >
> > https://github.com/apache/ignite-extensions/runs/6228019576?check_suite_focus=true
> >
> >
> > == Ignite GCE Extension Module 1.0.0 ==
> >
> > The release candidate is uploaded to:
> >
> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-gce-ext-1.0.0-rc1/
> >
> > The following Maven staging can be used:
> >
> > https://repository.apache.org/content/repositories/orgapacheignite-1546/org/apache/ignite/ignite-gce-ext/
> >
> > Tag:
> >
> > https://github.com/apache/ignite-extensions/releases/tag/ignite-gce-ext-1.0.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://github.com/apache/ignite-extensions/blob/release/ignite-gce-ext-1.0.0/modules/gce-ext/RELEASE_NOTES.txt
> >
> > DEVNOTES:
> > https://github.com/apache/ignite-extensions/blob/master/DEVNOTES.md
> >
> > Release Checker Results:
> >
> > https://github.com/apache/ignite-extensions/runs/6228169980?check_suite_focus=true
> >
> >
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept (Ignite AWS 1.0.0 RC1, Ignite Azure 1.0.0 RC1, Ignite
> > GCE 1.0.0 RC1)
> > 0 - don't care either way
> > -1 - DO NOT accept (explain why)
> >
> > See notes on how to verify release here
> > https://www.apache.org/info/verification.html
> > and
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >
> >
> > This vote will be open for at least 7 days till Fri May 7, 2022,
> > 14:00 Moscow TZ. Please, write me down the thread if you need
> > additional time to check the release.
> >
> >
> > https://www.timeanddate.com/countdown/vote?iso=20220507T14=166=%5BVOTE%5D+Release+Ignite+AWS+1.0.0+RC1%2C+Ignite+Azure+1.0.0+RC1%2C+Ignite+GCE+1.0.0+RC1=sanserif
> >



-- 
Best wishes,
Amelchev Nikita

Re: 2.13 and Calcite

[Nikita Amelchev]

The calcite module was manually published to the maven from the
released archives. [1]

The deploy was skipped in a plugin configuration for the calcite
module. The issue was fixed to prevent this in the next releases. [2]

[1] 
https://repo.maven.apache.org/maven2/org/apache/ignite/ignite-calcite/2.13.0/
[2] https://issues.apache.org/jira/browse/IGNITE-16917

пт, 29 апр. 2022 г. в 12:33, Stephen Darlington
:
>
> Excellent, thanks.
>
> > On 29 Apr 2022, at 10:23, Nikita Amelchev  wrote:
> >
> > Hi Stephen,
> >
> > Yes, I know about this. The calcite module was not published to the
> > maven. The problem will be fixed at the nearest time.
> >
> > пт, 29 апр. 2022 г. в 11:50, Stephen Darlington
> > :
> >>
> >> Hi all,
> >>
> >> There’s a question in the user mailing list about the ignite-calcite 
> >> module. It does not appear to be in the Maven repo. Is this a deliberate 
> >> omission — because it’s an experimental feature — or did something go 
> >> wrong with the release?
> >>
> >> Regards,
> >> Stephen
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>


-- 
Best wishes,
Amelchev Nikita

Re: 2.13 and Calcite

[Nikita Amelchev]

Hi Stephen,

Yes, I know about this. The calcite module was not published to the
maven. The problem will be fixed at the nearest time.

пт, 29 апр. 2022 г. в 11:50, Stephen Darlington
:
>
> Hi all,
>
> There’s a question in the user mailing list about the ignite-calcite module. 
> It does not appear to be in the Maven repo. Is this a deliberate omission — 
> because it’s an experimental feature — or did something go wrong with the 
> release?
>
> Regards,
> Stephen



-- 
Best wishes,
Amelchev Nikita

[ANNOUNCE] Apache Ignite 2.13.0 Released

[Nikita Amelchev]

The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.13.0.

Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org

The Apache Ignite community has made a lot of changes in the 2.13.0
release. This blog post will help you to know about some valuable
improvements:
https://blogs.apache.org/ignite/entry/apache-ignite-2-13-0

For the full list of changes, you can refer to the RELEASE_NOTES list
which is trying to catalogue the most significant improvements for
this version of the database:
https://ignite.apache.org/releases/2.13.0/release_notes.html

Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi

Please let us know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask


Regards,
Nikita Amelchev on behalf of the Apache Ignite community.

Re: [DISCUSSION] Move ignite-hibernate modules to the Ignite Extensions

[Nikita Amelchev]

+1

вт, 26 апр. 2022 г. в 17:22, Anton Vinogradov :
>
> +1
>
> On Tue, Apr 26, 2022 at 4:45 PM Николай Ижиков  wrote:
>
> > +1
> >
> > > 26 апр. 2022 г., в 16:24, Maxim Muzafarov 
> > написал(а):
> > >
> > > Hello Igniters,
> > >
> > >
> > > Currently we have a batch of ignite-hibernate modules which provide
> > > Hibernate second-level cache (L2 cache) implementation based on the
> > > Apache Ignite for different version of hibernate.
> > >
> > > The following list of modules we have:
> > > - ignite-hibernate_4.2
> > > - ignite-hibernate_5.1
> > > - ignite-hibernate_5.3
> > > - ignite-hibernate-core (a common part for all hibernate modules)
> > >
> > > I propose to use the same approach as was used for the
> > > ignite-spring-data module [1] and move all these modules to the Ignite
> > > Extesions project.
> > >
> > > In details:
> > >
> > > - remove all these modules from the Ignite project.
> > > - create ignite-hibernate extension.
> > > - move ignite-hibernate-core + ignite-hibernate_4.2 to
> > > release/ignite-hibernate-4.2.0 branch (the version of ignite-hibernate
> > > extension will be 4.2.0) and release it on demand;
> > > - move ignite-hibernate-core + ignite-hibernate_5.1 to
> > > release/ignite-hibernate-5.1.0 branch (the version of ignite-hibernate
> > > extension will be 5.1.0) and release it on demand;
> > > - move ignite-hibernate-core + ignite-hibernate_5.3 to the master
> > > branch and to the release/ignite-hibernate-5.3.0 branch (the version
> > > of ignite-hibernate extension will be 5.3.0) and release it
> > > immediately;
> > >
> > >
> > > Is it OK or am I missing something?
> > > WDYT?
> > >
> > >
> > > [1] https://lists.apache.org/thread/b03bny7xj9x5ty371srtdn9ysd72qht7
> >
> >



-- 
Best wishes,
Amelchev Nikita

[RESULT] [VOTE] Release Apache Ignite 2.13.0 RC2

[Nikita Amelchev]

Dear community,

The release of Apache Ignite 2.13.0 RC2 has been accepted.

Vote result: The vote PASSES with five +1 votes (4 bindings), one +0.5
vote, no 0
votes, and no -1 votes.

+1 votes:
- Zhenya Stanilovsky
- Nikolay Izhikov (binding)
- Ilya Kasnacheev (binding)
- Maxim Muzafarov (binding)
- Alex Plehanov (binding)

+0.5 votes:
- Ivan Daschinsky

The new release will be announced soon.

-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.13.0 RC2

[Nikita Amelchev]

Hi Igniters, PMCs,

Please, verify a new release candidate.

The vote will continue until there are enough votes for a resolution. [1]

[1] https://www.apache.org/foundation/voting.html#ReleaseVotes

пт, 22 апр. 2022 г. в 08:24, Zhenya Stanilovsky :
>
>
> Nikita thanks for your effort !
> Download sources, run examples.
> +1 from me.
>
> >Dear Community,
> >
> >The release candidate is ready.
> >
> >I have uploaded a release candidate to:
> >https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/
> >https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2/
> >
> >The following staging can be used for testing:
> >https://repository.apache.org/content/repositories/orgapacheignite-1542
> >
> >Tag name is 2.13.0-rc1:
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc2
> >
> >RELEASE_NOTES:
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13
> >
> >Complete list of resolved issues:
> >https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> >
> >DEVNOTES:
> >https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13
> >
> >Additional checks have been performed (available for users included
> >into the release group on TeamCity).
> >
> >TC [Check RC: Licenses, compile, chksum]
> >https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6399934
> >
> >TC [2] Compare w/ Previous Release
> >https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6399932
> >
> >The vote is formal, see voting guidelines
> >https://www.apache.org/foundation/voting.html
> >
> >+1 - to accept Apache Ignite 2.13.0-rc2
> >0 - don't care either way
> >-1 - DO NOT accept Apache Ignite Ignite 2.13.0-rc2 (explain why)
> >
> >See notes on how to verify release here
> >https://www.apache.org/info/verification.html
> >and
> >https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >
> >This vote will be open for at least 3 days till Fri Apr 23, 2022,
> >20:00 UTC. Please, write me down the thread if you need additional
> >time to check the
> >release.
> >https://www.timeanddate.com/countdown/vote?iso=20220423T20=0=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC2=sanserif
> >
> >--
> >Best wishes,
> >Amelchev Nikita
>
>
>
>



-- 
Best wishes,
Amelchev Nikita

[DISCUSSION] Update documentation with GitHub Actions

[Nikita Amelchev]

Hello, Igniters.

I propose to add a GitHub action to update documentation for released
Ignite versions by a click. [1]

For now, this is a complex manual work that requires understanding all
the intermediate steps. [2]

New process to update documentation:
1. Commit documentation changes to a released branch.
2. Run the action with a click.
3. Check the result.

Moreover, this will also simplify the process of publishing a new release.

ASF's GitHub Actions Policy allows automated services to push changes
related to documentation. [3]
Write access is required to run the workflow. So, only committers can
run the action. [4]

WDYT? Any objections?

[1] https://issues.apache.org/jira/browse/IGNITE-16895
[2] 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=85461527#HowtoDocument-UpdatingPublishedDocs
[3] https://infra.apache.org/github-actions-policy.html
[4] 
https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow

-- 
Best wishes,
Amelchev Nikita

[VOTE] Release Apache Ignite 2.13.0 RC2

[Nikita Amelchev]

Dear Community,

The release candidate is ready.

I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2/

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

Tag name is 2.13.0-rc1:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc2

RELEASE_NOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13

Complete list of resolved issues:
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

DEVNOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13

Additional checks have been performed (available for users included
into the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6399934

TC [2] Compare w/ Previous Release
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6399932

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

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

See notes on how to verify release here
https://www.apache.org/info/verification.html
and
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open for at least 3 days till Fri Apr 23, 2022,
20:00 UTC. Please, write me down the thread if you need additional
time to check the
release.
https://www.timeanddate.com/countdown/vote?iso=20220423T20=0=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC2=sanserif

-- 
Best wishes,
Amelchev Nikita

Re: Re[4]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Roman, Hi.

The Spring dependency has been updated in the IGNITE-16781 that's in
the 2.13 scope.

ср, 20 апр. 2022 г. в 19:28, Roman Puchkovskiy :
>
> Hi Nikita.
>
> You already know this, just stating for the record: vulnerable Spring
> versions in ignite-extensions were replaced with the latest patched
> (and safe) versions in [1].
>
> [1] - https://issues.apache.org/jira/browse/IGNITE-16869
>
> пн, 18 апр. 2022 г. в 18:11, Nikita Amelchev :
> >
> > Hi, Roman.
> >
> > Vulnerable Spring Boot is used in Ignite extensions. AI 2.13 releases
> > ignite-parent that will be used for extensions to share versions. I
> > will cherry-pick the patch.
> >
> > Thank you.
> >
> > пн, 18 апр. 2022 г. в 15:00, Roman Puchkovskiy 
> > :
> > >
> > > Hi Igniters.
> > >
> > > A fix for CVE-2022-22965 [1] vulnerability was merged to master branch
> > > recently, Jira issue is [2].
> > > I'm not sure whether this is a blocker, but the vulnerability seems to
> > > be pretty bad.
> > >
> > > Should it be cherry-picked to release 2.13?
> > >
> > > [1] - https://nvd.nist.gov/vuln/detail/CVE-2022-22965
> > > [2] - https://issues.apache.org/jira/browse/IGNITE-16781
> > >
> > > пн, 11 апр. 2022 г. в 19:53, Nikita Amelchev :
> > > >
> > > > I'm announcing a code freeze for the 2.13 release [1]. Only blockers
> > > > are accepted to be included to the scope.
> > > >
> > > > [1] 
> > > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > > >
> > > > пн, 28 мар. 2022 г. в 12:39, Nikita Amelchev :
> > > > >
> > > > > Guys,
> > > > >
> > > > > Could you help with the TC bot configuration to the `ignite-2.13`
> > > > > release branch?
> > > > >
> > > > > пн, 28 мар. 2022 г. в 09:22, Zhenya Stanilovsky 
> > > > > :
> > > > >
> > > > > >
> > > > > >
> > > > > > Thanks Nikita, cherry-picked: IGNITE-16742 Extend calcite module 
> > > > > > documentation.
> > > > > >
> > > > > >
> > > > > >
> > > > > > >Igniters,
> > > > > > >
> > > > > > >I have cut the release branch: 'ignite-2.13'. Please, cherry-pick 
> > > > > > >new
> > > > > > >issues if needed.
> > > > > > >
> > > > > > >The 2.13 scope is freezed. Unresolved not-blocking issues will be
> > > > > > >moved on the code freeze stage. The planning release date was 
> > > > > > >updated
> > > > > > >[1]:
> > > > > > >
> > > > > > >Scope Freeze: March 25, 2022
> > > > > > >Code Freeze: April 8, 2022
> > > > > > >Voting Date: April 15, 2022
> > > > > > >Release Date: April 22, 2022
> > > > > > >
> > > > > > >[1]  
> > > > > > >https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > > > > > >
> > > > > > >чт, 10 мар. 2022 г. в 16:17, Nikita Amelchev < 
> > > > > > >namelc...@apache.org >:
> > > > > > >>
> > > > > > >> Hello, Igniters.
> > > > > > >>
> > > > > > >> I have created the 2.13 release page. [1]
> > > > > > >>
> > > > > > >> The new SQL Calcite engine is expected to merge in the coming 
> > > > > > >> week.
> > > > > > >> [2] I suggest cutting the 2.13 branch after the merge. I've 
> > > > > > >> updated
> > > > > > >> the planned release dates on the release page.
> > > > > > >>
> > > > > > >> [1]  
> > > > > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > > > > > >> [2]  
> > > > > > >> https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho
> > > > > > >>
> > > > > > >> чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev < 
> > > > > > >> namelc...@apache.org >:
> > > > > > >> >
> > > > > > >> > Guys,
> > &g

[CANCEL] [VOTE] Release Apache Ignite 2.13.0 RC1

[Nikita Amelchev]

Canceling due to missing the NUMA-allocator library in binaries [1]. I
will prepare RC2 soon.

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

-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.13.0 RC1

[Nikita Amelchev]

Ivan, please create an issue to add to the assembly. I'll
cherry-picked and prepare a new RC.

ср, 20 апр. 2022 г. в 14:45, Ivan Daschinsky :

>
> Seems that somehow numa-allocator is not included in binary releases.
>
> ср, 20 апр. 2022 г. в 14:14, Nikita Amelchev :
>
> > I will make sure this issue is included in the 2.13 documentation. Thanks.
> >
> > ср, 20 апр. 2022 г. в 14:09, 18624049226 <18624049...@163.com>:
> > >
> > > I think the following commit should be included in 2.13:
> > >
> > > IGNITE-15712: Documentation: Invalid documentation about
> > > SqlViewMetricExporterSpi
> > >
> > > just doc issue.
> > >
> > > 在 2022/4/20 16:21, Nikita Amelchev 写道:
> > > > Zhenya, Hi!
> > > >
> > > > Additional checks are available for users included into the release
> > > > group on TeamCity. Make sure you are in this group.
> > > >
> > > > ср, 20 апр. 2022 г. в 09:19, Zhenya
> > Stanilovsky:
> > > >>
> > > >> Nikita, thanks !  I found that below link is unavailable:
> > > >>
> > > >>
> > > >>
> > > >>> TC [2] Compare w/ Previous Release
> > > >>>
> > https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6398741
> > > >>>
> > > >>
> > > >
> > > >
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >
>
>
> --
> Sincerely yours, Ivan Daschinskiy



--
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.13.0 RC1

[Nikita Amelchev]

I will make sure this issue is included in the 2.13 documentation. Thanks.

ср, 20 апр. 2022 г. в 14:09, 18624049226 <18624049...@163.com>:
>
> I think the following commit should be included in 2.13:
>
> IGNITE-15712: Documentation: Invalid documentation about
> SqlViewMetricExporterSpi
>
> just doc issue.
>
> 在 2022/4/20 16:21, Nikita Amelchev 写道:
> > Zhenya, Hi!
> >
> > Additional checks are available for users included into the release
> > group on TeamCity. Make sure you are in this group.
> >
> > ср, 20 апр. 2022 г. в 09:19, Zhenya Stanilovsky:
> >>
> >> Nikita, thanks !  I found that below link is unavailable:
> >>
> >>
> >>
> >>> TC [2] Compare w/ Previous Release
> >>> https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6398741
> >>>
> >>
> >
> >



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.13.0 RC1

[Nikita Amelchev]

Zhenya, Hi!

Additional checks are available for users included into the release
group on TeamCity. Make sure you are in this group.

ср, 20 апр. 2022 г. в 09:19, Zhenya Stanilovsky :
>
>
> Nikita, thanks !  I found that below link is unavailable:
>
>
>
> >TC [2] Compare w/ Previous Release
> >https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6398741
> >
>
>



-- 
Best wishes,
Amelchev Nikita

[VOTE] Release Apache Ignite 2.13.0 RC1

[Nikita Amelchev]

Dear Community,

The release candidate is ready.

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

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

Tag name is 2.13.0-rc1:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc1

RELEASE_NOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13

Complete list of resolved issues:
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

DEVNOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13

Additional checks have been performed (available for users included
into the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6398743

TC [2] Compare w/ Previous Release
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6398741

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

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

See notes on how to verify release here
https://www.apache.org/info/verification.html
and
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open for at least 3 days till Fri Apr 22, 2022,
20:00 UTC. Please,
write me down the thread if you need additional time to check the
release.
https://www.timeanddate.com/countdown/vote?iso=20220422T20=0=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC1=sanserif

-- 
Best wishes,
Amelchev Nikita

Re: Re[4]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hi, Roman.

Vulnerable Spring Boot is used in Ignite extensions. AI 2.13 releases
ignite-parent that will be used for extensions to share versions. I
will cherry-pick the patch.

Thank you.

пн, 18 апр. 2022 г. в 15:00, Roman Puchkovskiy :
>
> Hi Igniters.
>
> A fix for CVE-2022-22965 [1] vulnerability was merged to master branch
> recently, Jira issue is [2].
> I'm not sure whether this is a blocker, but the vulnerability seems to
> be pretty bad.
>
> Should it be cherry-picked to release 2.13?
>
> [1] - https://nvd.nist.gov/vuln/detail/CVE-2022-22965
> [2] - https://issues.apache.org/jira/browse/IGNITE-16781
>
> пн, 11 апр. 2022 г. в 19:53, Nikita Amelchev :
> >
> > I'm announcing a code freeze for the 2.13 release [1]. Only blockers
> > are accepted to be included to the scope.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> >
> > пн, 28 мар. 2022 г. в 12:39, Nikita Amelchev :
> > >
> > > Guys,
> > >
> > > Could you help with the TC bot configuration to the `ignite-2.13`
> > > release branch?
> > >
> > > пн, 28 мар. 2022 г. в 09:22, Zhenya Stanilovsky 
> > > :
> > >
> > > >
> > > >
> > > > Thanks Nikita, cherry-picked: IGNITE-16742 Extend calcite module 
> > > > documentation.
> > > >
> > > >
> > > >
> > > > >Igniters,
> > > > >
> > > > >I have cut the release branch: 'ignite-2.13'. Please, cherry-pick new
> > > > >issues if needed.
> > > > >
> > > > >The 2.13 scope is freezed. Unresolved not-blocking issues will be
> > > > >moved on the code freeze stage. The planning release date was updated
> > > > >[1]:
> > > > >
> > > > >Scope Freeze: March 25, 2022
> > > > >Code Freeze: April 8, 2022
> > > > >Voting Date: April 15, 2022
> > > > >Release Date: April 22, 2022
> > > > >
> > > > >[1]  
> > > > >https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > > > >
> > > > >чт, 10 мар. 2022 г. в 16:17, Nikita Amelchev < namelc...@apache.org >:
> > > > >>
> > > > >> Hello, Igniters.
> > > > >>
> > > > >> I have created the 2.13 release page. [1]
> > > > >>
> > > > >> The new SQL Calcite engine is expected to merge in the coming week.
> > > > >> [2] I suggest cutting the 2.13 branch after the merge. I've updated
> > > > >> the planned release dates on the release page.
> > > > >>
> > > > >> [1]  
> > > > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > > > >> [2]  https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho
> > > > >>
> > > > >> чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev < namelc...@apache.org 
> > > > >> >:
> > > > >> >
> > > > >> > Guys,
> > > > >> >
> > > > >> > +1 to await merge of the Calcite SQL engine before code-freeze 
> > > > >> > phase
> > > > >> > and release branch cutting. Other features and fixes can be awaited
> > > > >> > too, it's discussable.
> > > > >> >
> > > > >> > But the 2.12 branch was cut on October 15, 2021. There are many 
> > > > >> > fixes
> > > > >> > and features that were merged into the master during this period. 
> > > > >> > The
> > > > >> > total time between branches cut is 5 months (if there is no delay
> > > > >> > happens). Seems it is not so frequently.
> > > > >> >
> > > > >> > чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky < 
> > > > >> > arzamas...@mail.ru.invalid >:
> > > > >> > >
> > > > >> > >
> > > > >> > > Maxim, i think that more frequent releases are useful.
> > > > >> > > Ready to release branch means that it passed all known tests and 
> > > > >> > > also have an appropriate votes.
> > > > >> > > More code changes creates more difficulties in final tests and 
> > > > >> > > sometimes migration.
> > > > >> > > No need to 

Re: Re[4]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

I'm announcing a code freeze for the 2.13 release [1]. Only blockers
are accepted to be included to the scope.

[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13

пн, 28 мар. 2022 г. в 12:39, Nikita Amelchev :
>
> Guys,
>
> Could you help with the TC bot configuration to the `ignite-2.13`
> release branch?
>
> пн, 28 мар. 2022 г. в 09:22, Zhenya Stanilovsky :
>
> >
> >
> > Thanks Nikita, cherry-picked: IGNITE-16742 Extend calcite module 
> > documentation.
> >
> >
> >
> > >Igniters,
> > >
> > >I have cut the release branch: 'ignite-2.13'. Please, cherry-pick new
> > >issues if needed.
> > >
> > >The 2.13 scope is freezed. Unresolved not-blocking issues will be
> > >moved on the code freeze stage. The planning release date was updated
> > >[1]:
> > >
> > >Scope Freeze: March 25, 2022
> > >Code Freeze: April 8, 2022
> > >Voting Date: April 15, 2022
> > >Release Date: April 22, 2022
> > >
> > >[1]  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > >
> > >чт, 10 мар. 2022 г. в 16:17, Nikita Amelchev < namelc...@apache.org >:
> > >>
> > >> Hello, Igniters.
> > >>
> > >> I have created the 2.13 release page. [1]
> > >>
> > >> The new SQL Calcite engine is expected to merge in the coming week.
> > >> [2] I suggest cutting the 2.13 branch after the merge. I've updated
> > >> the planned release dates on the release page.
> > >>
> > >> [1]  
> > >> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> > >> [2]  https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho
> > >>
> > >> чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev < namelc...@apache.org >:
> > >> >
> > >> > Guys,
> > >> >
> > >> > +1 to await merge of the Calcite SQL engine before code-freeze phase
> > >> > and release branch cutting. Other features and fixes can be awaited
> > >> > too, it's discussable.
> > >> >
> > >> > But the 2.12 branch was cut on October 15, 2021. There are many fixes
> > >> > and features that were merged into the master during this period. The
> > >> > total time between branches cut is 5 months (if there is no delay
> > >> > happens). Seems it is not so frequently.
> > >> >
> > >> > чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky < 
> > >> > arzamas...@mail.ru.invalid >:
> > >> > >
> > >> > >
> > >> > > Maxim, i think that more frequent releases are useful.
> > >> > > Ready to release branch means that it passed all known tests and 
> > >> > > also have an appropriate votes.
> > >> > > More code changes creates more difficulties in final tests and 
> > >> > > sometimes migration.
> > >> > > No need to switch between neighbor minor versions for user if all 
> > >> > > work properly well.
> > >> > > I «vote» for more frequent releases.
> > >> > >
> > >> > > >
> > >> > > >>
> > >> > > >>>Hi, guys!
> > >> > > >>>
> > >> > > >>>Ignite 2.12 was released on 17th Jan. And here is a plan to 
> > >> > > >>>release 2.13 on
> > >> > > >>>28 Mar. It is only 2.5 months between those versions. IMHO, it's 
> > >> > > >>>better to
> > >> > > >>>have more time between releases:
> > >> > > >>>1. We had some bug reports after releasing 2.11, and it can be 
> > >> > > >>>worth
> > >> > > >>>waiting for users feedback about 2.12. Also meetup with 
> > >> > > >>>description of 2.12
> > >> > > >>>will be only next week (16 Feb).
> > >> > > >>>2. In my understanding, users don't switch between versions of 
> > >> > > >>>databases
> > >> > > >>>frequently. Actually it's hard work to upgrade such a dependency. 
> > >> > > >>>So, no
> > >> > > >>>need for continuous delivery here. I think it's a common 
> > >> > > >>>practice, for
> > >

Re: Re[4]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Guys,

Could you help with the TC bot configuration to the `ignite-2.13`
release branch?

пн, 28 мар. 2022 г. в 09:22, Zhenya Stanilovsky :

>
>
> Thanks Nikita, cherry-picked: IGNITE-16742 Extend calcite module 
> documentation.
>
>
>
> >Igniters,
> >
> >I have cut the release branch: 'ignite-2.13'. Please, cherry-pick new
> >issues if needed.
> >
> >The 2.13 scope is freezed. Unresolved not-blocking issues will be
> >moved on the code freeze stage. The planning release date was updated
> >[1]:
> >
> >Scope Freeze: March 25, 2022
> >Code Freeze: April 8, 2022
> >Voting Date: April 15, 2022
> >Release Date: April 22, 2022
> >
> >[1]  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> >
> >чт, 10 мар. 2022 г. в 16:17, Nikita Amelchev < namelc...@apache.org >:
> >>
> >> Hello, Igniters.
> >>
> >> I have created the 2.13 release page. [1]
> >>
> >> The new SQL Calcite engine is expected to merge in the coming week.
> >> [2] I suggest cutting the 2.13 branch after the merge. I've updated
> >> the planned release dates on the release page.
> >>
> >> [1]  https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> >> [2]  https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho
> >>
> >> чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev < namelc...@apache.org >:
> >> >
> >> > Guys,
> >> >
> >> > +1 to await merge of the Calcite SQL engine before code-freeze phase
> >> > and release branch cutting. Other features and fixes can be awaited
> >> > too, it's discussable.
> >> >
> >> > But the 2.12 branch was cut on October 15, 2021. There are many fixes
> >> > and features that were merged into the master during this period. The
> >> > total time between branches cut is 5 months (if there is no delay
> >> > happens). Seems it is not so frequently.
> >> >
> >> > чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky < 
> >> > arzamas...@mail.ru.invalid >:
> >> > >
> >> > >
> >> > > Maxim, i think that more frequent releases are useful.
> >> > > Ready to release branch means that it passed all known tests and also 
> >> > > have an appropriate votes.
> >> > > More code changes creates more difficulties in final tests and 
> >> > > sometimes migration.
> >> > > No need to switch between neighbor minor versions for user if all work 
> >> > > properly well.
> >> > > I «vote» for more frequent releases.
> >> > >
> >> > > >
> >> > > >>
> >> > > >>>Hi, guys!
> >> > > >>>
> >> > > >>>Ignite 2.12 was released on 17th Jan. And here is a plan to release 
> >> > > >>>2.13 on
> >> > > >>>28 Mar. It is only 2.5 months between those versions. IMHO, it's 
> >> > > >>>better to
> >> > > >>>have more time between releases:
> >> > > >>>1. We had some bug reports after releasing 2.11, and it can be worth
> >> > > >>>waiting for users feedback about 2.12. Also meetup with description 
> >> > > >>>of 2.12
> >> > > >>>will be only next week (16 Feb).
> >> > > >>>2. In my understanding, users don't switch between versions of 
> >> > > >>>databases
> >> > > >>>frequently. Actually it's hard work to upgrade such a dependency. 
> >> > > >>>So, no
> >> > > >>>need for continuous delivery here. I think it's a common practice, 
> >> > > >>>for
> >> > > >>>example, MongoDB releases 1 time per year, Cassandra 2 times. 
> >> > > >>>CockroachDB
> >> > > >>>releases minor versions every month, but major versions are still 
> >> > > >>>released
> >> > > >>>2 times a year. But I'm not aware of all databases.
> >> > > >>>
> >> > > >>>I think we should move dates for at least 1 month. Also it depends 
> >> > > >>>on the
> >> > > >>>Calcite engine readiness. WDYT?
> >> > > >>>
> >> > > >>>Anyway, from my side there are some tickets I want to inclu

Re: Re[2]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Igniters,

I have cut the release branch: 'ignite-2.13'. Please, cherry-pick new
issues if needed.

The 2.13 scope is freezed. Unresolved not-blocking issues will be
moved on the code freeze stage. The planning release date was updated
[1]:

Scope Freeze: March 25, 2022
Code Freeze: April 8, 2022
Voting Date: April 15, 2022
Release Date: April 22, 2022

[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13

чт, 10 мар. 2022 г. в 16:17, Nikita Amelchev :
>
> Hello, Igniters.
>
> I have created the 2.13 release page. [1]
>
> The new SQL Calcite engine is expected to merge in the coming week.
> [2] I suggest cutting the 2.13 branch after the merge. I've updated
> the planned release dates on the release page.
>
> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
> [2] https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho
>
> чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev :
> >
> > Guys,
> >
> > +1 to await merge of the Calcite SQL engine before code-freeze phase
> > and release branch cutting. Other features and fixes can be awaited
> > too, it's discussable.
> >
> > But the 2.12 branch was cut on October 15, 2021. There are many fixes
> > and features that were merged into the master during this period.  The
> > total time between branches cut is 5 months (if there is no delay
> > happens). Seems it is not so frequently.
> >
> > чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky 
> > :
> > >
> > >
> > > Maxim, i think that more frequent releases are useful.
> > > Ready to release branch means that it passed all known tests and also 
> > > have an appropriate votes.
> > > More code changes creates more difficulties in final tests and sometimes 
> > > migration.
> > > No need to switch between neighbor minor versions for user if all work 
> > > properly well.
> > > I «vote»  for more frequent releases.
> > >
> > > >
> > > >>
> > > >>>Hi, guys!
> > > >>>
> > > >>>Ignite 2.12 was released on 17th Jan. And here is a plan to release 
> > > >>>2.13 on
> > > >>>28 Mar. It is only 2.5 months between those versions. IMHO, it's 
> > > >>>better to
> > > >>>have more time between releases:
> > > >>>1. We had some bug reports after releasing 2.11, and it can be worth
> > > >>>waiting for users feedback about 2.12. Also meetup with description of 
> > > >>>2.12
> > > >>>will be only next week (16 Feb).
> > > >>>2. In my understanding, users don't switch between versions of 
> > > >>>databases
> > > >>>frequently. Actually it's hard work to upgrade such a dependency. So, 
> > > >>>no
> > > >>>need for continuous delivery here. I think it's a common practice, for
> > > >>>example, MongoDB releases 1 time per year, Cassandra 2 times. 
> > > >>>CockroachDB
> > > >>>releases minor versions every month, but major versions are still 
> > > >>>released
> > > >>>2 times a year. But I'm not aware of all databases.
> > > >>>
> > > >>>I think we should move dates for at least 1 month. Also it depends on 
> > > >>>the
> > > >>>Calcite engine readiness. WDYT?
> > > >>>
> > > >>>Anyway, from my side there are some tickets I want to include to the 
> > > >>>next
> > > >>>release scope:
> > > >>>1. Partition reservation for cache queries (it will make IndexQuery 
> > > >>>work on
> > > >>>unstable topology): IGNITE-16030 and IGNITE-16031
> > > >>>
> > > >>>2. Also there is a discussion started by Andrey Mashenlov about known 
> > > >>>index
> > > >>>corruption scenarios [1]. It looks like there are at least 2 issues to
> > > >>>resolve: dropping of affinity index, handle of orphaned indexes. I 
> > > >>>think we
> > > >>>should fix those known issues before the next release. WDYT?
> > > >>>
> > > >>>[1]  https://lists.apache.org/thread/m6dt0pn1qb01d8w6zm2fvo7lxgt0r068
> > > >>>
> > > >>>
> > > >>>On Wed, Feb 9, 2022 at 3:13 PM Maxim Muzafarov < mmu...@apache.org > 
> > > >>>wrote:
> > > >>>
> >

Re: [PROPOSAL] Release Calcite-based SQL engine as an experimental feature

[Nikita Amelchev]

Great news!

I will cut the 2.13 release branch soon.

чт, 24 мар. 2022 г. в 18:07, Alex Plehanov :

>
> Hello Igniters,
>
> I've merged the pull request. The Calcite-based SQL engine is in the master
> branch now.
> If you desire to try it, you can find configuration instructions in
> modules/calcite/README.txt file.
>
> вс, 6 мар. 2022 г. в 13:03, Alex Plehanov :
>
> > Hello Igniters,
> >
> > I've prepared the pull request [1] and have plans to merge it to the
> > master branch in about two weeks, if there is no objection.
> >
> > [1]: https://github.com/apache/ignite/pull/9855
> >
> > чт, 30 дек. 2021 г. в 13:43, Anton Vinogradov :
> >
> >> > it would be great to release a new SQL engine in 2.13 as an
> >> experimental feature.
> >> ++1
> >>
> >> On Thu, Dec 30, 2021 at 12:55 PM Alex Plehanov 
> >> wrote:
> >>
> >> > Andrey,
> >> >
> >> > >  Is this [1] a full scope of the tickets that MUST be resolved before
> >> the
> >> > engine could be merged?
> >> > Yes, we must resolve at least these tickets before merging. If you see
> >> any
> >> > other release blockers fill free to attach them to this ticket.
> >> >
> >> > > I think we have to add instructions to the readme file on how to turn
> >> a
> >> > new SQL engine on.
> >> > Sure, I think it should be the part of documentation ticket.
> >> >
> >> > > Also, I don't like the module name "ignite-calcite", because Calcite
> >> is
> >> > an independent project.
> >> > Personally, I see no problems here (but it's discussable). We have a
> >> lot of
> >> > modules where the name is an independent project: "ignite-kafka",
> >> > "ignite-spring", "ignite-kubernetes", "ignite-log4j",
> >> "ignite-zookeeper",
> >> > etc.
> >> >
> >> > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or
> >> > "ignite-sql"?
> >> > Module "ignite-indexing" also contains SQL engine, so names like
> >> > "ignite-sql-engine" or "ignite-sql" will be ambiguous.
> >> >
> >> > чт, 30 дек. 2021 г. в 13:54, Andrey Mashenkov <
> >> andrey.mashen...@gmail.com
> >> > >:
> >> >
> >> > > Alex,
> >> > > it would be great to release a new SQL engine in 2.13 as an
> >> > > experimental feature.
> >> > >
> >> > > Is this [1] a full scope of the tickets that MUST be resolved before
> >> the
> >> > > engine could be merged?
> >> > > I think we have to add instructions to the readme file on how to turn
> >> a
> >> > new
> >> > > SQL engine on.
> >> > >
> >> > > Also, I don't like the module name "ignite-calcite", because Calcite
> >> is
> >> > an
> >> > > independent project.
> >> > > and Ignite just uses it.
> >> > > So, would you mind renaming the module to e.g. "ignite-sql-engine" or
> >> > > "ignite-sql"?
> >> > >
> >> > > [1] https://issues.apache.org/jira/browse/IGNITE-15436
> >> > >
> >> > > On Thu, Dec 30, 2021 at 11:10 AM Zhenya Stanilovsky
> >> > >  wrote:
> >> > >
> >> > > >
> >> > > > Alex, great !
> >> > > > If someone wants to touch codebase somehow plz use this branch [1]
> >> > > > Test passed can be found here [2] [3]
> >> > > >
> >> > > > [1]
> >> https://github.com/apache/ignite/tree/sql-calcite/modules/calcite
> >> > > > [2]
> >> > > >
> >> > >
> >> >
> >> https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/java/org/apache/ignite/internal/processors/query/calcite
> >> > > > [3]
> >> > > >
> >> > >
> >> >
> >> https://github.com/apache/ignite/tree/sql-calcite/modules/calcite/src/test/sql
> >> > > >
> >> > > > >
> >> > > > >>
> >> > > > >>>Hello, Igniters!
> >> > > > >>>
> >> > > > >>>As you may already know there is the new Ignite SQL engine based
> >> on
> >> > > > Apache
> >> > > > >>>Calcite currently under development.
> >> > > > >>>
> >> > > > >>>Reasons to move from H2-based engine and motivation for creating
> >> the
> >> > > new
> >> > > > >>>one in details described in IEP-37 [1].
> >> > > > >>>
> >> > > > >>>You can find all related to the new engine source code changes in
> >> > the
> >> > > > >>>"sql-calcite" branch [2].
> >> > > > >>>
> >> > > > >>>Calcite-based SQL engine is not production-ready yet and has a
> >> lot
> >> > of
> >> > > > known
> >> > > > >>>issues. In the future, the new engine should be fully
> >> independent of
> >> > > > >>>"ignite-indexing" and H2, but now it relies on schema management
> >> and
> >> > > > >>>indexes implemented in the "ignite-indexing" module and can't
> >> work
> >> > > > without
> >> > > > >>>the old engine. Despite all of the above mentioned, in the
> >> current
> >> > > > state,
> >> > > > >>>it has its own parsing, planning and execution flow and is
> >> almost as
> >> > > > >>>functional as the H2-based SQL engine.
> >> > > > >>>
> >> > > > >>>Some users are already interested in the Calcite-based engine and
> >> > > asking
> >> > > > >>>about the development status and release dates. Calcite-based SQL
> >> > > engine
> >> > > > >>>will be the only SQL engine in Ignite 3.0. Perhaps even in 2.x we
> >> > can
> >> > > > get
> >> > > > >>>rid of the H2-based engine at some time in 

Re: Re[2]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Igniters.

I have created the 2.13 release page. [1]

The new SQL Calcite engine is expected to merge in the coming week.
[2] I suggest cutting the 2.13 branch after the merge. I've updated
the planned release dates on the release page.

[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.13
[2] https://lists.apache.org/thread/3fkq3mn2npz326bp6gjtw3sw8xrlqyho

чт, 10 февр. 2022 г. в 15:23, Nikita Amelchev :
>
> Guys,
>
> +1 to await merge of the Calcite SQL engine before code-freeze phase
> and release branch cutting. Other features and fixes can be awaited
> too, it's discussable.
>
> But the 2.12 branch was cut on October 15, 2021. There are many fixes
> and features that were merged into the master during this period.  The
> total time between branches cut is 5 months (if there is no delay
> happens). Seems it is not so frequently.
>
> чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky :
> >
> >
> > Maxim, i think that more frequent releases are useful.
> > Ready to release branch means that it passed all known tests and also have 
> > an appropriate votes.
> > More code changes creates more difficulties in final tests and sometimes 
> > migration.
> > No need to switch between neighbor minor versions for user if all work 
> > properly well.
> > I «vote»  for more frequent releases.
> >
> > >
> > >>
> > >>>Hi, guys!
> > >>>
> > >>>Ignite 2.12 was released on 17th Jan. And here is a plan to release 2.13 
> > >>>on
> > >>>28 Mar. It is only 2.5 months between those versions. IMHO, it's better 
> > >>>to
> > >>>have more time between releases:
> > >>>1. We had some bug reports after releasing 2.11, and it can be worth
> > >>>waiting for users feedback about 2.12. Also meetup with description of 
> > >>>2.12
> > >>>will be only next week (16 Feb).
> > >>>2. In my understanding, users don't switch between versions of databases
> > >>>frequently. Actually it's hard work to upgrade such a dependency. So, no
> > >>>need for continuous delivery here. I think it's a common practice, for
> > >>>example, MongoDB releases 1 time per year, Cassandra 2 times. CockroachDB
> > >>>releases minor versions every month, but major versions are still 
> > >>>released
> > >>>2 times a year. But I'm not aware of all databases.
> > >>>
> > >>>I think we should move dates for at least 1 month. Also it depends on the
> > >>>Calcite engine readiness. WDYT?
> > >>>
> > >>>Anyway, from my side there are some tickets I want to include to the next
> > >>>release scope:
> > >>>1. Partition reservation for cache queries (it will make IndexQuery work 
> > >>>on
> > >>>unstable topology): IGNITE-16030 and IGNITE-16031
> > >>>
> > >>>2. Also there is a discussion started by Andrey Mashenlov about known 
> > >>>index
> > >>>corruption scenarios [1]. It looks like there are at least 2 issues to
> > >>>resolve: dropping of affinity index, handle of orphaned indexes. I think 
> > >>>we
> > >>>should fix those known issues before the next release. WDYT?
> > >>>
> > >>>[1]  https://lists.apache.org/thread/m6dt0pn1qb01d8w6zm2fvo7lxgt0r068
> > >>>
> > >>>
> > >>>On Wed, Feb 9, 2022 at 3:13 PM Maxim Muzafarov < mmu...@apache.org > 
> > >>>wrote:
> > >>>
> > >>>> Nikita,
> > >>>>
> > >>>> Thank you for starting this thread.
> > >>>> +1 for these dates, but I think it's better to start the code freeze
> > >>>> date when the Calcite engine will be actually merged to the master
> > >>>> branch.
> > >>>>
> > >>>> On Tue, 8 Feb 2022 at 13:10, Nikita Amelchev < namelc...@apache.org > 
> > >>>> wrote:
> > >>>> >
> > >>>> > Dear Ignite Community!
> > >>>> >
> > >>>> > I suggest starting Apache Ignite 2.13 release activities.
> > >>>> >
> > >>>> > There is a plan to merge the new Calcite SQL engine. [1] I think that
> > >>>> > 2.13 is a good candidate for it.
> > >>>> >
> > >>>> > Moreover, we've accumulated a hundred resolved [2] issues with ne

Re: [DISCUSSION] Exclude ignite-log4j, log4j 1.2.17

[Nikita Amelchev]

+1 to deprecate the 'ignite-log4j' module and remove it in the next releases.

вт, 1 мар. 2022 г. в 20:40, Sergei Ryzhov :
>
> Anton, Nikolay thanks.
>
> With this ticket[1] I change the default logger to ignite-log4j2
> And I will mark log4j as deprecated.
>
> before the review, I will check on the TC-bot and check on the Ducktests.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-16626
>
> пн, 28 февр. 2022 г. в 19:10, Anton Vinogradov :
>
> > > But, seems, we can’t do it right now, because of existing deployments.
> > Correct
> >
> > > Let’s mark this module as deprecated and remove it in 2.14?
> > Possible way
> >
> > Also, we must check this will not cause problems at tests (eg. Ducktests)
> >
> > On Mon, Feb 28, 2022 at 6:48 PM Nikolay Izhikov 
> > wrote:
> >
> > > Hello, Anton.
> > >
> > > +1 to remove outdated logging library.
> > >
> > > But, seems, we can’t do it right now, because of existing deployments.
> > > Let’s mark this module as deprecated and remove it in 2.14?
> > >
> > >
> > > > Not every deployment require to be secured.
> > >
> > > Disagree.
> > > We should update or workaround known security issues ASAP.
> > >
> > >
> > > > Not every deployment requires to use of log4j.
> > >
> > >
> > >
> > > Agree, but we shouldn’t provide or support modules with known security
> > > issues.
> > >
> > >
> > > > 28 февр. 2022 г., в 18:41, Anton Vinogradov 
> > написал(а):
> > > >
> > > > Your deployment has vulnerabilities only in case you configured log4j
> > as
> > > a
> > > > logger.
> > > > Not every deployment require to be secured.
> > > > Not every deployment requires to use of log4j.
> > > >
> > > > We must change the default logging library if the current is log4j and
> > > > provide the ability to use log4j as before (where it is required) but
> > > with
> > > > a warning, I think.
> > > >
> > > > On Mon, Feb 28, 2022 at 3:55 PM Sergei Ryzhov 
> > > wrote:
> > > >
> > > >> Hello, Igniters.
> > > >>
> > > >> log4j 1.2.17 is not supported and contains critical vulnerabilities
> > > >> I suggest excluding log4j 1.2.17 and module ignite-log4j from
> > ignite[1].
> > > >>
> > > >> Direct vulnerabilities:
> > > >> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23305
> > > >> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23302
> > > >> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-4104
> > > >> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17571
> > > >>
> > > >> WDYT?
> > > >>
> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-16626
> > > >>
> > > >> --
> > > >> Best regards,
> > > >> Sergei Ryzhov
> > > >>
> > >
> > >
> >
>
>
> --
> Best regards,
> Sergei Ryzhov



-- 
Best wishes,
Amelchev Nikita

Re: [ANNOUNCE] Welcome Pavel Pereslegin as a new committer

[Nikita Amelchev]

My congratulations, Pavel!

чт, 10 февр. 2022 г. в 18:53, Дмитрий Сорокин :
>
> Great job Pavel, my congrats!
>
>
> Чт, 10 февр. 2022 г. в 18:29, Nikolay Izhikov :
>
> > Great news! Congratulations!
> >
> > > 10 февр. 2022 г., в 18:26, Maksim Timonin 
> > написал(а):
> > >
> > > Hi Pavel,
> > >
> > > Congratulations!
> > >
> > > On Thu, Feb 10, 2022 at 6:16 PM Maxim Muzafarov 
> > wrote:
> > >
> > >> The Project Management Committee (PMC) for Apache Ignite has invited
> > >> Pavel Pereslegin to become a committer and we are pleased to announce
> > that
> > >> he has accepted.
> > >>
> > >> He made a lot of major contributions to the Apache Ignite codebase
> > >> like a snapshot restore procedure, batch update operation to the
> > >> PageMemory, TDE cache key rotation procedure, Service context
> > >> injection and etc.
> > >>
> > >> Being a committer enables easier contribution to the project since
> > there is
> > >> no need to go via the patch submission process. This should enable
> > better
> > >> productivity.
> > >>
> > >> Please join me in welcoming Pavel, and congratulating him on the new
> > role
> > >> in
> > >> the Apache Ignite Community.
> > >>
> > >>
> > >> Best Regards,
> > >> Maxim Muzafarov
> > >>
> >
> >



-- 
Best wishes,
Amelchev Nikita

Re: Re[2]: Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Guys,

+1 to await merge of the Calcite SQL engine before code-freeze phase
and release branch cutting. Other features and fixes can be awaited
too, it's discussable.

But the 2.12 branch was cut on October 15, 2021. There are many fixes
and features that were merged into the master during this period.  The
total time between branches cut is 5 months (if there is no delay
happens). Seems it is not so frequently.

чт, 10 февр. 2022 г. в 15:17, Zhenya Stanilovsky :
>
>
> Maxim, i think that more frequent releases are useful.
> Ready to release branch means that it passed all known tests and also have an 
> appropriate votes.
> More code changes creates more difficulties in final tests and sometimes 
> migration.
> No need to switch between neighbor minor versions for user if all work 
> properly well.
> I «vote»  for more frequent releases.
>
> >
> >>
> >>>Hi, guys!
> >>>
> >>>Ignite 2.12 was released on 17th Jan. And here is a plan to release 2.13 on
> >>>28 Mar. It is only 2.5 months between those versions. IMHO, it's better to
> >>>have more time between releases:
> >>>1. We had some bug reports after releasing 2.11, and it can be worth
> >>>waiting for users feedback about 2.12. Also meetup with description of 2.12
> >>>will be only next week (16 Feb).
> >>>2. In my understanding, users don't switch between versions of databases
> >>>frequently. Actually it's hard work to upgrade such a dependency. So, no
> >>>need for continuous delivery here. I think it's a common practice, for
> >>>example, MongoDB releases 1 time per year, Cassandra 2 times. CockroachDB
> >>>releases minor versions every month, but major versions are still released
> >>>2 times a year. But I'm not aware of all databases.
> >>>
> >>>I think we should move dates for at least 1 month. Also it depends on the
> >>>Calcite engine readiness. WDYT?
> >>>
> >>>Anyway, from my side there are some tickets I want to include to the next
> >>>release scope:
> >>>1. Partition reservation for cache queries (it will make IndexQuery work on
> >>>unstable topology): IGNITE-16030 and IGNITE-16031
> >>>
> >>>2. Also there is a discussion started by Andrey Mashenlov about known index
> >>>corruption scenarios [1]. It looks like there are at least 2 issues to
> >>>resolve: dropping of affinity index, handle of orphaned indexes. I think we
> >>>should fix those known issues before the next release. WDYT?
> >>>
> >>>[1]  https://lists.apache.org/thread/m6dt0pn1qb01d8w6zm2fvo7lxgt0r068
> >>>
> >>>
> >>>On Wed, Feb 9, 2022 at 3:13 PM Maxim Muzafarov < mmu...@apache.org > wrote:
> >>>
> >>>> Nikita,
> >>>>
> >>>> Thank you for starting this thread.
> >>>> +1 for these dates, but I think it's better to start the code freeze
> >>>> date when the Calcite engine will be actually merged to the master
> >>>> branch.
> >>>>
> >>>> On Tue, 8 Feb 2022 at 13:10, Nikita Amelchev < namelc...@apache.org > 
> >>>> wrote:
> >>>> >
> >>>> > Dear Ignite Community!
> >>>> >
> >>>> > I suggest starting Apache Ignite 2.13 release activities.
> >>>> >
> >>>> > There is a plan to merge the new Calcite SQL engine. [1] I think that
> >>>> > 2.13 is a good candidate for it.
> >>>> >
> >>>> > Moreover, we've accumulated a hundred resolved [2] issues with new
> >>>> > features and bug fixes which are waiting for their release date. For
> >>>> > example,
> >>>> >
> >>>> > BinaryArray introduced,
> >>>> > Read Repair strategies implemented,
> >>>> > CPP Thin: asynchronous network events handling,
> >>>> > NUMA-aware allocator for data regions
> >>>> > etc.
> >>>> >
> >>>> > I want to propose myself to be the release manager of the planning
> >>>> release.
> >>>> >
> >>>> > I propose the following timeline:
> >>>> >
> >>>> > Scope Freeze: February 21, 2022
> >>>> > Code Freeze: March 7, 2022
> >>>> > Voting Date: March 21, 2022
> >>>> > Release Date: March 28, 2022
> >>>> >
> >>>> > WDYT?
> >>>> >
> >>>> > [1]  https://issues.apache.org/jira/browse/IGNITE-15436
> >>>> > [2]
> >>>>  
> >>>> https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> >>>> >
> >>>> > --
> >>>> > Best wishes,
> >>>> > Amelchev Nikita
> >>>>
> >>
> >>
> >>
> >>



-- 
Best wishes,
Amelchev Nikita

Apache Ignite 2.13 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Dear Ignite Community!

I suggest starting Apache Ignite 2.13 release activities.

There is a plan to merge the new Calcite SQL engine. [1] I think that
2.13 is a good candidate for it.

Moreover, we've accumulated a hundred resolved [2] issues with new
features and bug fixes which are waiting for their release date. For
example,

BinaryArray introduced,
Read Repair strategies implemented,
CPP Thin: asynchronous network events handling,
NUMA-aware allocator for data regions
etc.

I want to propose myself to be the release manager of the planning release.

I propose the following timeline:

Scope Freeze: February 21, 2022
Code Freeze: March 7, 2022
Voting Date: March 21, 2022
Release Date: March 28, 2022

WDYT?

[1] https://issues.apache.org/jira/browse/IGNITE-15436
[2] 
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

-- 
Best wishes,
Amelchev Nikita

[ANNOUNCE] Apache Ignite 2.12.0 Released

[Nikita Amelchev]

The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.12.0.

Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org

The Apache Ignite community has made a lot of changes in the 2.12.0
release. This blog post will help you to know about some valuable
improvements:
https://blogs.apache.org/ignite/entry/apache-ignite-2-12-0

For the full list of changes, you can refer to the RELEASE_NOTES list
which is trying to catalogue the most significant improvements for
this version of the database:
https://ignite.apache.org/releases/2.12.0/release_notes.html

Download the latest Ignite version from here:
https://ignite.apache.org/download.cgi

Please let us know if you encounter any problems:
https://ignite.apache.org/community/resources.html#ask


Regards,
Nikita Amelchev on behalf of the Apache Ignite community.

[RESULT] [VOTE] Release Apache Ignite 2.12.0 RC2

[Nikita Amelchev]

Dear community,

The release of Apache Ignite 2.12.0 RC2 has been accepted.

Vote result: The vote PASSES with seven +1 votes (5 bindings), no 0
votes, and no -1 votes.

+1 votes:
- Pavel Tupitsyn (binding)
- Valentin Kulichenko (binding)
- Vladimir Steshin
- Nikolay Izhikov (binding)
- Maxim Muzafarov (binding)
- Anton Vinogradov (binding)
- Ivan Daschinsky

The new release will be announced soon.

-- 
Best wishes,
Amelchev Nikita

[VOTE] Release Apache Ignite 2.12.0 RC2

[Nikita Amelchev]

Dear Community,

The release candidate (2.12.0-rc2) is ready.

I have uploaded a release candidate to:
https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc2/
https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc2/

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

Tag name is 2.12.0-rc2:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc2

RELEASE_NOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12

Complete list of resolved issues:
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

DEVNOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12

Additional checks have been performed (available for users included
into the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6266150?showRootCauses=false=true

TC [2] Compare w/ Previous Release
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6266148?showRootCauses=false=true

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

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

See notes on how to verify release here
https://www.apache.org/info/verification.html
and
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open until Thu Jan 13, 2022, 16:00 UTC. Please,
write me down the thread if you need additional time to check the
release.
https://www.timeanddate.com/countdown/vote?iso=20220113T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC2=sanserif

-- 
Best wishes,
Amelchev Nikita

[CANCEL] [VOTE] Release Apache Ignite 2.12.0 RC1

[Nikita Amelchev]

Canceling due to vulnerable log2j version [1]. I will prepare RC2 soon.

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

-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Release Apache Ignite 2.12.0 RC1

[Nikita Amelchev]

I think this is a blocker. I will cancel the vote and cherrypick the fix [1].

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

сб, 1 янв. 2022 г. в 19:39, Ivan Daschinsky :
>
> -0.5. We should update log4j2 to version 2.17.1
>
> пт, 31 дек. 2021 г., 00:43 Nikita Amelchev :
>
> > Dear Community,
> >
> > The release candidate is ready.
> >
> > I have uploaded a release candidate to:
> > https://dist.apache.org/repos/dist/dev/ignite/2.12.0-rc1/
> > https://dist.apache.org/repos/dist/dev/ignite/packages_2.12.0-rc1/
> >
> > The following staging can be used for testing:
> > https://repository.apache.org/content/repositories/orgapacheignite-1538
> >
> > Tag name is 2.12.0-rc1:
> >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc1
> >
> > RELEASE_NOTES:
> >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12
> >
> > Complete list of resolved issues:
> >
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority
> >
> > DEVNOTES:
> >
> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12
> >
> > Additional checks have been performed (available for users included
> > into the release group on TeamCity).
> >
> > TC [Check RC: Licenses, compile, chksum]
> >
> > https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6253654?showRootCauses=false=true
> >
> > TC [2] Compare w/ Previous Release
> >
> > https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6253662?showRootCauses=false
> >
> > The vote is formal, see voting guidelines
> > https://www.apache.org/foundation/voting.html
> >
> > +1 - to accept Apache Ignite 2.12.0-rc1
> > 0 - don't care either way
> > -1 - DO NOT accept Apache Ignite Ignite 2.12.0-rc1 (explain why)
> >
> > See notes on how to verify release here
> > https://www.apache.org/info/verification.html
> > and
> >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification
> >
> > This vote will be open until Mon Jan 10, 2022, 16:00 UTC.
> > The voting time was increased due to the long NY weekend. Please,
> > write me down the thread if you need additional time to check the
> > release.
> >
> > https://www.timeanddate.com/countdown/vote?iso=20220110T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC1=sanserif
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >



-- 
Best wishes,
Amelchev Nikita

[VOTE] Release Apache Ignite 2.12.0 RC1

[Nikita Amelchev]

Dear Community,

The release candidate is ready.

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

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

Tag name is 2.12.0-rc1:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.12.0-rc1

RELEASE_NOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.12

Complete list of resolved issues:
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority

DEVNOTES:
https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.12

Additional checks have been performed (available for users included
into the release group on TeamCity).

TC [Check RC: Licenses, compile, chksum]
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6253654?showRootCauses=false=true

TC [2] Compare w/ Previous Release
https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6253662?showRootCauses=false

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

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

See notes on how to verify release here
https://www.apache.org/info/verification.html
and
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification

This vote will be open until Mon Jan 10, 2022, 16:00 UTC.
The voting time was increased due to the long NY weekend. Please,
write me down the thread if you need additional time to check the
release.
https://www.timeanddate.com/countdown/vote?iso=20220110T16=0=VOTE+on+the+Apache+Ignite+Release+2.12.0+RC1=sanserif

-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Pavel, thank you.

The "[3] Build & Upload Nuget Staging Packages" configuration also
pushes packages to the MyGet.
Will packages be published to some package registry?

чт, 30 дек. 2021 г. в 10:15, Pavel Tupitsyn :
>
> NuGet packages are now prepared as part of the main config "[1] Release 
> Build".
> They are placed to svn/vote/apache-ignite-2.12.0-nuget.zip [1]
>
> I propose to remove "[3] Build & Upload Nuget Staging Packages" configuration.
> NuGet packages can be downloaded from vote artifacts and verified locally by 
> installing from a folder:
> dotnet add package Apache.Ignite --source ~/Downloads/and/so/on
>
> Thoughts, objections?
>
> [1] 
> https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_ReleaseBuild/6347367?buildTab=artifacts#%2Frelease-2.12.0-rc1.zip!%2Fpackages;%2Frelease-2.12.0-rc1.zip!%2Fsvn%2Fvote%2Fapache-ignite-2.12.0-nuget.zip
>
> On Thu, Dec 30, 2021 at 9:29 AM Pavel Tupitsyn  wrote:
>>
>> Hello Nikita,
>>
>> I'll have a look.
>>
>> On Wed, Dec 29, 2021 at 6:12 PM Nikita Amelchev  wrote:
>>>
>>> Hello. Petr, Pavel,
>>>
>>> It seems that the release profile to build the Nuget package was
>>> broken. Could you please help with fixing it?
>>>
>>> [1] 
>>> https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/6347635
>>>
>>> вс, 26 дек. 2021 г. в 16:29, Nikita Amelchev :
>>> >
>>> > Igniters,
>>> >
>>> > There are two issues left to release 2.12:
>>> >
>>> > 1. The log4j dependency update in the REST module. The fix is leaving
>>> > only the slf4j facade for third-party libraries and allowing a user to
>>> > configure the underlying logging framework yourself. [1]
>>> >
>>> > 2. Migration zookeeper-ip-finder to the extensions [2] (and then
>>> > update log4j dependency) as discussed in the thread [3].
>>> >
>>> > Please, join the review. I have a plan to merge it at the nearest time
>>> > and prepare RC.
>>> >
>>> > Also, I suggest including issues [4, 5] that block the snapshot restore 
>>> > process.
>>> >
>>> > [1] https://issues.apache.org/jira/browse/IGNITE-13464
>>> > [2] https://issues.apache.org/jira/browse/IGNITE-16182
>>> > [3] https://lists.apache.org/thread/bdt9yoy3so9p26ymox3rxh45vk85toc5
>>> > [4] https://issues.apache.org/jira/browse/IGNITE-16194
>>> > [5] https://issues.apache.org/jira/browse/IGNITE-16177
>>> >
>>> > вт, 21 дек. 2021 г. в 13:34, Ivan Daschinsky :
>>> > >
>>> > > Also, zookeeper ip finder depends on good old log4j 1.x
>>> > >
>>> > > вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky :
>>> > >
>>> > > > As for me, I am +1 for removing ZookeeperIpFinder from 
>>> > > > ignite-zookeeper.
>>> > > >
>>> > > >
>>> > > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev :
>>> > > >
>>> > > >> Folks,
>>> > > >>
>>> > > >> What do you think about fixing vulnerability log4j dependencies in
>>> > > >> rest-http, zookeeper modules in 2.12?
>>> > > >>
>>> > > >> The issue is in progress and can be resolved in a few days. [1]
>>> > > >>
>>> > > >> I suggest including it to the scope.
>>> > > >>
>>> > > >> [1] https://issues.apache.org/jira/browse/IGNITE-13464
>>> > > >>
>>> > > >> пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин 
>>> > > >> >> > > >> >:
>>> > > >> >
>>> > > >> > Hi Nikita,
>>> > > >> >
>>> > > >> > The proposed timeline looks great. Thank you!
>>> > > >> >
>>> > > >> > Slava.
>>> > > >> >
>>> > > >> > пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev 
>>> > > >> > :
>>> > > >> >
>>> > > >> > > Hello, Slava.
>>> > > >> > >
>>> > > >> > > I am planning the following timeline:
>>> > > >> > >
>>> > > >> > > Voting Date: December 20, 2021
>>

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello. Petr, Pavel,

It seems that the release profile to build the Nuget package was
broken. Could you please help with fixing it?

[1] 
https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages/6347635

вс, 26 дек. 2021 г. в 16:29, Nikita Amelchev :
>
> Igniters,
>
> There are two issues left to release 2.12:
>
> 1. The log4j dependency update in the REST module. The fix is leaving
> only the slf4j facade for third-party libraries and allowing a user to
> configure the underlying logging framework yourself. [1]
>
> 2. Migration zookeeper-ip-finder to the extensions [2] (and then
> update log4j dependency) as discussed in the thread [3].
>
> Please, join the review. I have a plan to merge it at the nearest time
> and prepare RC.
>
> Also, I suggest including issues [4, 5] that block the snapshot restore 
> process.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-13464
> [2] https://issues.apache.org/jira/browse/IGNITE-16182
> [3] https://lists.apache.org/thread/bdt9yoy3so9p26ymox3rxh45vk85toc5
> [4] https://issues.apache.org/jira/browse/IGNITE-16194
> [5] https://issues.apache.org/jira/browse/IGNITE-16177
>
> вт, 21 дек. 2021 г. в 13:34, Ivan Daschinsky :
> >
> > Also, zookeeper ip finder depends on good old log4j 1.x
> >
> > вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky :
> >
> > > As for me, I am +1 for removing ZookeeperIpFinder from ignite-zookeeper.
> > >
> > >
> > > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev :
> > >
> > >> Folks,
> > >>
> > >> What do you think about fixing vulnerability log4j dependencies in
> > >> rest-http, zookeeper modules in 2.12?
> > >>
> > >> The issue is in progress and can be resolved in a few days. [1]
> > >>
> > >> I suggest including it to the scope.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-13464
> > >>
> > >> пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин  > >> >:
> > >> >
> > >> > Hi Nikita,
> > >> >
> > >> > The proposed timeline looks great. Thank you!
> > >> >
> > >> > Slava.
> > >> >
> > >> > пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev :
> > >> >
> > >> > > Hello, Slava.
> > >> > >
> > >> > > I am planning the following timeline:
> > >> > >
> > >> > > Voting Date: December 20, 2021
> > >> > > Release Date: December 27, 2021
> > >> > >
> > >> > > чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин <
> > >> slava.kopti...@gmail.com>:
> > >> > > >
> > >> > > > Hello Nikita,
> > >> > > >
> > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates the
> > >> log4j
> > >> > > > version to 2.16.
> > >> > > > Thanks a lot!
> > >> > > >
> > >> > > > Could you please share a current timeline for the rest steps
> > >> related to
> > >> > > the
> > >> > > > release?
> > >> > > >
> > >> > > > Thanks,
> > >> > > > S.
> > >> > > >
> > >> > > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev  > >> >:
> > >> > > >
> > >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates the
> > >> log4j
> > >> > > > > version to 2.16.
> > >> > > > >
> > >> > > > > Slava, thank you.
> > >> > > > >
> > >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16127
> > >> > > > >
> > >> > > > > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин <
> > >> > > slava.kopti...@gmail.com>:
> > >> > > > > >
> > >> > > > > > Hello,
> > >> > > > > >
> > >> > > > > > Nikita, it seems that we have to add the following ticket
> > >> > > > > > https://issues.apache.org/jira/browse/IGNITE-16127 to Apache
> > >> Ignite
> > >> > > 2.12
> > >> > > > > > release.
> > >> > > > > >
> > >> > > > >

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Igniters,

There are two issues left to release 2.12:

1. The log4j dependency update in the REST module. The fix is leaving
only the slf4j facade for third-party libraries and allowing a user to
configure the underlying logging framework yourself. [1]

2. Migration zookeeper-ip-finder to the extensions [2] (and then
update log4j dependency) as discussed in the thread [3].

Please, join the review. I have a plan to merge it at the nearest time
and prepare RC.

Also, I suggest including issues [4, 5] that block the snapshot restore process.

[1] https://issues.apache.org/jira/browse/IGNITE-13464
[2] https://issues.apache.org/jira/browse/IGNITE-16182
[3] https://lists.apache.org/thread/bdt9yoy3so9p26ymox3rxh45vk85toc5
[4] https://issues.apache.org/jira/browse/IGNITE-16194
[5] https://issues.apache.org/jira/browse/IGNITE-16177

вт, 21 дек. 2021 г. в 13:34, Ivan Daschinsky :
>
> Also, zookeeper ip finder depends on good old log4j 1.x
>
> вт, 21 дек. 2021 г. в 13:32, Ivan Daschinsky :
>
> > As for me, I am +1 for removing ZookeeperIpFinder from ignite-zookeeper.
> >
> >
> > вт, 21 дек. 2021 г. в 13:26, Nikita Amelchev :
> >
> >> Folks,
> >>
> >> What do you think about fixing vulnerability log4j dependencies in
> >> rest-http, zookeeper modules in 2.12?
> >>
> >> The issue is in progress and can be resolved in a few days. [1]
> >>
> >> I suggest including it to the scope.
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-13464
> >>
> >> пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин  >> >:
> >> >
> >> > Hi Nikita,
> >> >
> >> > The proposed timeline looks great. Thank you!
> >> >
> >> > Slava.
> >> >
> >> > пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev :
> >> >
> >> > > Hello, Slava.
> >> > >
> >> > > I am planning the following timeline:
> >> > >
> >> > > Voting Date: December 20, 2021
> >> > > Release Date: December 27, 2021
> >> > >
> >> > > чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин <
> >> slava.kopti...@gmail.com>:
> >> > > >
> >> > > > Hello Nikita,
> >> > > >
> >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates the
> >> log4j
> >> > > > version to 2.16.
> >> > > > Thanks a lot!
> >> > > >
> >> > > > Could you please share a current timeline for the rest steps
> >> related to
> >> > > the
> >> > > > release?
> >> > > >
> >> > > > Thanks,
> >> > > > S.
> >> > > >
> >> > > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev  >> >:
> >> > > >
> >> > > > > I have cherry-picked the issue [1] to the 2.12. It updates the
> >> log4j
> >> > > > > version to 2.16.
> >> > > > >
> >> > > > > Slava, thank you.
> >> > > > >
> >> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16127
> >> > > > >
> >> > > > > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин <
> >> > > slava.kopti...@gmail.com>:
> >> > > > > >
> >> > > > > > Hello,
> >> > > > > >
> >> > > > > > Nikita, it seems that we have to add the following ticket
> >> > > > > > https://issues.apache.org/jira/browse/IGNITE-16127 to Apache
> >> Ignite
> >> > > 2.12
> >> > > > > > release.
> >> > > > > >
> >> > > > > > Thanks,
> >> > > > > > S.
> >> > > > > >
> >> > > > > >
> >> > > > > > вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev <
> >> namelc...@apache.org>:
> >> > > > > >
> >> > > > > > > +1 to move these auth issues to the next release. I will
> >> prepare
> >> > > RC at
> >> > > > > > > the nearest time.
> >> > > > > > >
> >> > > > > > > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn <
> >> ptupit...@apache.org
> >> > > >:
> >> > > > > > > >
> >> > > > > > > > Agree wit

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Folks,

What do you think about fixing vulnerability log4j dependencies in
rest-http, zookeeper modules in 2.12?

The issue is in progress and can be resolved in a few days. [1]

I suggest including it to the scope.

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

пт, 17 дек. 2021 г. в 16:22, Вячеслав Коптилин :
>
> Hi Nikita,
>
> The proposed timeline looks great. Thank you!
>
> Slava.
>
> пт, 17 дек. 2021 г. в 15:32, Nikita Amelchev :
>
> > Hello, Slava.
> >
> > I am planning the following timeline:
> >
> > Voting Date: December 20, 2021
> > Release Date: December 27, 2021
> >
> > чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин :
> > >
> > > Hello Nikita,
> > >
> > > > I have cherry-picked the issue [1] to the 2.12. It updates the log4j
> > > version to 2.16.
> > > Thanks a lot!
> > >
> > > Could you please share a current timeline for the rest steps related to
> > the
> > > release?
> > >
> > > Thanks,
> > > S.
> > >
> > > ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev :
> > >
> > > > I have cherry-picked the issue [1] to the 2.12. It updates the log4j
> > > > version to 2.16.
> > > >
> > > > Slava, thank you.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-16127
> > > >
> > > > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин <
> > slava.kopti...@gmail.com>:
> > > > >
> > > > > Hello,
> > > > >
> > > > > Nikita, it seems that we have to add the following ticket
> > > > > https://issues.apache.org/jira/browse/IGNITE-16127 to Apache Ignite
> > 2.12
> > > > > release.
> > > > >
> > > > > Thanks,
> > > > > S.
> > > > >
> > > > >
> > > > > вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev :
> > > > >
> > > > > > +1 to move these auth issues to the next release. I will prepare
> > RC at
> > > > > > the nearest time.
> > > > > >
> > > > > > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn  > >:
> > > > > > >
> > > > > > > Agree with Nikolay, let's proceed with the release.
> > > > > > >
> > > > > > > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov <
> > nizhi...@apache.org
> > > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > Nikita.
> > > > > > > >
> > > > > > > > I don’t think IGNITE-16068 is a release blocker.
> > > > > > > >
> > > > > > > > 1. It only happens when authentication enabled.
> > > > > > > > 2. There is at lease 2 workarounds:
> > > > > > > > a. Use the same file.encoding for all Ignite nodes.
> > > > > > > > b. Use only latin characters in user login.
> > > > > > > >
> > > > > > > > I propose to postpone this ticket and move on with the release.
> > > > > > > >
> > > > > > > > > 13 дек. 2021 г., в 15:28, Nikita Amelchev <
> > namelc...@apache.org>
> > > > > > > > написал(а):
> > > > > > > > >
> > > > > > > > > Hello.
> > > > > > > > >
> > > > > > > > > I have cherry-picked the blocked [1] to the 2.12. It updates
> > the
> > > > > > log4j
> > > > > > > > > version to 2.15.
> > > > > > > > >
> > > > > > > > > The release is blocked by one blocker issue with auth.
> > > > > > > > >
> > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16101
> > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-16068
> > > > > > > > >
> > > > > > > > > чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev <
> > > > namelc...@apache.org>:
> > > > > > > > >>
> > > > > > > > >> Hello, Nikolay.
> > > > > > > > >>
> > > > > > > > >> I have cherry-picked the issue fix.
> > > > > > > > >

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Slava.

I am planning the following timeline:

Voting Date: December 20, 2021
Release Date: December 27, 2021

чт, 16 дек. 2021 г. в 11:52, Вячеслав Коптилин :
>
> Hello Nikita,
>
> > I have cherry-picked the issue [1] to the 2.12. It updates the log4j
> version to 2.16.
> Thanks a lot!
>
> Could you please share a current timeline for the rest steps related to the
> release?
>
> Thanks,
> S.
>
> ср, 15 дек. 2021 г. в 21:45, Nikita Amelchev :
>
> > I have cherry-picked the issue [1] to the 2.12. It updates the log4j
> > version to 2.16.
> >
> > Slava, thank you.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-16127
> >
> > ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин :
> > >
> > > Hello,
> > >
> > > Nikita, it seems that we have to add the following ticket
> > > https://issues.apache.org/jira/browse/IGNITE-16127 to Apache Ignite 2.12
> > > release.
> > >
> > > Thanks,
> > > S.
> > >
> > >
> > > вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev :
> > >
> > > > +1 to move these auth issues to the next release. I will prepare RC at
> > > > the nearest time.
> > > >
> > > > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn :
> > > > >
> > > > > Agree with Nikolay, let's proceed with the release.
> > > > >
> > > > > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov  > >
> > > > wrote:
> > > > >
> > > > > > Nikita.
> > > > > >
> > > > > > I don’t think IGNITE-16068 is a release blocker.
> > > > > >
> > > > > > 1. It only happens when authentication enabled.
> > > > > > 2. There is at lease 2 workarounds:
> > > > > > a. Use the same file.encoding for all Ignite nodes.
> > > > > > b. Use only latin characters in user login.
> > > > > >
> > > > > > I propose to postpone this ticket and move on with the release.
> > > > > >
> > > > > > > 13 дек. 2021 г., в 15:28, Nikita Amelchev 
> > > > > > написал(а):
> > > > > > >
> > > > > > > Hello.
> > > > > > >
> > > > > > > I have cherry-picked the blocked [1] to the 2.12. It updates the
> > > > log4j
> > > > > > > version to 2.15.
> > > > > > >
> > > > > > > The release is blocked by one blocker issue with auth.
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16101
> > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-16068
> > > > > > >
> > > > > > > чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev <
> > namelc...@apache.org>:
> > > > > > >>
> > > > > > >> Hello, Nikolay.
> > > > > > >>
> > > > > > >> I have cherry-picked the issue fix.
> > > > > > >>
> > > > > > >> Thank you.
> > > > > > >>
> > > > > > >> ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov <
> > nizhi...@apache.org>:
> > > > > > >>>
> > > > > > >>> Hello.
> > > > > > >>>
> > > > > > >>> Let’s include [1] in 2.12 scope.
> > > > > > >>>
> > > > > > >>> After migrations authentication processor to security API we
> > have
> > > > an
> > > > > > issue.
> > > > > > >>> Persistent data region should exists on client node if
> > > > authentication
> > > > > > is enabled.
> > > > > > >>>
> > > > > > >>> It seems very annoying for the users.
> > > > > > >>>
> > > > > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15969
> > > > > > >>>
> > > > > > >>>> 2 дек. 2021 г., в 19:50, Nikita Amelchev <
> > namelc...@apache.org>
> > > > > > написал(а):
> > > > > > >>>>
> > > > > > >>>> I would like to formally announce code freeze for 2.12.0. Only
> > > > > > >>>> blockers are accepted to

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

I have cherry-picked the issue [1] to the 2.12. It updates the log4j
version to 2.16.

Slava, thank you.

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

ср, 15 дек. 2021 г. в 14:14, Вячеслав Коптилин :
>
> Hello,
>
> Nikita, it seems that we have to add the following ticket
> https://issues.apache.org/jira/browse/IGNITE-16127 to Apache Ignite 2.12
> release.
>
> Thanks,
> S.
>
>
> вт, 14 дек. 2021 г. в 09:54, Nikita Amelchev :
>
> > +1 to move these auth issues to the next release. I will prepare RC at
> > the nearest time.
> >
> > пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn :
> > >
> > > Agree with Nikolay, let's proceed with the release.
> > >
> > > On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov 
> > wrote:
> > >
> > > > Nikita.
> > > >
> > > > I don’t think IGNITE-16068 is a release blocker.
> > > >
> > > > 1. It only happens when authentication enabled.
> > > > 2. There is at lease 2 workarounds:
> > > > a. Use the same file.encoding for all Ignite nodes.
> > > > b. Use only latin characters in user login.
> > > >
> > > > I propose to postpone this ticket and move on with the release.
> > > >
> > > > > 13 дек. 2021 г., в 15:28, Nikita Amelchev 
> > > > написал(а):
> > > > >
> > > > > Hello.
> > > > >
> > > > > I have cherry-picked the blocked [1] to the 2.12. It updates the
> > log4j
> > > > > version to 2.15.
> > > > >
> > > > > The release is blocked by one blocker issue with auth.
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16101
> > > > > [2] https://issues.apache.org/jira/browse/IGNITE-16068
> > > > >
> > > > > чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev :
> > > > >>
> > > > >> Hello, Nikolay.
> > > > >>
> > > > >> I have cherry-picked the issue fix.
> > > > >>
> > > > >> Thank you.
> > > > >>
> > > > >> ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov :
> > > > >>>
> > > > >>> Hello.
> > > > >>>
> > > > >>> Let’s include [1] in 2.12 scope.
> > > > >>>
> > > > >>> After migrations authentication processor to security API we have
> > an
> > > > issue.
> > > > >>> Persistent data region should exists on client node if
> > authentication
> > > > is enabled.
> > > > >>>
> > > > >>> It seems very annoying for the users.
> > > > >>>
> > > > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15969
> > > > >>>
> > > > >>>> 2 дек. 2021 г., в 19:50, Nikita Amelchev 
> > > > написал(а):
> > > > >>>>
> > > > >>>> I would like to formally announce code freeze for 2.12.0. Only
> > > > >>>> blockers are accepted to be included to the scope. [1]
> > > > >>>>
> > > > >>>> We have one blocker issue [2] that will be fixed soon.
> > > > >>>>
> > > > >>>> [1]
> > > >
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
> > > > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > >>>>
> > > > >>>> чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev  > >:
> > > > >>>>>
> > > > >>>>> Hi, Igniters.
> > > > >>>>>
> > > > >>>>> The release is blocked by the auth issue [1] discussed above. The
> > > > >>>>> patch will be prepared at the nearest time.
> > > > >>>>>
> > > > >>>>> I want to include the useful issue that adds the ability to
> > configure
> > > > >>>>> snapshot thread pool size if nobody minds.
> > > > >>>>>
> > > > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > >>>>> [2] https://issues.apache.org/jira/browse/IGNITE-16014
> > > > >>>>>
> > > > >>>>> пт, 26 нояб. 20

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

+1 to move these auth issues to the next release. I will prepare RC at
the nearest time.

пн, 13 дек. 2021 г. в 16:13, Pavel Tupitsyn :
>
> Agree with Nikolay, let's proceed with the release.
>
> On Mon, Dec 13, 2021 at 3:31 PM Nikolay Izhikov  wrote:
>
> > Nikita.
> >
> > I don’t think IGNITE-16068 is a release blocker.
> >
> > 1. It only happens when authentication enabled.
> > 2. There is at lease 2 workarounds:
> > a. Use the same file.encoding for all Ignite nodes.
> > b. Use only latin characters in user login.
> >
> > I propose to postpone this ticket and move on with the release.
> >
> > > 13 дек. 2021 г., в 15:28, Nikita Amelchev 
> > написал(а):
> > >
> > > Hello.
> > >
> > > I have cherry-picked the blocked [1] to the 2.12. It updates the log4j
> > > version to 2.15.
> > >
> > > The release is blocked by one blocker issue with auth.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-16101
> > > [2] https://issues.apache.org/jira/browse/IGNITE-16068
> > >
> > > чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev :
> > >>
> > >> Hello, Nikolay.
> > >>
> > >> I have cherry-picked the issue fix.
> > >>
> > >> Thank you.
> > >>
> > >> ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov :
> > >>>
> > >>> Hello.
> > >>>
> > >>> Let’s include [1] in 2.12 scope.
> > >>>
> > >>> After migrations authentication processor to security API we have an
> > issue.
> > >>> Persistent data region should exists on client node if authentication
> > is enabled.
> > >>>
> > >>> It seems very annoying for the users.
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-15969
> > >>>
> > >>>> 2 дек. 2021 г., в 19:50, Nikita Amelchev 
> > написал(а):
> > >>>>
> > >>>> I would like to formally announce code freeze for 2.12.0. Only
> > >>>> blockers are accepted to be included to the scope. [1]
> > >>>>
> > >>>> We have one blocker issue [2] that will be fixed soon.
> > >>>>
> > >>>> [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
> > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > >>>>
> > >>>> чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev :
> > >>>>>
> > >>>>> Hi, Igniters.
> > >>>>>
> > >>>>> The release is blocked by the auth issue [1] discussed above. The
> > >>>>> patch will be prepared at the nearest time.
> > >>>>>
> > >>>>> I want to include the useful issue that adds the ability to configure
> > >>>>> snapshot thread pool size if nobody minds.
> > >>>>>
> > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15966
> > >>>>> [2] https://issues.apache.org/jira/browse/IGNITE-16014
> > >>>>>
> > >>>>> пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev  > >:
> > >>>>>>
> > >>>>>> Hello,
> > >>>>>>
> > >>>>>> I want to include the issue [1] to the 2.12 scope. It fixes some
> > >>>>>> metrics according to the JSR107.
> > >>>>>>
> > >>>>>> Any objections?
> > >>>>>>
> > >>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
> > >>>>>> cache method should update statistics if the method returns true
> > >>>>>>
> > >>>>>> чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev  > >:
> > >>>>>>>
> > >>>>>>> Hello Ivan,
> > >>>>>>>
> > >>>>>>> +1, the issue can be cherry-picked to the 2.12.
> > >>>>>>>
> > >>>>>>> чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov  > >:
> > >>>>>>>>
> > >>>>>>>> Hello everyone,
> > >>>>>>>>
> > >>>>>>>> is there a chance to add this issue to the release scope? [1]
&

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello.

I have cherry-picked the blocked [1] to the 2.12. It updates the log4j
version to 2.15.

The release is blocked by one blocker issue with auth.

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

чт, 9 дек. 2021 г. в 12:44, Nikita Amelchev :
>
> Hello, Nikolay.
>
> I have cherry-picked the issue fix.
>
> Thank you.
>
> ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov :
> >
> > Hello.
> >
> > Let’s include [1] in 2.12 scope.
> >
> > After migrations authentication processor to security API we have an issue.
> > Persistent data region should exists on client node if authentication is 
> > enabled.
> >
> > It seems very annoying for the users.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15969
> >
> > > 2 дек. 2021 г., в 19:50, Nikita Amelchev  
> > > написал(а):
> > >
> > > I would like to formally announce code freeze for 2.12.0. Only
> > > blockers are accepted to be included to the scope. [1]
> > >
> > > We have one blocker issue [2] that will be fixed soon.
> > >
> > > [1] 
> > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
> > > [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > >
> > > чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev :
> > >>
> > >> Hi, Igniters.
> > >>
> > >> The release is blocked by the auth issue [1] discussed above. The
> > >> patch will be prepared at the nearest time.
> > >>
> > >> I want to include the useful issue that adds the ability to configure
> > >> snapshot thread pool size if nobody minds.
> > >>
> > >> [1] https://issues.apache.org/jira/browse/IGNITE-15966
> > >> [2] https://issues.apache.org/jira/browse/IGNITE-16014
> > >>
> > >> пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev :
> > >>>
> > >>> Hello,
> > >>>
> > >>> I want to include the issue [1] to the 2.12 scope. It fixes some
> > >>> metrics according to the JSR107.
> > >>>
> > >>> Any objections?
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
> > >>> cache method should update statistics if the method returns true
> > >>>
> > >>> чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev :
> > >>>>
> > >>>> Hello Ivan,
> > >>>>
> > >>>> +1, the issue can be cherry-picked to the 2.12.
> > >>>>
> > >>>> чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
> > >>>>>
> > >>>>> Hello everyone,
> > >>>>>
> > >>>>> is there a chance to add this issue to the release scope? [1]
> > >>>>> Currently, defragmentation of certain types of indexes can corrupt 
> > >>>>> them.
> > >>>>> Fix is straightforward and should not cause any problems.
> > >>>>> Thank you!
> > >>>>>
> > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15968
> > >>>>>
> > >>>>> вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev :
> > >>>>>
> > >>>>>> Ivan,
> > >>>>>>
> > >>>>>> I have cherry-picked the issue:
> > >>>>>> https://issues.apache.org/jira/browse/IGNITE-15767
> > >>>>>>
> > >>>>>> вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
> > >>>>>>>
> > >>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > >>>>>>>
> > >>>>>>> Cherry-picked to 2.12
> > >>>>>>>
> > >>>>>>>> 23 нояб. 2021 г., в 16:38, Nikita Amelchev 
> > >>>>>> написал(а):
> > >>>>>>>>
> > >>>>>>>> Hi, +1 to cherry-pick.
> > >>>>>>>>
> > >>>>>>>> вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky 
> > >>>>>>>> :
> > >>>>>>>>>
> > >>>>>>>>> Hi! Lets add one simple bug fix, but very useful
> > >>>>>>>>>
> > >>>>>>>&

Re: 0-day CVE in log4j

[Nikita Amelchev]

Hello.

The issue to update dependency was created:
https://issues.apache.org/jira/browse/IGNITE-16101

I want to include it to the 2.12 scope.

сб, 11 дек. 2021 г., 09:19 Raymond Wilson :

> All
>
> This blew up today: CVE-2021-44228 (
>
> https://www.bleepingcomputer.com/news/security/new-zero-day-exploit-for-log4j-java-library-is-an-enterprise-nightmare/
> )
>
> Will there be a risk assessment with respect to Ignite for this CVE?
>
> Thanks,
> Raymond.
>
> --
> 
> Raymond Wilson
> Trimble Distinguished Engineer, Civil Construction Software (CCS)
> 11 Birmingham Drive | Christchurch, New Zealand
> raymond_wil...@trimble.com
>
> <
> https://worksos.trimble.com/?utm_source=Trimble_medium=emailsign_campaign=Launch
> >
>

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Nikolay.

I have cherry-picked the issue fix.

Thank you.

ср, 8 дек. 2021 г. в 18:47, Nikolay Izhikov :
>
> Hello.
>
> Let’s include [1] in 2.12 scope.
>
> After migrations authentication processor to security API we have an issue.
> Persistent data region should exists on client node if authentication is 
> enabled.
>
> It seems very annoying for the users.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15969
>
> > 2 дек. 2021 г., в 19:50, Nikita Amelchev  написал(а):
> >
> > I would like to formally announce code freeze for 2.12.0. Only
> > blockers are accepted to be included to the scope. [1]
> >
> > We have one blocker issue [2] that will be fixed soon.
> >
> > [1] 
> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
> > [2] https://issues.apache.org/jira/browse/IGNITE-15966
> >
> > чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev :
> >>
> >> Hi, Igniters.
> >>
> >> The release is blocked by the auth issue [1] discussed above. The
> >> patch will be prepared at the nearest time.
> >>
> >> I want to include the useful issue that adds the ability to configure
> >> snapshot thread pool size if nobody minds.
> >>
> >> [1] https://issues.apache.org/jira/browse/IGNITE-15966
> >> [2] https://issues.apache.org/jira/browse/IGNITE-16014
> >>
> >> пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev :
> >>>
> >>> Hello,
> >>>
> >>> I want to include the issue [1] to the 2.12 scope. It fixes some
> >>> metrics according to the JSR107.
> >>>
> >>> Any objections?
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
> >>> cache method should update statistics if the method returns true
> >>>
> >>> чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev :
> >>>>
> >>>> Hello Ivan,
> >>>>
> >>>> +1, the issue can be cherry-picked to the 2.12.
> >>>>
> >>>> чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
> >>>>>
> >>>>> Hello everyone,
> >>>>>
> >>>>> is there a chance to add this issue to the release scope? [1]
> >>>>> Currently, defragmentation of certain types of indexes can corrupt them.
> >>>>> Fix is straightforward and should not cause any problems.
> >>>>> Thank you!
> >>>>>
> >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15968
> >>>>>
> >>>>> вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev :
> >>>>>
> >>>>>> Ivan,
> >>>>>>
> >>>>>> I have cherry-picked the issue:
> >>>>>> https://issues.apache.org/jira/browse/IGNITE-15767
> >>>>>>
> >>>>>> вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
> >>>>>>>
> >>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> >>>>>>>
> >>>>>>> Cherry-picked to 2.12
> >>>>>>>
> >>>>>>>> 23 нояб. 2021 г., в 16:38, Nikita Amelchev 
> >>>>>> написал(а):
> >>>>>>>>
> >>>>>>>> Hi, +1 to cherry-pick.
> >>>>>>>>
> >>>>>>>> вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky :
> >>>>>>>>>
> >>>>>>>>> Hi! Lets add one simple bug fix, but very useful
> >>>>>>>>>
> >>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-15767
> >>>>>>>>>
> >>>>>>>>> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn :
> >>>>>>>>>
> >>>>>>>>>> Yes, let's fix those auth issues, there are so many complaints on
> >>>>>> the user
> >>>>>>>>>> list.
> >>>>>>>>>>
> >>>>>>>>>> On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov <
> >>>>>> pmgheap@gmail.com>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> Igniters,
> >>>>>>>>>>> it seems that issues [1] a

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

I would like to formally announce code freeze for 2.12.0. Only
blockers are accepted to be included to the scope. [1]

We have one blocker issue [2] that will be fixed soon.

[1] 
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P3.Stabilization
[2] https://issues.apache.org/jira/browse/IGNITE-15966

чт, 2 дек. 2021 г. в 16:01, Nikita Amelchev :
>
> Hi, Igniters.
>
> The release is blocked by the auth issue [1] discussed above. The
> patch will be prepared at the nearest time.
>
> I want to include the useful issue that adds the ability to configure
> snapshot thread pool size if nobody minds.
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15966
> [2] https://issues.apache.org/jira/browse/IGNITE-16014
>
> пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev :
> >
> > Hello,
> >
> > I want to include the issue [1] to the 2.12 scope. It fixes some
> > metrics according to the JSR107.
> >
> > Any objections?
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
> > cache method should update statistics if the method returns true
> >
> > чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev :
> > >
> > > Hello Ivan,
> > >
> > > +1, the issue can be cherry-picked to the 2.12.
> > >
> > > чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
> > > >
> > > > Hello everyone,
> > > >
> > > > is there a chance to add this issue to the release scope? [1]
> > > > Currently, defragmentation of certain types of indexes can corrupt them.
> > > > Fix is straightforward and should not cause any problems.
> > > > Thank you!
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-15968
> > > >
> > > > вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev :
> > > >
> > > > > Ivan,
> > > > >
> > > > > I have cherry-picked the issue:
> > > > > https://issues.apache.org/jira/browse/IGNITE-15767
> > > > >
> > > > > вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
> > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > > > >
> > > > > > Cherry-picked to 2.12
> > > > > >
> > > > > > > 23 нояб. 2021 г., в 16:38, Nikita Amelchev 
> > > > > написал(а):
> > > > > > >
> > > > > > > Hi, +1 to cherry-pick.
> > > > > > >
> > > > > > > вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky 
> > > > > > > :
> > > > > > >>
> > > > > > >> Hi! Lets add one simple bug fix, but very useful
> > > > > > >>
> > > > > > >> https://issues.apache.org/jira/browse/IGNITE-15767
> > > > > > >>
> > > > > > >> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn 
> > > > > > >> :
> > > > > > >>
> > > > > > >>> Yes, let's fix those auth issues, there are so many complaints 
> > > > > > >>> on
> > > > > the user
> > > > > > >>> list.
> > > > > > >>>
> > > > > > >>> On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov <
> > > > > pmgheap@gmail.com>
> > > > > > >>> wrote:
> > > > > > >>>
> > > > > > >>>> Igniters,
> > > > > > >>>> it seems that issues [1] and [2] that were discovered recently 
> > > > > > >>>> are
> > > > > > >>>> blockers for the 2.12 release.
> > > > > > >>>>
> > > > > > >>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > > > > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > > > >>>>
> > > > > > >>>> On 22.11.2021 11:04, Nikolay Izhikov wrote:
> > > > > > >>>>> Hello.
> > > > > > >>>>>
> > > > > > >>>>> One more tiny fix that will improve java thin client 
> > > > > > >>>>> performance in
> > > > > > >>>> certain cases [1]
> > > > > > >>>>> I think it worth to cherry-pick

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hi, Igniters.

The release is blocked by the auth issue [1] discussed above. The
patch will be prepared at the nearest time.

I want to include the useful issue that adds the ability to configure
snapshot thread pool size if nobody minds.

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

пт, 26 нояб. 2021 г. в 11:44, Nikita Amelchev :
>
> Hello,
>
> I want to include the issue [1] to the 2.12 scope. It fixes some
> metrics according to the JSR107.
>
> Any objections?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
> cache method should update statistics if the method returns true
>
> чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev :
> >
> > Hello Ivan,
> >
> > +1, the issue can be cherry-picked to the 2.12.
> >
> > чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
> > >
> > > Hello everyone,
> > >
> > > is there a chance to add this issue to the release scope? [1]
> > > Currently, defragmentation of certain types of indexes can corrupt them.
> > > Fix is straightforward and should not cause any problems.
> > > Thank you!
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-15968
> > >
> > > вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev :
> > >
> > > > Ivan,
> > > >
> > > > I have cherry-picked the issue:
> > > > https://issues.apache.org/jira/browse/IGNITE-15767
> > > >
> > > > вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
> > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > > >
> > > > > Cherry-picked to 2.12
> > > > >
> > > > > > 23 нояб. 2021 г., в 16:38, Nikita Amelchev 
> > > > написал(а):
> > > > > >
> > > > > > Hi, +1 to cherry-pick.
> > > > > >
> > > > > > вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky :
> > > > > >>
> > > > > >> Hi! Lets add one simple bug fix, but very useful
> > > > > >>
> > > > > >> https://issues.apache.org/jira/browse/IGNITE-15767
> > > > > >>
> > > > > >> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn 
> > > > > >> :
> > > > > >>
> > > > > >>> Yes, let's fix those auth issues, there are so many complaints on
> > > > the user
> > > > > >>> list.
> > > > > >>>
> > > > > >>> On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov <
> > > > pmgheap@gmail.com>
> > > > > >>> wrote:
> > > > > >>>
> > > > > >>>> Igniters,
> > > > > >>>> it seems that issues [1] and [2] that were discovered recently 
> > > > > >>>> are
> > > > > >>>> blockers for the 2.12 release.
> > > > > >>>>
> > > > > >>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > > > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > > >>>>
> > > > > >>>> On 22.11.2021 11:04, Nikolay Izhikov wrote:
> > > > > >>>>> Hello.
> > > > > >>>>>
> > > > > >>>>> One more tiny fix that will improve java thin client 
> > > > > >>>>> performance in
> > > > > >>>> certain cases [1]
> > > > > >>>>> I think it worth to cherry-pick it to 2.12 release.
> > > > > >>>>>
> > > > > >>>>> Any objections?
> > > > > >>>>>
> > > > > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15924
> > > > > >>>>>
> > > > > >>>>>> 19 нояб. 2021 г., в 14:56, Nikita Amelchev 
> > > > > >>>>>> 
> > > > > >>>> написал(а):
> > > > > >>>>>>
> > > > > >>>>>> Vladimir, +1.
> > > > > >>>>>>
> > > > > >>>>>> I have cherry-picked the issue.
> > > > > >>>>>>
> > > > > >>>>>> пт, 19 нояб. 2021 г. в 14:53, Steshin V

Re: [ANNOUNCE] Welcome Maxim Timonin as a new committer

[Nikita Amelchev]

Hi Maxim,

My congratulations!

пн, 29 нояб. 2021 г. в 19:57, Zhenya Stanilovsky :
>
>
>
> Big deal, congrats Maxim !
>
>
> >Igniters,
> >
> >The Project Management Committee (PMC) for Apache Ignite has invited Maxim
> >Timonin to become a committer and we are pleased to announce that he has
> >accepted.
> >
> >Maxim makes valuable contributions to the Apache Ignite code, helps
> >actively to applications developers on the user list, and made a good start
> >in Project awareness contributing by presenting at Ignite Summit: Cloud
> >Edition.
> >
> >Being a committer enables easier contribution to the project since there is
> >no need to go via the patch submission process. This should enable better
> >productivity.
> >
> >Please join me in welcoming Maxim, and congratulating him on the new role
> >in the Apache Ignite Community!
> >
> >Kseniya Romanova
> >on behalf of Apache Ignite PMC
>
>
>
>



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello,

I want to include the issue [1] to the 2.12 scope. It fixes some
metrics according to the JSR107.

Any objections?

[1] https://issues.apache.org/jira/browse/IGNITE-16002 The remove
cache method should update statistics if the method returns true

чт, 25 нояб. 2021 г. в 17:12, Nikita Amelchev :
>
> Hello Ivan,
>
> +1, the issue can be cherry-picked to the 2.12.
>
> чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
> >
> > Hello everyone,
> >
> > is there a chance to add this issue to the release scope? [1]
> > Currently, defragmentation of certain types of indexes can corrupt them.
> > Fix is straightforward and should not cause any problems.
> > Thank you!
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15968
> >
> > вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev :
> >
> > > Ivan,
> > >
> > > I have cherry-picked the issue:
> > > https://issues.apache.org/jira/browse/IGNITE-15767
> > >
> > > вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
> > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > >
> > > > Cherry-picked to 2.12
> > > >
> > > > > 23 нояб. 2021 г., в 16:38, Nikita Amelchev 
> > > написал(а):
> > > > >
> > > > > Hi, +1 to cherry-pick.
> > > > >
> > > > > вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky :
> > > > >>
> > > > >> Hi! Lets add one simple bug fix, but very useful
> > > > >>
> > > > >> https://issues.apache.org/jira/browse/IGNITE-15767
> > > > >>
> > > > >> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn :
> > > > >>
> > > > >>> Yes, let's fix those auth issues, there are so many complaints on
> > > the user
> > > > >>> list.
> > > > >>>
> > > > >>> On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov <
> > > pmgheap@gmail.com>
> > > > >>> wrote:
> > > > >>>
> > > > >>>> Igniters,
> > > > >>>> it seems that issues [1] and [2] that were discovered recently are
> > > > >>>> blockers for the 2.12 release.
> > > > >>>>
> > > > >>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > > >>>>
> > > > >>>> On 22.11.2021 11:04, Nikolay Izhikov wrote:
> > > > >>>>> Hello.
> > > > >>>>>
> > > > >>>>> One more tiny fix that will improve java thin client performance 
> > > > >>>>> in
> > > > >>>> certain cases [1]
> > > > >>>>> I think it worth to cherry-pick it to 2.12 release.
> > > > >>>>>
> > > > >>>>> Any objections?
> > > > >>>>>
> > > > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15924
> > > > >>>>>
> > > > >>>>>> 19 нояб. 2021 г., в 14:56, Nikita Amelchev 
> > > > >>>> написал(а):
> > > > >>>>>>
> > > > >>>>>> Vladimir, +1.
> > > > >>>>>>
> > > > >>>>>> I have cherry-picked the issue.
> > > > >>>>>>
> > > > >>>>>> пт, 19 нояб. 2021 г. в 14:53, Steshin Vladimir <
> > > vlads...@gmail.com>:
> > > > >>>>>>> Hi all.
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> Let's add simple and useful thin-client-pool monitoring in
> > > 2.12:
> > > > >>>>>>>
> > > > >>>>>>> https://issues.apache.org/jira/browse/IGNITE-15183
> > > > >>>>>>>
> > > > >>>>>>> https://github.com/apache/ignite/pull/9525
> > > > >>>>>>>
> > > > >>>>>>>
> > > > >>>>>>> 19.11.2021 09:50, Maksim Timonin пишет:
> > > > >>>>>>>> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects
> > > users
> > > > 

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello Ivan,

+1, the issue can be cherry-picked to the 2.12.

чт, 25 нояб. 2021 г. в 17:07, Ivan Bessonov :
>
> Hello everyone,
>
> is there a chance to add this issue to the release scope? [1]
> Currently, defragmentation of certain types of indexes can corrupt them.
> Fix is straightforward and should not cause any problems.
> Thank you!
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15968
>
> вт, 23 нояб. 2021 г. в 20:44, Nikita Amelchev :
>
> > Ivan,
> >
> > I have cherry-picked the issue:
> > https://issues.apache.org/jira/browse/IGNITE-15767
> >
> > вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
> > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > >
> > > Cherry-picked to 2.12
> > >
> > > > 23 нояб. 2021 г., в 16:38, Nikita Amelchev 
> > написал(а):
> > > >
> > > > Hi, +1 to cherry-pick.
> > > >
> > > > вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky :
> > > >>
> > > >> Hi! Lets add one simple bug fix, but very useful
> > > >>
> > > >> https://issues.apache.org/jira/browse/IGNITE-15767
> > > >>
> > > >> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn :
> > > >>
> > > >>> Yes, let's fix those auth issues, there are so many complaints on
> > the user
> > > >>> list.
> > > >>>
> > > >>> On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov <
> > pmgheap@gmail.com>
> > > >>> wrote:
> > > >>>
> > > >>>> Igniters,
> > > >>>> it seems that issues [1] and [2] that were discovered recently are
> > > >>>> blockers for the 2.12 release.
> > > >>>>
> > > >>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > > >>>>
> > > >>>> On 22.11.2021 11:04, Nikolay Izhikov wrote:
> > > >>>>> Hello.
> > > >>>>>
> > > >>>>> One more tiny fix that will improve java thin client performance in
> > > >>>> certain cases [1]
> > > >>>>> I think it worth to cherry-pick it to 2.12 release.
> > > >>>>>
> > > >>>>> Any objections?
> > > >>>>>
> > > >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15924
> > > >>>>>
> > > >>>>>> 19 нояб. 2021 г., в 14:56, Nikita Amelchev 
> > > >>>> написал(а):
> > > >>>>>>
> > > >>>>>> Vladimir, +1.
> > > >>>>>>
> > > >>>>>> I have cherry-picked the issue.
> > > >>>>>>
> > > >>>>>> пт, 19 нояб. 2021 г. в 14:53, Steshin Vladimir <
> > vlads...@gmail.com>:
> > > >>>>>>> Hi all.
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> Let's add simple and useful thin-client-pool monitoring in
> > 2.12:
> > > >>>>>>>
> > > >>>>>>> https://issues.apache.org/jira/browse/IGNITE-15183
> > > >>>>>>>
> > > >>>>>>> https://github.com/apache/ignite/pull/9525
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> 19.11.2021 09:50, Maksim Timonin пишет:
> > > >>>>>>>> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects
> > users
> > > >>> of
> > > >>>>>>>> metrics in case there are too many partitions (> 2), we
> > observed
> > > >>>>>>>> extensive heap usage.
> > > >>>>>>>>
> > > >>>>>>>> [1] https://github.com/apache/ignite/pull/9518/files
> > > >>>>>>>> [2] https://issues.apache.org/jira/browse/IGNITE-15781
> > > >>>>>>>>
> > > >>>>>>>> On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin <
> > > >>>> timonin.ma...@gmail.com>
> > > >>>>>>>> wrote:
> > > >>>>>>>>
> > > >>

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Ivan,

I have cherry-picked the issue:
https://issues.apache.org/jira/browse/IGNITE-15767

вт, 23 нояб. 2021 г. в 20:31, Nikolay Izhikov :
>
> > [1] https://issues.apache.org/jira/browse/IGNITE-15951
>
> Cherry-picked to 2.12
>
> > 23 нояб. 2021 г., в 16:38, Nikita Amelchev  
> > написал(а):
> >
> > Hi, +1 to cherry-pick.
> >
> > вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky :
> >>
> >> Hi! Lets add one simple bug fix, but very useful
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-15767
> >>
> >> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn :
> >>
> >>> Yes, let's fix those auth issues, there are so many complaints on the user
> >>> list.
> >>>
> >>> On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov 
> >>> wrote:
> >>>
> >>>> Igniters,
> >>>> it seems that issues [1] and [2] that were discovered recently are
> >>>> blockers for the 2.12 release.
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/IGNITE-15951
> >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15966
> >>>>
> >>>> On 22.11.2021 11:04, Nikolay Izhikov wrote:
> >>>>> Hello.
> >>>>>
> >>>>> One more tiny fix that will improve java thin client performance in
> >>>> certain cases [1]
> >>>>> I think it worth to cherry-pick it to 2.12 release.
> >>>>>
> >>>>> Any objections?
> >>>>>
> >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15924
> >>>>>
> >>>>>> 19 нояб. 2021 г., в 14:56, Nikita Amelchev 
> >>>> написал(а):
> >>>>>>
> >>>>>> Vladimir, +1.
> >>>>>>
> >>>>>> I have cherry-picked the issue.
> >>>>>>
> >>>>>> пт, 19 нояб. 2021 г. в 14:53, Steshin Vladimir :
> >>>>>>> Hi all.
> >>>>>>>
> >>>>>>>
> >>>>>>> Let's add simple and useful thin-client-pool monitoring in 2.12:
> >>>>>>>
> >>>>>>> https://issues.apache.org/jira/browse/IGNITE-15183
> >>>>>>>
> >>>>>>> https://github.com/apache/ignite/pull/9525
> >>>>>>>
> >>>>>>>
> >>>>>>> 19.11.2021 09:50, Maksim Timonin пишет:
> >>>>>>>> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users
> >>> of
> >>>>>>>> metrics in case there are too many partitions (> 2), we observed
> >>>>>>>> extensive heap usage.
> >>>>>>>>
> >>>>>>>> [1] https://github.com/apache/ignite/pull/9518/files
> >>>>>>>> [2] https://issues.apache.org/jira/browse/IGNITE-15781
> >>>>>>>>
> >>>>>>>> On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin <
> >>>> timonin.ma...@gmail.com>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will
> >>>> fix it
> >>>>>>>>> in 1-2 days.
> >>>>>>>>>
> >>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-15943
> >>>>>>>>>
> >>>>>>>>> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov  >>>>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>>> Folks,
> >>>>>>>>>>
> >>>>>>>>>> I've fixed almost all the review comments [1]. Hopefully, the
> >>>> changes
> >>>>>>>>>> will be merged by the end of the week.
> >>>>>>>>>>
> >>>>>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-14744
> >>>>>>>>>>
> >>>>>>>>>> On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev <
> >>> namelc...@apache.org>
> >>>>>>>>>> wrote:
> >>>>>>>>>>> Hello, Pavel.
> >>>>>>>>>>>
> >>>>>>>>>

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hi, +1 to cherry-pick.

вт, 23 нояб. 2021 г. в 15:25, Ivan Daschinsky :
>
> Hi! Lets add one simple bug fix, but very useful
>
> https://issues.apache.org/jira/browse/IGNITE-15767
>
> пн, 22 нояб. 2021 г. в 15:22, Pavel Tupitsyn :
>
> > Yes, let's fix those auth issues, there are so many complaints on the user
> > list.
> >
> > On Mon, Nov 22, 2021 at 1:03 PM Mikhail Petrov 
> > wrote:
> >
> > > Igniters,
> > > it seems that issues [1] and [2] that were discovered recently are
> > > blockers for the 2.12 release.
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-15951
> > > [2] https://issues.apache.org/jira/browse/IGNITE-15966
> > >
> > > On 22.11.2021 11:04, Nikolay Izhikov wrote:
> > > > Hello.
> > > >
> > > > One more tiny fix that will improve java thin client performance in
> > > certain cases [1]
> > > > I think it worth to cherry-pick it to 2.12 release.
> > > >
> > > > Any objections?
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-15924
> > > >
> > > >> 19 нояб. 2021 г., в 14:56, Nikita Amelchev 
> > > написал(а):
> > > >>
> > > >> Vladimir, +1.
> > > >>
> > > >> I have cherry-picked the issue.
> > > >>
> > > >> пт, 19 нояб. 2021 г. в 14:53, Steshin Vladimir :
> > > >>>  Hi all.
> > > >>>
> > > >>>
> > > >>>  Let's add simple and useful thin-client-pool monitoring in 2.12:
> > > >>>
> > > >>> https://issues.apache.org/jira/browse/IGNITE-15183
> > > >>>
> > > >>> https://github.com/apache/ignite/pull/9525
> > > >>>
> > > >>>
> > > >>> 19.11.2021 09:50, Maksim Timonin пишет:
> > > >>>> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users
> > of
> > > >>>> metrics in case there are too many partitions (> 2), we observed
> > > >>>> extensive heap usage.
> > > >>>>
> > > >>>> [1] https://github.com/apache/ignite/pull/9518/files
> > > >>>> [2] https://issues.apache.org/jira/browse/IGNITE-15781
> > > >>>>
> > > >>>> On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin <
> > > timonin.ma...@gmail.com>
> > > >>>> wrote:
> > > >>>>
> > > >>>>> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will
> > > fix it
> > > >>>>> in 1-2 days.
> > > >>>>>
> > > >>>>> https://issues.apache.org/jira/browse/IGNITE-15943
> > > >>>>>
> > > >>>>> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov  > >
> > > wrote:
> > > >>>>>
> > > >>>>>> Folks,
> > > >>>>>>
> > > >>>>>> I've fixed almost all the review comments [1]. Hopefully, the
> > > changes
> > > >>>>>> will be merged by the end of the week.
> > > >>>>>>
> > > >>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-14744
> > > >>>>>>
> > > >>>>>> On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev <
> > namelc...@apache.org>
> > > >>>>>> wrote:
> > > >>>>>>> Hello, Pavel.
> > > >>>>>>>
> > > >>>>>>> The code freeze is blocked by two issues discussed above [1] [2].
> > > The
> > > >>>>>>> issues are in the final review state and should be merged soon.
> > > >>>>>>>
> > > >>>>>>> The bugfix is useful and can be cherry-picked, thank you.
> > > >>>>>>>
> > > >>>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15530
> > > >>>>>>> [2] https://issues.apache.org/jira/browse/IGNITE-14744
> > > >>>>>>>
> > > >>>>>>>
> > > >>>>>>> пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn <
> > ptupit...@apache.org
> > > >:
> > > >>>>>>>
> > > >>>>>>>> Igniters,

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Vladimir, +1.

I have cherry-picked the issue.

пт, 19 нояб. 2021 г. в 14:53, Steshin Vladimir :
>
>  Hi all.
>
>
>  Let's add simple and useful thin-client-pool monitoring in 2.12:
>
> https://issues.apache.org/jira/browse/IGNITE-15183
>
> https://github.com/apache/ignite/pull/9525
>
>
> 19.11.2021 09:50, Maksim Timonin пишет:
> > Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of
> > metrics in case there are too many partitions (> 2), we observed
> > extensive heap usage.
> >
> > [1] https://github.com/apache/ignite/pull/9518/files
> > [2] https://issues.apache.org/jira/browse/IGNITE-15781
> >
> > On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin 
> > wrote:
> >
> >> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will fix it
> >> in 1-2 days.
> >>
> >> https://issues.apache.org/jira/browse/IGNITE-15943
> >>
> >> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov  wrote:
> >>
> >>> Folks,
> >>>
> >>> I've fixed almost all the review comments [1]. Hopefully, the changes
> >>> will be merged by the end of the week.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/IGNITE-14744
> >>>
> >>> On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev 
> >>> wrote:
> >>>> Hello, Pavel.
> >>>>
> >>>> The code freeze is blocked by two issues discussed above [1] [2]. The
> >>>> issues are in the final review state and should be merged soon.
> >>>>
> >>>> The bugfix is useful and can be cherry-picked, thank you.
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/IGNITE-15530
> >>>> [2] https://issues.apache.org/jira/browse/IGNITE-14744
> >>>>
> >>>>
> >>>> пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn :
> >>>>
> >>>>> Igniters,
> >>>>>
> >>>>> What's the code freeze status?
> >>>>> Can I cherry-pick a bugfix [1] ?
> >>>>>
> >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15807
> >>>>>
> >>>>> On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky 
> >>> wrote:
> >>>>>> Thanks, cherry-picked to master.
> >>>>>>
> >>>>>> вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev  >>>> :
> >>>>>>> Ivan,
> >>>>>>>
> >>>>>>> Yes, the patch can be cherry-picked.
> >>>>>>>
> >>>>>>> вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky  >>>> :
> >>>>>>>> Since code freeze is postponed, may be I can cherry-pick my
> >>> patch
> >>>>>> already
> >>>>>>>> merged to master?
> >>>>>>>> https://issues.apache.org/jira/browse/IGNITE-15806
> >>>>>>>>
> >>>>>>>> пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev <
> >>> namelc...@apache.org>:
> >>>>>>>>> Maksim T., Maxim M., Ok.
> >>>>>>>>>
> >>>>>>>>> I think we can move code freeze to +1 week to await these
> >>> issues.
> >>>>>>>>> пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov <
> >>> mmu...@apache.org>:
> >>>>>>>>>> Folks,
> >>>>>>>>>>
> >>>>>>>>>> I've previously mentioned that I'd like to include the [1]
> >>> issue in
> >>>>>>>>>> the release. Currently, the status is "Patch Available" and
> >>> it's
> >>>>>>>>>> actively reviewing now. I'd be happy if we wait a couple of
> >>> days
> >>>>>> and
> >>>>>>>>>> add this improvement to the release.
> >>>>>>>>>>
> >>>>>>>>>> I've also created an issue [2] to remove the ambiguity
> >>> output
> >>>>>> message
> >>>>>>>>>> for the snapshot check and idle verify procedures. This is
> >>> a minor
> >>>>>>>>>> output message change, however, it was directly requested
> >>> by users.
> >>>>>>>>>

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Maksim, Pavel, +1 to cherry-pick these issues.

пт, 19 нояб. 2021 г. в 11:45, Nikolay Izhikov :
>
> Hello.
>
> > [2] https://issues.apache.org/jira/browse/IGNITE-15781
>
> Cherry-picked to 2.12.
>
> > 19 нояб. 2021 г., в 10:12, Pavel Tupitsyn  написал(а):
> >
> > I'd like to add this simple fix as well [1]
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15954
> >
> > On Fri, Nov 19, 2021 at 9:50 AM Maksim Timonin 
> > wrote:
> >
> >> Hi, I want to add to 2.12 a fix [1] of a bug [2]. It affects users of
> >> metrics in case there are too many partitions (> 2), we observed
> >> extensive heap usage.
> >>
> >> [1] https://github.com/apache/ignite/pull/9518/files
> >> [2] https://issues.apache.org/jira/browse/IGNITE-15781
> >>
> >> On Thu, Nov 18, 2021 at 12:59 PM Maksim Timonin 
> >> wrote:
> >>
> >>> Hi, guys, we have a blocker [1]. NPE for some SQL queries. I will fix it
> >>> in 1-2 days.
> >>>
> >>> https://issues.apache.org/jira/browse/IGNITE-15943
> >>>
> >>> On Mon, Nov 15, 2021 at 2:57 PM Maxim Muzafarov 
> >> wrote:
> >>>
> >>>> Folks,
> >>>>
> >>>> I've fixed almost all the review comments [1]. Hopefully, the changes
> >>>> will be merged by the end of the week.
> >>>>
> >>>> [1] https://issues.apache.org/jira/browse/IGNITE-14744
> >>>>
> >>>> On Mon, 8 Nov 2021 at 15:42, Nikita Amelchev 
> >>>> wrote:
> >>>>>
> >>>>> Hello, Pavel.
> >>>>>
> >>>>> The code freeze is blocked by two issues discussed above [1] [2]. The
> >>>>> issues are in the final review state and should be merged soon.
> >>>>>
> >>>>> The bugfix is useful and can be cherry-picked, thank you.
> >>>>>
> >>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15530
> >>>>> [2] https://issues.apache.org/jira/browse/IGNITE-14744
> >>>>>
> >>>>>
> >>>>> пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn :
> >>>>>
> >>>>>>
> >>>>>> Igniters,
> >>>>>>
> >>>>>> What's the code freeze status?
> >>>>>> Can I cherry-pick a bugfix [1] ?
> >>>>>>
> >>>>>> [1] https://issues.apache.org/jira/browse/IGNITE-15807
> >>>>>>
> >>>>>> On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky  >>>
> >>>> wrote:
> >>>>>>
> >>>>>>> Thanks, cherry-picked to master.
> >>>>>>>
> >>>>>>> вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev <
> >> namelc...@apache.org
> >>>>> :
> >>>>>>>
> >>>>>>>> Ivan,
> >>>>>>>>
> >>>>>>>> Yes, the patch can be cherry-picked.
> >>>>>>>>
> >>>>>>>> вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky <
> >> ivanda...@gmail.com
> >>>>> :
> >>>>>>>>>
> >>>>>>>>> Since code freeze is postponed, may be I can cherry-pick my
> >>>> patch
> >>>>>>> already
> >>>>>>>>> merged to master?
> >>>>>>>>> https://issues.apache.org/jira/browse/IGNITE-15806
> >>>>>>>>>
> >>>>>>>>> пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev <
> >>>> namelc...@apache.org>:
> >>>>>>>>>
> >>>>>>>>>> Maksim T., Maxim M., Ok.
> >>>>>>>>>>
> >>>>>>>>>> I think we can move code freeze to +1 week to await these
> >>>> issues.
> >>>>>>>>>>
> >>>>>>>>>> пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov <
> >>>> mmu...@apache.org>:
> >>>>>>>>>>>
> >>>>>>>>>>> Folks,
> >>>>>>>>>>>
> >>>>>>>>>>> I've previously mentioned that I'd like to include the [1]
> >>>> issue in
> >>>>>>>>>>> th

[ANNOUNCE] Apache Ignite Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 released

[Nikita Amelchev]

The Apache Ignite Community is pleased to announce the release of
Apache Ignite Spring Cache and Spring Transactions extensions 1.0.0.

The following integrations were migrated to the Apache Ignite
Extensions repository:

- Spring Transactions extension
- Spring Cache extension

Apache Ignite Spring Cache extension: release notes [1], documentation [2].
Apache Ignite Spring Transactions extension: release notes [3],
documentation [4].

The sources package is available here:
https://ignite.apache.org/download.cgi#extensions

Please let us know if you have any problems
https://ignite.apache.org/community/resources.html#ask

[1] https://ignite.apache.org/releases/ext/spring-tx-1.0.0/release_notes.html
[2] 
https://ignite.apache.org/docs/2.11.0/extensions-and-integrations/spring/spring-tx.html
[3] https://ignite.apache.org/releases/ext/spring-cache-1.0.0/release_notes.html
[4] 
https://ignite.apache.org/docs/2.11.0/extensions-and-integrations/spring/spring-caching.html

-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello, Pavel.

The code freeze is blocked by two issues discussed above [1] [2]. The
issues are in the final review state and should be merged soon.

The bugfix is useful and can be cherry-picked, thank you.

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


пн, 8 нояб. 2021 г. в 14:46, Pavel Tupitsyn :

>
> Igniters,
>
> What's the code freeze status?
> Can I cherry-pick a bugfix [1] ?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-15807
>
> On Tue, Nov 2, 2021 at 4:39 PM Ivan Daschinsky  wrote:
>
> > Thanks, cherry-picked to master.
> >
> > вт, 2 нояб. 2021 г. в 16:00, Nikita Amelchev :
> >
> > > Ivan,
> > >
> > > Yes, the patch can be cherry-picked.
> > >
> > > вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky :
> > > >
> > > > Since code freeze is postponed, may be I can cherry-pick my patch
> > already
> > > > merged to master?
> > > > https://issues.apache.org/jira/browse/IGNITE-15806
> > > >
> > > > пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev :
> > > >
> > > > > Maksim T., Maxim M., Ok.
> > > > >
> > > > > I think we can move code freeze to +1 week to await these issues.
> > > > >
> > > > > пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov :
> > > > > >
> > > > > > Folks,
> > > > > >
> > > > > > I've previously mentioned that I'd like to include the [1] issue in
> > > > > > the release. Currently, the status is "Patch Available" and it's
> > > > > > actively reviewing now. I'd be happy if we wait a couple of days
> > and
> > > > > > add this improvement to the release.
> > > > > >
> > > > > > I've also created an issue [2] to remove the ambiguity output
> > message
> > > > > > for the snapshot check and idle verify procedures. This is a minor
> > > > > > output message change, however, it was directly requested by users.
> > > > > > Would you don't mind if we include this issue in the release also?
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14744
> > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15849
> > > > > >
> > > > > > On Fri, 29 Oct 2021 at 14:19, Maksim Timonin <
> > > timonin.ma...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > Status update on my issue:
> > > > > > >
> > > > > > > IGNITE-15530 [1] is in "Patch Available" state, Anton Vinogradov
> > > > > agreed to
> > > > > > > review this ticket.
> > > > > > >
> > > > > > > Also, I'm preparing IndexQuery docs in ticket IGNITE-15745 [2].
> > I'm
> > > > > going
> > > > > > > to submit a patch with docs today/tomorrow, and want to include
> > > them in
> > > > > > > 2.12 too.
> > > > > > >
> > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15530
> > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15745
> > > > > > >
> > > > > > > On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev <
> > > > > ilya.kasnach...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I have prepared a fix for sqlline.sh -e:
> > > > > > > > https://github.com/apache/ignite/pull/9536
> > > > > > > >
> > > > > > > > If smbd reviews it, we can put it on 2.12.
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > --
> > > > > > > > Ilya Kasnacheev
> > > > > > > >
> > > > > > > >
> > > > > > > > чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev <
> > > namelc...@apache.org>:
> > > > > > > >
> > > > > > > > > Maksim, ok.
> > > > > > > > >
> > > > > > > > > Ivan,
> > > > > > > > > The minor issues can be 

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Ivan,

Yes, the patch can be cherry-picked.

вт, 2 нояб. 2021 г. в 15:55, Ivan Daschinsky :
>
> Since code freeze is postponed, may be I can cherry-pick my patch already
> merged to master?
> https://issues.apache.org/jira/browse/IGNITE-15806
>
> пт, 29 окт. 2021 г. в 20:24, Nikita Amelchev :
>
> > Maksim T., Maxim M., Ok.
> >
> > I think we can move code freeze to +1 week to await these issues.
> >
> > пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov :
> > >
> > > Folks,
> > >
> > > I've previously mentioned that I'd like to include the [1] issue in
> > > the release. Currently, the status is "Patch Available" and it's
> > > actively reviewing now. I'd be happy if we wait a couple of days and
> > > add this improvement to the release.
> > >
> > > I've also created an issue [2] to remove the ambiguity output message
> > > for the snapshot check and idle verify procedures. This is a minor
> > > output message change, however, it was directly requested by users.
> > > Would you don't mind if we include this issue in the release also?
> > >
> > > [1] https://issues.apache.org/jira/browse/IGNITE-14744
> > > [2] https://issues.apache.org/jira/browse/IGNITE-15849
> > >
> > > On Fri, 29 Oct 2021 at 14:19, Maksim Timonin 
> > wrote:
> > > >
> > > > Status update on my issue:
> > > >
> > > > IGNITE-15530 [1] is in "Patch Available" state, Anton Vinogradov
> > agreed to
> > > > review this ticket.
> > > >
> > > > Also, I'm preparing IndexQuery docs in ticket IGNITE-15745 [2]. I'm
> > going
> > > > to submit a patch with docs today/tomorrow, and want to include them in
> > > > 2.12 too.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/IGNITE-15530
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-15745
> > > >
> > > > On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev <
> > ilya.kasnach...@gmail.com>
> > > > wrote:
> > > >
> > > > > Hello!
> > > > >
> > > > > I have prepared a fix for sqlline.sh -e:
> > > > > https://github.com/apache/ignite/pull/9536
> > > > >
> > > > > If smbd reviews it, we can put it on 2.12.
> > > > >
> > > > > Regards,
> > > > > --
> > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > > чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev :
> > > > >
> > > > > > Maksim, ok.
> > > > > >
> > > > > > Ivan,
> > > > > > The minor issues can be considered if they will be merged before
> > the
> > > > > > code freeze.
> > > > > >
> > > > > > ср, 27 окт. 2021 г. в 14:55, Pavel Tupitsyn  > >:
> > > > > > >
> > > > > > > Ivan, every additional ticket potentially moves the release date
> > > > > further.
> > > > > > > Also, AFAIK, Igor is on vacation and can't do a review this week.
> > > > > > >
> > > > > > > On Wed, Oct 27, 2021 at 2:32 PM Ivan Daschinsky <
> > ivanda...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Pavel, but what is the problem to include a minor refactoring?
> > > > > > Especially
> > > > > > > > before code freeze?
> > > > > > > >
> > > > > > > > ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn <
> > ptupit...@apache.org>:
> > > > > > > >
> > > > > > > > > Ivan, IGNITE-15806 seems to be a minor refactoring, not sure
> > we
> > > > > > should
> > > > > > > > > inflate the scope with this.
> > > > > > > > >
> > > > > > > > > On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky <
> > > > > ivanda...@gmail.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Nikita, can we add
> > > > > > https://issues.apache.org/jira/browse/IGNITE-15806
> > > > > > > > > this
> > > > > > > > > > ticket for release?
> > > > > > &

[RESULT] [VOTE] Release Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 RC1

[Nikita Amelchev]

Dear community,

Release of Apache Ignite spring-tx-ext, spring-cache-ext extensions
1.0.0 RC1 has been accepted.

3 - "+1" votes received (3 binding).
2 - "+0,5" vote received (1 binding).
1 - "-0" vote received (1 binding).

Here are the votes received:

Anton Vinogradov (binding)
Ivan Daschinsky
Maxim Muzafarov (binding)
Ilya Kasnacheev (binding)
Denis Magda (binding)
Nikolay Izhikov (binding)

New release will be announced soon.

-- 
Best wishes,
Amelchev Nikita

Re: [VOTE][EXTENSION] Release Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 RC1

[Nikita Amelchev]

The vote received enough votes for a resolution. I will prepare a
result shortly.

I have created issues to improve the release process:
IGNITE-15860 [Extensions] Automated RC preparation and testing at
Apache TeamCity [1]
IGNITE-15861 [Extensions] Move examples to separate maven projects [2]

Thanks for voting!

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

вт, 2 нояб. 2021 г. в 12:04, Nikolay Izhikov :
>
> +1 (binding)
>
> > 1 нояб. 2021 г., в 17:41, Denis Magda  написал(а):
> >
> > +1 (binding)
> >
> > Support to release the integration and then bring in essential automation
> > for testing.
> >
> > -
> > Denis
> >
> >
> > On Wed, Oct 27, 2021 at 4:48 AM Nikita Amelchev 
> > wrote:
> >
> >> Dear Ignite Community,
> >>
> >> I have uploaded a release candidate of extensions modules:
> >> - spring-tx-ext 1.0.0
> >> - spring-cache-ext 1.0.0
> >> - spring-data-commons 1.1.0
> >>
> >> The following staging can be used for testing:
> >> https://repository.apache.org/content/repositories/orgapacheignite-1533
> >>
> >> The release candidate of the spring-tx-ext 1.0.0 extension:
> >>
> >> https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0-rc1/
> >>
> >> The release candidate of the spring-cache-ext 1.0.0 extension:
> >>
> >> https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-cache-ext/1.0.0-rc1/
> >>
> >> The release candidate of the spring-data-common 1.1.0 dependent module
> >> is in the packages mentioned above.
> >>
> >> Tags were created:
> >> ignite-spring-tx-ext-1.0.0-rc1
> >> ignite-spring-cache-ext-1.0.0-rc1
> >> ignite-spring-data-commons-1.1.0-rc1
> >>
> >>
> >> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=refs/tags/ignite-spring-tx-ext-1.0.0-rc1
> >>
> >> RELEASE NOTES:
> >>
> >> https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=c6b2a393e042ce956bfefd5d7d92d5ab4ff04cda;hb=HEAD
> >>
> >> DOCUMENTATION:
> >> Documentation of the spring-tx-ext extension:
> >>
> >> https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
> >>
> >> Documentation of the spring-cache-ext extension:
> >>
> >> https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-caching.adoc
> >>
> >> The vote is formal, see voting guidelines
> >> https://www.apache.org/foundation/voting.html
> >>
> >> +1 - to accept the extensions modules listed in the thread
> >> 0 - don't care either way
> >> -1 - DO NOT accept either of the extensions modules listed in the
> >> thread (explain why)
> >>
> >> The vote will hold for 5 days and will end on November 1, 2021, 10:00 UTC
> >> https://www.timeanddate.com/countdown/generic?iso=20211101T10=0
> >>
> >> --
> >> Best wishes,
> >> Amelchev Nikita
> >>
>


-- 
Best wishes,
Amelchev Nikita

Re: [VOTE][EXTENSION] Release Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 RC1

[Nikita Amelchev]

Hi Igniters, PMCs,

Remind you that according to ASF policy [1] for a release vote to
pass, a minimum of three positive votes (full binding +1, not
fractions) and more positive than negative votes must be cast.

I suggest continuing the vote until there are enough votes for a
resolution. The policy allows this.

[1] https://www.apache.org/foundation/voting.html#ReleaseVotes

вс, 31 окт. 2021 г. в 13:46, Mikhail Petrov :
>
> Ilya, for Ignite 2.10 versions and earlier spring-tx and spring-cache
> integrations are stored in the ignite-spring module. Initially, there
> were no dedicated modules for them. As I see, we cannot fully migrate
> the ignite-spring module as it is responsible for parsing Ignite XML
> configurations and included in binary release. Therefore, if the users
> want to use the mentioned above extensions with Ignite 2.10 or earlier
> they can get two copies of the Ignite extension classes in their
> classpath - one from extension dependency and one from ignite-spring.
> This problem cannot be solved by excluding some modules - only by
> shading or specifying some classes before others in the classpath.
>
> WDYT?
>
>
> --
> Mikhail
>
>
> On 31.10.2021 01:13, Ilya Kasnacheev wrote:
> > Hello!
> >
> > + 0.5
> >
> >> Apache Ignite 2.10.0 and earlier the ignite-spring-cache-ext dependency
> > must be added to classpath before ignite-spring, due to duplication of
> > Spring Cache integration classes.
> >
> > I think this recommendation does not have much sense - the order of
> > classpath and maven dependency resolution is not something you may count
> > on. We could teach our users to do proper maven exclusion instead (what is
> > the module which they need to exclude - is it spring-cache? which classes
> > are duplicated?)
> >
> > But otherwise maybe we should get it out of door and finish the migration.
> >
> > Regards,



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Maksim T., Maxim M., Ok.

I think we can move code freeze to +1 week to await these issues.

пт, 29 окт. 2021 г. в 15:53, Maxim Muzafarov :
>
> Folks,
>
> I've previously mentioned that I'd like to include the [1] issue in
> the release. Currently, the status is "Patch Available" and it's
> actively reviewing now. I'd be happy if we wait a couple of days and
> add this improvement to the release.
>
> I've also created an issue [2] to remove the ambiguity output message
> for the snapshot check and idle verify procedures. This is a minor
> output message change, however, it was directly requested by users.
> Would you don't mind if we include this issue in the release also?
>
> [1] https://issues.apache.org/jira/browse/IGNITE-14744
> [2] https://issues.apache.org/jira/browse/IGNITE-15849
>
> On Fri, 29 Oct 2021 at 14:19, Maksim Timonin  wrote:
> >
> > Status update on my issue:
> >
> > IGNITE-15530 [1] is in "Patch Available" state, Anton Vinogradov agreed to
> > review this ticket.
> >
> > Also, I'm preparing IndexQuery docs in ticket IGNITE-15745 [2]. I'm going
> > to submit a patch with docs today/tomorrow, and want to include them in
> > 2.12 too.
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15530
> > [2] https://issues.apache.org/jira/browse/IGNITE-15745
> >
> > On Thu, Oct 28, 2021 at 11:06 AM Ilya Kasnacheev 
> > wrote:
> >
> > > Hello!
> > >
> > > I have prepared a fix for sqlline.sh -e:
> > > https://github.com/apache/ignite/pull/9536
> > >
> > > If smbd reviews it, we can put it on 2.12.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> > >
> > >
> > > чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev :
> > >
> > > > Maksim, ok.
> > > >
> > > > Ivan,
> > > > The minor issues can be considered if they will be merged before the
> > > > code freeze.
> > > >
> > > > ср, 27 окт. 2021 г. в 14:55, Pavel Tupitsyn :
> > > > >
> > > > > Ivan, every additional ticket potentially moves the release date
> > > further.
> > > > > Also, AFAIK, Igor is on vacation and can't do a review this week.
> > > > >
> > > > > On Wed, Oct 27, 2021 at 2:32 PM Ivan Daschinsky 
> > > > wrote:
> > > > >
> > > > > > Pavel, but what is the problem to include a minor refactoring?
> > > > Especially
> > > > > > before code freeze?
> > > > > >
> > > > > > ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn :
> > > > > >
> > > > > > > Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we
> > > > should
> > > > > > > inflate the scope with this.
> > > > > > >
> > > > > > > On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky <
> > > ivanda...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Nikita, can we add
> > > > https://issues.apache.org/jira/browse/IGNITE-15806
> > > > > > > this
> > > > > > > > ticket for release?
> > > > > > > >
> > > > > > > > ср, 27 окт. 2021 г. в 13:40, Maksim Timonin <
> > > > timonin.ma...@gmail.com>:
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I'd like to include the ticket in 2.12. There was a 
> > > > > > > > > performance
> > > > > > issue,
> > > > > > > I
> > > > > > > > > spent some time trying to figure it out. I prepared some fixes
> > > > and I
> > > > > > am
> > > > > > > > > going to submit a patch this week.
> > > > > > > > >
> > > > > > > > > I think this issue is critical to include to 2.12 together 
> > > > > > > > > with
> > > > basic
> > > > > > > > > IndexQuery functionality, because this ticket provides 
> > > > > > > > > expected
> > > > > > > behavior
> > > > > > > > of
> > > > > > > > > querying indexes - sorted over all nodes results.
> > > > > > > >

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Maksim, ok.

Ivan,
The minor issues can be considered if they will be merged before the
code freeze.

ср, 27 окт. 2021 г. в 14:55, Pavel Tupitsyn :
>
> Ivan, every additional ticket potentially moves the release date further.
> Also, AFAIK, Igor is on vacation and can't do a review this week.
>
> On Wed, Oct 27, 2021 at 2:32 PM Ivan Daschinsky  wrote:
>
> > Pavel, but what is the problem to include a minor refactoring? Especially
> > before code freeze?
> >
> > ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn :
> >
> > > Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we should
> > > inflate the scope with this.
> > >
> > > On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky 
> > > wrote:
> > >
> > > > Nikita, can we add https://issues.apache.org/jira/browse/IGNITE-15806
> > > this
> > > > ticket for release?
> > > >
> > > > ср, 27 окт. 2021 г. в 13:40, Maksim Timonin :
> > > >
> > > > > Hi,
> > > > >
> > > > > I'd like to include the ticket in 2.12. There was a performance
> > issue,
> > > I
> > > > > spent some time trying to figure it out. I prepared some fixes and I
> > am
> > > > > going to submit a patch this week.
> > > > >
> > > > > I think this issue is critical to include to 2.12 together with basic
> > > > > IndexQuery functionality, because this ticket provides expected
> > > behavior
> > > > of
> > > > > querying indexes - sorted over all nodes results.
> > > > >
> > > > > - IGNITE-15530: IndexQuery has to use MergeSort reducer [1]
> > > > >
> > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15530
> > > > >
> > > > > On Wed, Oct 27, 2021 at 1:23 PM Nikita Amelchev <
> > namelc...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hello.
> > > > > >
> > > > > > Code freeze is planned for Friday, October 29.
> > > > > >
> > > > > > There are 40 unresolved issues [1] in the release scope. I suggest
> > > > > > bumping up the fix version if they will not be resolved till the
> > code
> > > > > > freeze.
> > > > > >
> > > > > > Please, feel free to write if some of them are critical to be in
> > the
> > > > > 2.12.
> > > > > >
> > > > > > Also, please, pay attention to unresolved documentation issues. [2]
> > > > > >
> > > > > > Sergey, Petr, thanks for helping with TC.
> > > > > >
> > > > > > [1]
> > > > > >
> > > > >
> > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20
> > > > > >
> > > > > > [2]
> > > > > >
> > > > >
> > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> > > > > >
> > > > > > вт, 26 окт. 2021 г. в 12:50, Petr Ivanov :
> > > > > > >
> > > > > > > Thanks, Sergey.
> > > > > > >
> > > > > > > I've also reconfigured nightly builds for ignite-2.12 branch.
> > > > > > >
> > > > > > >
> > > > > > > > On 22 Oct 2021, at 17:32, Сергей Утцель 
> > > wrote:
> > > > > > > >
> > > > > > > > I configured TC bot to 'ignite-2.12' instead of 'ignite-2.11'
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Best wishes,
> > > > > > Amelchev Nikita
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Sincerely yours, Ivan Daschinskiy
> > > >
> > >
> >
> >
> > --
> > Sincerely yours, Ivan Daschinskiy
> >



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hello.

Code freeze is planned for Friday, October 29.

There are 40 unresolved issues [1] in the release scope. I suggest
bumping up the fix version if they will not be resolved till the code
freeze.

Please, feel free to write if some of them are critical to be in the 2.12.

Also, please, pay attention to unresolved documentation issues. [2]

Sergey, Petr, thanks for helping with TC.

[1] 
https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20

[2] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20

вт, 26 окт. 2021 г. в 12:50, Petr Ivanov :
>
> Thanks, Sergey.
>
> I've also reconfigured nightly builds for ignite-2.12 branch.
>
>
> > On 22 Oct 2021, at 17:32, Сергей Утцель  wrote:
> >
> > I configured TC bot to 'ignite-2.12' instead of 'ignite-2.11'
>


-- 
Best wishes,
Amelchev Nikita

[VOTE][EXTENSION] Release Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 RC1

[Nikita Amelchev]

Dear Ignite Community,

I have uploaded a release candidate of extensions modules:
 - spring-tx-ext 1.0.0
 - spring-cache-ext 1.0.0
 - spring-data-commons 1.1.0

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

The release candidate of the spring-tx-ext 1.0.0 extension:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0-rc1/

The release candidate of the spring-cache-ext 1.0.0 extension:
https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-cache-ext/1.0.0-rc1/

The release candidate of the spring-data-common 1.1.0 dependent module
is in the packages mentioned above.

Tags were created:
ignite-spring-tx-ext-1.0.0-rc1
ignite-spring-cache-ext-1.0.0-rc1
ignite-spring-data-commons-1.1.0-rc1

https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=refs/tags/ignite-spring-tx-ext-1.0.0-rc1

RELEASE NOTES:
https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=c6b2a393e042ce956bfefd5d7d92d5ab4ff04cda;hb=HEAD

DOCUMENTATION:
Documentation of the spring-tx-ext extension:
https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc

Documentation of the spring-cache-ext extension:
https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-caching.adoc

The vote is formal, see voting guidelines
https://www.apache.org/foundation/voting.html

+1 - to accept the extensions modules listed in the thread
0 - don't care either way
-1 - DO NOT accept either of the extensions modules listed in the
thread (explain why)

The vote will hold for 5 days and will end on November 1, 2021, 10:00 UTC
https://www.timeanddate.com/countdown/generic?iso=20211101T10=0

-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSS] Release spring-tx-ext and spring-cache-ext Ignite extensions

[Nikita Amelchev]

Igniters,

The spring-tx and spring-cache extensions are ready to be released.

I have created the release branch: `ignite-spring-tx-cache-ext-1.0`.

The updated documentation: spring-tx [1], spring-cache [2].

I will prepare the release candidate at the nearest time.

[1] 
https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc
[2] 
https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-caching.adoc

вт, 5 окт. 2021 г. в 13:48, Nikolay Izhikov :
>
> +1
>
> > 5 окт. 2021 г., в 11:48, Nikita Amelchev  написал(а):
> >
> > Folks, we should release the spring-data-commons module with the 1.1.0
> > version to release spring-tx, spring-cache modules.
> > It contains some proxies required for the new modules.
> >
> > I suggest:
> >
> > 1. Release the spring-data-commons 1.1.0, spring-tx 1.0.0,
> > spring-cache 1.0.0 modules with separate source packages:
> >
> > /ignite/ignite-extensions/ignite-spring-data-commons/1.1.0/[src]
> > /ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0/[src]
> > /ignite/ignite-extensions/ignite-spring-cache-ext/1.0.0/[src]
> >
> > (The spring-data-commons 1.0.0 was included in the
> > ignite-spring-data-all-ext/1.0.0 source package)
> >
> > 2. Use one voting thread for this activity.
> >
> > Any objections?
> >
> > пт, 24 сент. 2021 г. в 15:14, Nikita Amelchev :
> >>
> >> Igniters,
> >>
> >> Since Ignite 2.11 has been released the following extension modules
> >> can be released too:
> >>
> >> spring-cache-ext
> >> spring-tx-ext
> >>
> >> I want to be a release manager for these if nobody minds.
> >>
> >> The release process can be started after checking documentation.
> >>
> >> --
> >> Best wishes,
> >> Amelchev Nikita
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
>


-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Igniters,

Could you help with the TC bot configuration?

The TC bot should be configured to the `ignite-2.12` release branch.

пт, 22 окт. 2021 г. в 12:42, Nikolay Izhikov :
>
> Hello.
>
> In the scope of IEP-80 Breaking changes in Ignite-2.x PR for the following 
> API are prepared:
>
> 1. MVCC
> - https://issues.apache.org/jira/browse/IGNITE-15757
> - https://github.com/apache/ignite/pull/9516
>
> 2. LOCAL caches
> - https://issues.apache.org/jira/browse/IGNITE-15756
> - https://github.com/apache/ignite/pull/9515
>
> 3. CacheConfiguration#rebalanceDelay
> - https://issues.apache.org/jira/browse/IGNITE-15764
> - https://github.com/apache/ignite/pull/9515
>
> Please, review.
>
>
> > 21 окт. 2021 г., в 20:33, Nikita Amelchev  написал(а):
> >
> > Petr, thank you!
> >
> > чт, 21 окт. 2021 г. в 18:19, Petr Ivanov :
> >>
> >> Try now, please.
> >>
> >>> On 21 Oct 2021, at 17:47, Nikita Amelchev  wrote:
> >>>
> >>> Hi,
> >>>
> >>> Petr, could you grant me TC permissions to run release builds please?
> >>>
> >>> ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn :
> >>>
> >>>>
> >>>> Igniters,
> >>>>
> >>>> I've filed a blocker - release configurations on TeamCity should be fixed
> >>>> after recent .NET project structure refactoring:
> >>>> https://issues.apache.org/jira/browse/IGNITE-15779
> >>>>
> >>>> I'm on vacation right now with limited internet access, I'll work on this
> >>>> ASAP next week.
> >>>>
> >>>> On Wed, Oct 13, 2021 at 2:33 PM Nikita Amelchev 
> >>>> wrote:
> >>>>
> >>>>> Igniters,
> >>>>>
> >>>>> Scope freeze is planned for Friday, October 15.
> >>>>> I suggest creating the release branch on that date.
> >>>>>
> >>>>> The wiki page with the release info. [1] Please, check the fix version
> >>>>> of your issues.
> >>>>>
> >>>>> There are no unresolved blockers.
> >>>>> There are 3 important issues in the review state. [2]
> >>>>>
> >>>>> Also, please, pay attention to unresolved documentation issues. [3]
> >>>>>
> >>>>> [1] 
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> >>>>> [2]
> >>>>> https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary
> >>>>> [3]
> >>>>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> >>>>>
> >>>>> пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn :
> >>>>>>
> >>>>>> I'm working on IGNITE-15504 and plan to finish it early next week.
> >>>>>>
> >>>>>> On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev 
> >>>>> wrote:
> >>>>>>
> >>>>>>> Igniters,
> >>>>>>>
> >>>>>>> I have created the wiki page for the 2.12 release. [1]
> >>>>>>>
> >>>>>>> The release scope contains 1 issue that is marked as a blocker:
> >>>>>>> IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be
> >>>>>>> developed with newer SDKs [2]
> >>>>>>>
> >>>>>>> Folks, do not forget to document features (65 issues still not
> >>>>> resolved).
> >>>>>>> [3]
> >>>>>>>
> >>>>>>> Maxim, Ivan,
> >>>>>>> +1 to add these issues to the 2.12 scope.
> >>>>>>>
> >>>>>>> [1]
> >>>>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> >>>>>>> [2] ht

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Petr, thank you!

чт, 21 окт. 2021 г. в 18:19, Petr Ivanov :
>
> Try now, please.
>
> > On 21 Oct 2021, at 17:47, Nikita Amelchev  wrote:
> >
> > Hi,
> >
> > Petr, could you grant me TC permissions to run release builds please?
> >
> > ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn :
> >
> >>
> >> Igniters,
> >>
> >> I've filed a blocker - release configurations on TeamCity should be fixed
> >> after recent .NET project structure refactoring:
> >> https://issues.apache.org/jira/browse/IGNITE-15779
> >>
> >> I'm on vacation right now with limited internet access, I'll work on this
> >> ASAP next week.
> >>
> >> On Wed, Oct 13, 2021 at 2:33 PM Nikita Amelchev 
> >> wrote:
> >>
> >>> Igniters,
> >>>
> >>> Scope freeze is planned for Friday, October 15.
> >>> I suggest creating the release branch on that date.
> >>>
> >>> The wiki page with the release info. [1] Please, check the fix version
> >>> of your issues.
> >>>
> >>> There are no unresolved blockers.
> >>> There are 3 important issues in the review state. [2]
> >>>
> >>> Also, please, pay attention to unresolved documentation issues. [3]
> >>>
> >>> [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> >>> [2]
> >>> https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary
> >>> [3]
> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> >>>
> >>> пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn :
> >>>>
> >>>> I'm working on IGNITE-15504 and plan to finish it early next week.
> >>>>
> >>>> On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev 
> >>> wrote:
> >>>>
> >>>>> Igniters,
> >>>>>
> >>>>> I have created the wiki page for the 2.12 release. [1]
> >>>>>
> >>>>> The release scope contains 1 issue that is marked as a blocker:
> >>>>> IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be
> >>>>> developed with newer SDKs [2]
> >>>>>
> >>>>> Folks, do not forget to document features (65 issues still not
> >>> resolved).
> >>>>> [3]
> >>>>>
> >>>>> Maxim, Ivan,
> >>>>> +1 to add these issues to the 2.12 scope.
> >>>>>
> >>>>> [1]
> >>> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> >>>>> [2] https://issues.apache.org/jira/browse/IGNITE-15504
> >>>>> [3]
> >>>>>
> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> >>>>>
> >>>>> ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky :
> >>>>>>
> >>>>>> Created issues related building ODBC module, running C++ suites and
> >>>>>> removing VS project files
> >>>>>>
> >>>>>> 1. https://issues.apache.org/jira/browse/IGNITE-15637
> >>>>>> 2.https://issues.apache.org/jira/browse/IGNITE-15636
> >>>>>>
> >>>>>> вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky :
> >>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> Let's consider building odbc driver using Visual C++ 2017?
> >>>>>>>
> >>>>>>> 2015, 2017 and 2019 share the same redistributable package and it
> >>> is
> >>>>> the
> >>>>>>> default one in Windows 10.
> 

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Hi,

Petr, could you grant me TC permissions to run release builds please?

ср, 20 окт. 2021 г. в 10:25, Pavel Tupitsyn :

>
> Igniters,
>
> I've filed a blocker - release configurations on TeamCity should be fixed
> after recent .NET project structure refactoring:
> https://issues.apache.org/jira/browse/IGNITE-15779
>
> I'm on vacation right now with limited internet access, I'll work on this
> ASAP next week.
>
> On Wed, Oct 13, 2021 at 2:33 PM Nikita Amelchev 
> wrote:
>
> > Igniters,
> >
> > Scope freeze is planned for Friday, October 15.
> > I suggest creating the release branch on that date.
> >
> > The wiki page with the release info. [1] Please, check the fix version
> > of your issues.
> >
> > There are no unresolved blockers.
> > There are 3 important issues in the review state. [2]
> >
> > Also, please, pay attention to unresolved documentation issues. [3]
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> > [2]
> > https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary
> > [3]
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> >
> > пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn :
> > >
> > > I'm working on IGNITE-15504 and plan to finish it early next week.
> > >
> > > On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev 
> > wrote:
> > >
> > > > Igniters,
> > > >
> > > > I have created the wiki page for the 2.12 release. [1]
> > > >
> > > > The release scope contains 1 issue that is marked as a blocker:
> > > > IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be
> > > > developed with newer SDKs [2]
> > > >
> > > > Folks, do not forget to document features (65 issues still not
> > resolved).
> > > > [3]
> > > >
> > > > Maxim, Ivan,
> > > > +1 to add these issues to the 2.12 scope.
> > > >
> > > > [1]
> > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> > > > [2] https://issues.apache.org/jira/browse/IGNITE-15504
> > > > [3]
> > > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> > > >
> > > > ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky :
> > > > >
> > > > > Created issues related building ODBC module, running C++ suites and
> > > > > removing VS project files
> > > > >
> > > > > 1. https://issues.apache.org/jira/browse/IGNITE-15637
> > > > > 2.https://issues.apache.org/jira/browse/IGNITE-15636
> > > > >
> > > > > вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky :
> > > > >
> > > > > > +1
> > > > > >
> > > > > > Let's consider building odbc driver using Visual C++ 2017?
> > > > > >
> > > > > > 2015, 2017 and 2019 share the same redistributable package and it
> > is
> > > > the
> > > > > > default one in Windows 10.
> > > > > >
> > > > > > Also, let's remove vs project files, since the most of you all
> > agree
> > > > that
> > > > > > it is redundant.
> > > > > >
> > > > > > If both suggestions are ok, I will create ticketa soon.
> > > > > >
> > > > > > вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn :
> > > > > >
> > > > > >> +1
> > > > > >>
> > > > > >> On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov <
> > mmu...@apache.org>
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hello Nikita,

[ANNOUNCE] The 2.12 release branch creation

[Nikita Amelchev]

Hello, Igniters.

I announce scope freeze for the Apache Ignite 2.12 release.

I have created the ignite-2.12 branch for the release.

Only critical issues can be added to the scope. Please, discuss with
the community to add new issues.

Code freeze is planned for Friday, October 29.

All not-critical unresolved issues at the code freeze date will be
moved to the next release.

The wiki page with the release info:
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12

-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSSION][IEP-80] Breaking changes in Ignite-2.x

[Nikita Amelchev]

+1 for deprecation in the 2.12 release

пт, 15 окт. 2021 г. в 15:35, Nikolay Izhikov :
>
> Hello, Igniters.
>
> I’ve prepared IEP-80 [1] to track breaking changes that should be done in 
> Ignite 2.x.
>
> We agreed on the following algorithm to deal with breaking changes:
>
> - Ignite 2.[x] - deprecate the API + notification of the users.
> - Ignite 2.[x+1] - API removal.
>
>
> I propose to start these improvements with the d (depuration & removal) of 
> the following features:
>
> - LOCAL caches
> - MVCC caches
> - legacy service grid implementation
> - legacy JMX metrics beans.
>
> Deprecation in 2.12
> Removal in 2.13
>
> Please, share your opinion.
>
> [1] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334475



-- 
Best wishes,
Amelchev Nikita

Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]

[Nikita Amelchev]

Igniters,

Scope freeze is planned for Friday, October 15.
I suggest creating the release branch on that date.

The wiki page with the release info. [1] Please, check the fix version
of your issues.

There are no unresolved blockers.
There are 3 important issues in the review state. [2]

Also, please, pay attention to unresolved documentation issues. [3]

[1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
[2] 
https://issues.apache.org/jira/issues/?jql=(resolution%20%3D%20Unresolved%20AND%20project%20%3D%20%27Ignite%27%20AND%20type%20in%20(%22New%20Feature%22%2C%20Task%2C%20Sub-task%2C%20Improvement)%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20AND%20(labels%20in%20(%27important%27)%20OR%20Flags%20%3D%20Important))%20order%20by%20summary
[3] 
https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20

пт, 1 окт. 2021 г. в 19:06, Pavel Tupitsyn :
>
> I'm working on IGNITE-15504 and plan to finish it early next week.
>
> On Fri, Oct 1, 2021 at 6:08 PM Nikita Amelchev  wrote:
>
> > Igniters,
> >
> > I have created the wiki page for the 2.12 release. [1]
> >
> > The release scope contains 1 issue that is marked as a blocker:
> > IGNITE-15504 .NET: SDK 2.1 is out of support, make sure project can be
> > developed with newer SDKs [2]
> >
> > Folks, do not forget to document features (65 issues still not resolved).
> > [3]
> >
> > Maxim, Ivan,
> > +1 to add these issues to the 2.12 scope.
> >
> > [1] https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.12
> > [2] https://issues.apache.org/jira/browse/IGNITE-15504
> > [3]
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20
> >
> > ср, 29 сент. 2021 г. в 11:28, Ivan Daschinsky :
> > >
> > > Created issues related building ODBC module, running C++ suites and
> > > removing VS project files
> > >
> > > 1. https://issues.apache.org/jira/browse/IGNITE-15637
> > > 2.https://issues.apache.org/jira/browse/IGNITE-15636
> > >
> > > вс, 26 сент. 2021 г. в 19:50, Ivan Daschinsky :
> > >
> > > > +1
> > > >
> > > > Let's consider building odbc driver using Visual C++ 2017?
> > > >
> > > > 2015, 2017 and 2019 share the same redistributable package and it is
> > the
> > > > default one in Windows 10.
> > > >
> > > > Also, let's remove vs project files, since the most of you all agree
> > that
> > > > it is redundant.
> > > >
> > > > If both suggestions are ok, I will create ticketa soon.
> > > >
> > > > вс, 26 сент. 2021 г., 17:10 Pavel Tupitsyn :
> > > >
> > > >> +1
> > > >>
> > > >> On Fri, Sep 24, 2021 at 8:04 PM Maxim Muzafarov 
> > > >> wrote:
> > > >>
> > > >> > Hello Nikita,
> > > >> >
> > > >> > +1 if you will lead this release.
> > > >> >
> > > >> >
> > > >> > I'd suggest including into the release scope this one issue too:
> > > >> >
> > > >> > Snapshot restore must support restoring with indexes rebuild
> > > >> > https://issues.apache.org/jira/browse/IGNITE-14744
> > > >> >
> > > >> > Hopefully, it will be completed by the end of October.
> > > >> >
> > > >> > On Fri, 24 Sept 2021 at 19:48, Nikita Amelchev <
> > namelc...@apache.org>
> > > >> > wrote:
> > > >> > >
> > > >> > > Dear Ignite Community!
> > > >> > >
> > > >> > > I suggest starting Apache Ignite 2.12 release activities.
> > > >> > >
> > > >> > > For now, we've accumulated a hundred resolved issues with new
> > features
> > > >> > > and bug fixes which are waiting for their release date. For
> > example,
> > > >> > >
> > > >> > > CDC Application
> > > >> > > Index Query API
> > > >> > > Utility for analyzing indexes
> > > >> > > Java compute tasks for C++
> > > >> > > SQL commands statistics
> > > >> > > etc.
> > > >> > >
> > > >> > > I want to propose myself to be the release manager of the planning
> > > >> > release.
> > > >> > >
> > > >> > > I propose the following timeline:
> > > >> > >
> > > >> > > Scope Freeze: October 15, 2021
> > > >> > > Code Freeze: October 29, 2021
> > > >> > > Voting Date: November 15, 2021
> > > >> > > Release Date: November 22, 2021
> > > >> > >
> > > >> > > WDYT?
> > > >> > >
> > > >> > > --
> > > >> > > Best wishes,
> > > >> > > Amelchev Nikita
> > > >> >
> > > >>
> > > >
> > >
> > > --
> > > Sincerely yours, Ivan Daschinskiy
> >
> >
> >
> > --
> > Best wishes,
> > Amelchev Nikita
> >



-- 
Best wishes,
Amelchev Nikita

Re: Move Azure, AWS, GCE to the ignite-extensions

[Nikita Amelchev]

+1 to migrate and include to the Ignite 2.12 scope

пн, 20 сент. 2021 г. в 17:09, Denis Magda :
>
> Perfect, thanks, Maxim!
>
> -
> Denis
>
>
> On Mon, Sep 20, 2021 at 8:29 AM Maxim Muzafarov  wrote:
>
> > Folks,
> >
> >
> > I've created an issue [1] to move all cloud-based IP-finders to the
> > ignite-extensions. The motivation is the same as with migration of
> > Spring Data integration - to remove integration dependency of the
> > release cycle on Ignite releases.
> >
> >
> > [1] https://issues.apache.org/jira/browse/IGNITE-15541
> >



-- 
Best wishes,
Amelchev Nikita

Re: [DISCUSS] Release spring-tx-ext and spring-cache-ext Ignite extensions

[Nikita Amelchev]

Folks, we should release the spring-data-commons module with the 1.1.0
version to release spring-tx, spring-cache modules.
It contains some proxies required for the new modules.

I suggest:

1. Release the spring-data-commons 1.1.0, spring-tx 1.0.0,
spring-cache 1.0.0 modules with separate source packages:

/ignite/ignite-extensions/ignite-spring-data-commons/1.1.0/[src]
/ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0/[src]
/ignite/ignite-extensions/ignite-spring-cache-ext/1.0.0/[src]

(The spring-data-commons 1.0.0 was included in the
ignite-spring-data-all-ext/1.0.0 source package)

2. Use one voting thread for this activity.

Any objections?

пт, 24 сент. 2021 г. в 15:14, Nikita Amelchev :
>
> Igniters,
>
> Since Ignite 2.11 has been released the following extension modules
> can be released too:
>
> spring-cache-ext
> spring-tx-ext
>
> I want to be a release manager for these if nobody minds.
>
> The release process can be started after checking documentation.
>
> --
> Best wishes,
> Amelchev Nikita



-- 
Best wishes,
Amelchev Nikita

Re: [VOTE] Create separate Jira project and Confluence space for Ignite 3

[Nikita Amelchev]

+1

вт, 5 окт. 2021 г. в 11:41, Ivan Pavlukhin :
>
> 0 from me.
>
> > Voting ends in 72 hours, at 5pm PDT on October 7:
>
> I suggest to prolong voting at least till the end of the week. I see
> no reason to have such limited timeframe. Whole week including a
> weekend will allow more people to cast votes.
>
> 2021-10-05 10:06 GMT+03:00, ткаленко кирилл :
> > +1
> >
> > 05.10.2021, 02:52, "Valentin Kulichenko" :
> >> Hello Community,
> >>
> >> As discussed in [1], I would like to propose the creation of a separate
> >> Jira project and Confluence space for Ignite 3.
> >>
> >> Ignite 2 and Ignite 3 are developed in parallel in separate repos, so we
> >> need a clear separation in other tools as well - this will help to
> >> streamline the development process. Please refer to the discussion for
> >> more
> >> details.
> >>
> >> [1]
> >> https://lists.apache.org/thread.html/rdcad3fc64b9f3a848c93089baae2bee1124a97869a94f4a04dd80fdf%40%3Cdev.ignite.apache.org%3E
> >>
> >> Voting options:
> >>
> >>- +1 - Agree with the suggestion
> >>- 0 - Don't care much about the suggestion
> >>- -1 - Disagree with the suggestion
> >>
> >> This is a majority vote.
> >>
> >> Voting ends in 72 hours, at 5pm PDT on October 7:
> >> https://www.timeanddate.com/counters/fullscreen.html?mode=a=20211007T17=2021=10=7=17=0=0=224
> >>
> >> -Val
> >
>
>
> --
>
> Best regards,
> Ivan Pavlukhin



-- 
Best wishes,
Amelchev Nikita