Pavel, currently they offers only free 14-day trial, unfortunately
чт, 30 дек. 2021 г. в 13:16, Pavel Tupitsyn :
> Ivan,
>
> MyGet is free within some limits.
> It was introduced to make release verification easier - no need to unzip
> nuggets into a local dir, just install them from MyGet.
>
>
Ivan,
MyGet is free within some limits.
It was introduced to make release verification easier - no need to unzip
nuggets into a local dir, just install them from MyGet.
Nikita,
No, we won't upload NuGet packages to any registry before a successful RC
vote.
Only then we'll push them to nuget.org
I'm sorry, but I've never understand the purpose of uploading to MyGet. It
is not free registry and it is required to pay to use it.
чт, 30 дек. 2021 г. в 12:34, Nikita Amelchev :
> Pavel, thank you.
>
> The "[3] Build & Upload Nuget Staging Packages" configuration also
> pushes packages to the
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
>
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
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]
>
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
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
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
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 г. в
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, 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!
>
>
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
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
>
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
+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
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
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
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
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
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
>
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]
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]
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
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
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 г.
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
> > написал(а):
> >
>
> [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
>>
>>
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
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:
>
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]
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
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.
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
>
>
>
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
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
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
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
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
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
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
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]
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,
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?
> >
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 :
>
>
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.
>
> пт,
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
>
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
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]
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
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.
>
>
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?
>
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
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
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
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
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
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'
Release build issues (IGNITE-15779) should be resolved now.
On Fri, Oct 22, 2021 at 5:38 PM Сергей Утцель wrote:
> I configured TC bot to 'ignite-2.12' instead of 'ignite-2.11'
>
I configured TC bot to 'ignite-2.12' instead of 'ignite-2.11'
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
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
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 :
> >
> >>
> >>
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
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:
>
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
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,
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
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
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
+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
+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
>
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
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
75 matches
Mail list logo
