[MTCGA]: new failures in builds [6473335] needs to be handled

2022-06-08 Thread ignitetcbot
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize

[MTCGA]: new failures in builds [6472700] needs to be handled

2022-06-08 Thread ignitetcbot
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master IgniteWalRebalanceTest.testWithGlobalWalChange https://ci2.ignite.apache.org/test/690561471127920978?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3

Re: .NET Build and Versioning Improvements

2022-06-08 Thread Maxim Muzafarov
Folks, Make sense. Another tricky question is - can we have the following version committed in the source files 2.14.0.0, but when the 'release' profile get activated (or probably the build happened) revision number will changed to 2.14.0.62943? This will be the final release version ready for dep

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Andrey Gura
Alexander, It looks like a blocker. The issue has been targeted to alpha5 release. On Wed, Jun 8, 2022 at 7:30 PM Alexander Polovtcev wrote: > > Hello, dear Igniters. > I've discovered a bug regarding the Pluggable Storage Engines feature. > Please consider adding it to the release scope: > http

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Alexander Polovtcev
Hello, dear Igniters. I've discovered a bug regarding the Pluggable Storage Engines feature. Please consider adding it to the release scope: https://issues.apache.org/jira/browse/IGNITE-17139 On Mon, Jun 6, 2022 at 5:56 PM Andrey Gura wrote: > Igniters, > > our release schedule has shifted a bit

Re: .NET Build and Versioning Improvements

2022-06-08 Thread Pavel Tupitsyn
> As for the last number in .NET version, AFAIK it is used as the unique > build id and is required for nightly builds as nuget doesn't have > functionality a-la maven's 'snapshots' NuGet supports string suffixes like 2.15.0-nightly1. However, AssemblyVersionAttribute does not. In some cases it is

Re: .NET Build and Versioning Improvements

2022-06-08 Thread Ivan Daschinsky
As for the last number in .NET version, AFAIK it is used as the unique build id and is required for nightly builds as nuget doesn't have functionality a-la maven's 'snapshots' ср, 8 июн. 2022 г. в 16:07, Ivan Daschinsky : > Since nuget packages have been built on the same linux agent as the main

Re: .NET Build and Versioning Improvements

2022-06-08 Thread Ivan Daschinsky
Since nuget packages have been built on the same linux agent as the main release, it sounds logical to me that this step can be done within the maven lifecycle. I am for it, +1 ср, 8 июн. 2022 г. в 15:13, Maxim Muzafarov : > Hello Igniters, > > > I'd like to simplify the release build for the Apa

Re[2]: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Игорь Гусев
Please merge the remaining doc issue https://issues.apache.org/jira/browse/IGNITE-17106   >Среда, 8 июня 2022, 15:58 +04:00 от Andrey Gura : >  >Thanks, Yuri! > >On Wed, Jun 8, 2022 at 1:48 PM Юрий < jury.gerzhedow...@gmail.com > wrote: >> >> Seems SQL API: Add batched DML queries support [1] w

.NET Build and Versioning Improvements

2022-06-08 Thread Maxim Muzafarov
Hello Igniters, I'd like to simplify the release build for the Apache Ignite. My suggestion here are: 1. Mavenize the building procedure of the 'platform/donet' thin client (use maven with Ant task) 2. Change it's versions to fit the Ignite style. = 1. Build = Add a pom.xml sub-project with a

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Andrey Gura
Thanks, Yuri! On Wed, Jun 8, 2022 at 1:48 PM Юрий wrote: > > Seems SQL API: Add batched DML queries support [1] will be moved to next > alpha, so pleas don't waiting for it. > > In the same time SQL API: Examples [2] already done and merged to alpha 5 > branch. > > [1] https://issues.apache.org/

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Юрий
Seems SQL API: Add batched DML queries support [1] will be moved to next alpha, so pleas don't waiting for it. In the same time SQL API: Examples [2] already done and merged to alpha 5 branch. [1] https://issues.apache.org/jira/browse/IGNITE-16963 [2] https://issues.apache.org/jira/browse/IGNITE

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Andrey Gura
Pavel, The issue is targeted to the alpha5 release. On Wed, Jun 8, 2022 at 11:13 AM Pavel Tupitsyn wrote: > > Igniters, I'd like to include the following ticket as well: > IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client > [1] > > Would be great to have the same API avai

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Andrey Gura
On Wed, Jun 8, 2022 at 11:13 AM Pavel Tupitsyn wrote: > > Igniters, I'd like to include the following ticket as well: > IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client > [1] > > Would be great to have the same API available in server and client modes. > It'll be in main i

Re: [ANNOUNCE] Apache Ignite 3.0.0 alpha 5: Code freeze

2022-06-08 Thread Pavel Tupitsyn
Igniters, I'd like to include the following ticket as well: IGNITE-17057 Thin 3.0: Implement synchronous SQL API for java thin client [1] Would be great to have the same API available in server and client modes. It'll be in main in a couple hours. [1] https://issues.apache.org/jira/browse/IGNITE-