Hi Igniters, I would like to propose updating the Apache Ignite 2.x documentation for the recent 2.18 release, using a slightly different approach.
The idea is simple: documentation for features and user-visible changes already included in Ignite 2.18 should be available in the 2.18 docs branch, not only in master. Documentation for unreleased 2.19 functionality should stay in master (and here the usual process is perfectly fine). In practice, some changes were implemented by different contributors, and original authors may not always be available to write or review the docs, or may simply prefer not to contribute to this part. This is completely up to them: the community cannot demand more contribution than people are willing to provide. In such cases, we can reconstruct the behavior from code, tests, tickets, and PRs, including AI-assisted code reading where useful, and then validate the resulting documentation through normal community review. I suggest using lazy consensus for these documentation updates for missed features for 2.18: announce the intended changes in the PR and on the dev list, wait at least 72 hours, and proceed if there are no objections. This follows the usual ASF lazy consensus practice, where silence indicates assent: - https://www.apache.org/foundation/voting.html - https://community.apache.org/committers/decisionMaking.html As part of this initiative, I would also like to improve the 2.x documentation in two practical areas that may be helpful for users: troubleshooting and capacity planning. In addition, I will look for 2.18 features that are already available but still missing proper documentation. As a first step, I propose collecting the list of 2.18 features and user-visible changes that still need documentation updates, then preparing PRs where applicable. Please share any objections or suggestions. If there are no objections within 72 hours, I will assume lazy consensus and proceed. Regards, Dmitriy Pavlov
