Hi everyone, Following the feedback, I've split the original proposal into two PRs:
- Public API, observable behavior, and compatibility contracts [1]. - RFC development process [2]. Let's discuss the API definitions first, then the process. The original PR [3] is now closed; please continue the discussion in the relevant new PR. Thanks, Anton [1] https://github.com/apache/ignite/pull/13759 https://issues.apache.org/jira/browse/IGNITE-29219 [2] https://github.com/apache/ignite/pull/13760 https://issues.apache.org/jira/browse/IGNITE-29220 [3] https://github.com/apache/ignite/pull/13740 On Fri, Oct 23, 2026 at 11:09 PM Anton Vinogradov <[email protected]> wrote: > Hi everyone, > > Following our discussion, I've opened the first RFC [1] under IGNITE-29201 > [2]. > > It defines what counts as a public API and how we review API, protocol, > and storage changes through tickets and PRs, including approval from at > least three Ignite committers. > > Please take a look and share your thoughts, especially on the scope and > approval process. Comments in the PR are welcome; let's keep broader > process questions on this list. > > [1] https://github.com/apache/ignite/pull/13740 > [2] https://issues.apache.org/jira/browse/IGNITE-29201 > > Thanks, > Anton >
