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,
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
+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.
> >
>
,
Nikita Amelchev on behalf of the Apache Ignite community.
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
robably 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 A
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:
s://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 b
] 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.
>
>
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 ar
>
> > > > > 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 announ
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 sever
))%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 versio
pache.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-blo
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/d
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, 202
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;
+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,
+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.
>
>
+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
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
/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,
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
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,
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:
>
> >
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 :
> > >
> > >
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.
ср,
+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:
> >
> >
ote:
> >
> > > +1
> > >
> > > Cannot but support!
> > >
> > > Thanks,
> > > Nikita
> > >
> > > сб, 23 апр. 2022 г. в 17:47, Maxim Muzafarov :
> > >
> > > > Hello,
> > > >
> > > > +1, great im
+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
+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
/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 mo
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
://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
+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
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)
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
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
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:
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 relea
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
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 :
>
>
cExporterSpi
>
> 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 апр. 202
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
>
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:
[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.o
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 c
eeze: 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
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
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
>
/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 b
+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
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,
> > >
>
gt; >>>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
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
://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
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
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:
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
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:
release-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
; 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 :
> >
> &g
: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 Da
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
> >
cket
> 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.
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.
cessor 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
> >
> > >
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 (
>
>
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 announ
://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
] 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.o
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
>
ion 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 :
> >
> >
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/j
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
> > > 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.or
> 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 comment
ITE-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 merg
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
>
> > 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 :
> >
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:2
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
> >
> > 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 Comm
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
heev
> > 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,
&
nclude to 2.12 together with basic
> > > > > IndexQuery functionality, because this ticket provides expected
> > > behavior
> > > > of
> > > > > querying indexes - sorted over all nodes results.
> > > > >
> > > > > - IGNI
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
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
/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,
cheConfiguration#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!
> >
> &g
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?
> >
&g
es.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 Frid
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
+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] -
t; 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 ma
+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
> >
. 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
>
>
+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
1 - 100 of 252 matches
Mail list logo
