Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*Test with high flaky rate in master
IgniteClientReconnectMassiveShutdownSslTest.testMassiveServersShutdown2
Hi,
To my opinion it's fine, since we freezed release scope, but haven't freezed
the code yet.
So, we're at Phase2 - Rampdown phase -
https://cwiki.apache.org/confluence/display/IGNITE/Release+Process
Code freeze is planned to 14 June, see also
Hi ! I found that very important issue [1] (already in master) is not planned
to be in 2.11, may be it still possible to take it into scope ?
thanks !
[1] https://issues.apache.org/jira/browse/IGNITE-14739
>Hi Folks,
>
>Branch divergence has been completed. Sorry for the delay, it was my
Igniters,
Let me present a framework, we developed, that allows automating Apache
Ignite testing on a real cluster.
The framework was initially presented at Ignite Summit.
In brief,
The framework allows automating operations with any applications on a real
cluster using ssh in a form of a python
Hi Folks,
Branch divergence has been completed. Sorry for the delay, it was my fault. Now
branch for 2.11 is now available
https://github.com/apache/ignite/tree/ignite-2.11
https://gitbox.apache.org/repos/asf?p=ignite.git;a=shortlog;h=refs/heads/ignite-2.11
Who could help with updating TC bot
