You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by Dmitry Pavlov <dp...@gmail.com> on 2018/06/26 18:05:06 UTC

Ignite 2.6 E.R. Code freeze

Hi Folks,


I hope you’re doing absolutely well.

Apache Ignite 2.6 (emergency release) code freezed with 14 following
changes (see below). Issues merged to master were migrated to 2.7 version,
same for not closed issues.


Please double check if there is any missed issue on the release page
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.6

Sincerely,

Dmitriy Pavlov

[IGNITE-8530] Exchange hangs during start/stop stress test

[IGNITE-8476] AssertionError exception occurs when trying to remove node
from baseline under loading

[IGNITE-8565] Arbitrary code execution from GridClientJdkMarshaller

[IGNITE-8804] Windows WSL configuration has to be added to Ignite configs

[IGNITE-8807] Apache Ignite Linux packages 2.6 update

[IGNITE-8740] Support reuse of already initialized Ignite in
IgniteSpringBean

[IGNITE-8768] JVM crash in PDS1 suite in master branch

[IGNITE-8685] Incorrect size for switch segment record

[IGNITE-8561] SinglSegmentLogicalRecordsIterator is broken

[IGNITE-7896] Files of evicted partitions are not removed from disk storage

[IGNITE-8682] Attempt to configure IGFS in persistent mode without specific
data region ends with AssertionError

[IGNITE-8713] Security vulnerabilities in
spring-data-commons-1.13.1.RELEASE.jar

[IGNITE-8722] Issue in REST API 2.5

[IGNITE-8534] Upgrade Ignite Spark Module's Spark version to 2.3.0