Hi,
I have created and actioned a Jira ticket (
https://issues.apache.org/jira/browse/IGNITE-15602), and have a PR raised
from my fork to the main repo.
I think I have checked all the boxes except for verifying TCBot is happy
(per instruction below)
- [ ] The pull request has been checked by
Hi Denis,
Did you make any progress on this topic?
-Val
On Wed, Apr 21, 2021 at 6:11 AM Valentin Kulichenko <
valentin.kuliche...@gmail.com> wrote:
> Danis,
>
> Got it, thanks. Please provide the link to the IEP when you have one, I’d
> be happy to review!
>
> -Val
>
> On Tue, Apr 20, 2021 at
As for the original topic, we need to come to a solution. Let me summarize
what we've discussed so far.
-PROBLEM-
Ignite 3 is the next major version of Apache Ignite. It targets the same
use cases and provides a similar set of features as Ignite 2. At the same
time, Ignite 2 and Ignite 3 are
Folks,
Versioning is a separate topic. We agreed on the current scheme in March
[1]. If someone thinks we need to change it, please create a new thread and
present your suggestions.
[1]
Dear Ignite Community,
I would like someone to review change for IGNITE-15547.
It is related allowing during validation to add cache index on enums( classes)
that extend an interface.
Also as there is still failed builds on master branch, and failed tests from my
pull request are part of them,
Seems rational.
But still 2.11.0 and 21.1.0 for the time being will look like similar or error
in either version...
> On 27 Sep 2021, at 18:11, Ivan Pavlukhin wrote:
>
> I mean that Ignite 2.x will continue to use old scheme and Ignite 3
> will be e.g. Ignite 21.1 and so on.
>
> 2021-09-27
