Denis,
The post is added:
https://blogs.apache.org/ignite/entry/apache-ignite-2-11-stabilization
I've fixed the image according to your suggestions.
On Mon, 20 Sept 2021 at 21:35, Denis Magda wrote:
>
> Maxim, thanks for driving the release and preparing the announcement
> article!
>
> A few qu
Maxim, thanks for driving the release and preparing the announcement
article!
A few questions:
- Should "dev" be replaced with "2.11" on the picture of the cellular
clusters deployment section?
- Will the article be published on our blogs.apache.org page?
-
Denis
On Sat, Sep 18, 2021
The Apache Ignite Community is pleased to announce the release of
Apache Ignite 2.11.0.
Apache Ignite® is a Distributed Database For High-Performance
Computing With In-Memory Speed.
https://ignite.apache.org
The Apache Ignite Community has fixed a lot of bugs in the 2.11.0
release and made some v
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"Looks like [Running Ignite with Java 11 or later] link is broken." by
tim239
View feedback
https://app.bugyard.io/web/app/rycqZJDyY/f/61488444507c91001448c81c
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 depen
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-1554
+1
Since we've agreed that there are two projects (that are Ignite2 and Ignite3),
separate development environments seem to be logical and natural course of
things.
> On 18 Sep 2021, at 12:42, Alexander Polovtcev wrote:
>
> +1
> This is a welcome proposal, because we already have some pending
