...
All the development for the Apache Ignite 3.x happens in the dedicated repository: https://github.com/apache/ignite-3
TeamCity is currently set up to run all available JUnit tests (this will be changed in the future): https://ci.ignite.apache.org/project/ignite3
TeamCity triggers the test run for a pull request when it's created or updated. Upon completion, the PR is updated with the corresponding status which is shown as a successful or failed check.
The basic process to make a change is the following:
On the week of Sep 14th, we had two virtual events where the community discussed the proposed changes.
In English:
Widget Connector | ||
---|---|---|
|
In Russian:
Widget Connector | ||
---|---|---|
|
Slides are available here.
...
Some of the modules (mainly, integration components and thin clients) can be isolated into separate projects with independent lifecycles.
Ignite 3.0 is a major release, which gives us a unique opportunity to make incompatible changes. This can be used to do a cleanup and remove deprecated APIs and features. Additionally, all APIs should be revisited from this point of view – anything that is not relevant anymore should be removed from the project; some APIs can be reworked and modernized.
TBD: full list of removals.
GraalVM is gaining a lot of popularity, especially in the context of serverless environments and frameworks like Micronaut and Quarkus. Currently, even Ignite thin client blocks software from being built into a native GraalVM image – this needs to be fixed. Preferably, we should support this for thick clients as well, although this is a lower priority and might require much bigger effort.
...
.
Ignite 3.0 is a major release, which gives us a unique opportunity to make incompatible changes. This can be used to do a cleanup and remove deprecated APIs and features. Additionally, all APIs should be revisited from this point of view – anything that is not relevant anymore should be removed from the project; some APIs can be reworked and modernized.
List of proposed removals (WIP):
*Resource
annotations except for the IgniteInstanceResource
CacheRebalanceMode
and rebalance delay - should always work in the ASYNC
mode (current default)ASYNC
makes sense) and parametersIgniteFuture
with Java's CompletableFuture
String
, not a generic Serializable
objectLabel ignite-3
is used for any issues in JIRA that are related to Ignite 3.x.
Jira server ASF JIRA columns key,summary,type,updated,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=12349470 serverId 5aa69414-a9e9-3523-82ec-879b028fb15b