Skip to content

IGNITE-29201 Add RFC on public API changes - #13740

Open
anton-vinogradov wants to merge 3 commits into
apache:masterfrom
anton-vinogradov:ignite-29201-rfc-process
Open

anton-vinogradov wants to merge 3 commits into
apache:masterfrom
anton-vinogradov:ignite-29201-rfc-process

Conversation

@anton-vinogradov

@anton-vinogradov anton-vinogradov commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Adds the first RFC defining public API scope and the review process for API, protocol, and storage changes. It requires approval from three Ignite committers and explains when normal code review is enough.

CONTRIBUTING links to the RFC directory and the review process; no manual index needs updating.

Jira: https://issues.apache.org/jira/browse/IGNITE-29201

Validation: documentation-only change; checked the diff, relative links, and Apache license header. No code tests run.

- User-facing configuration, including defaults.
- Supported metrics, JMX interfaces, and system views.

The same review requirement covers client and internode protocols and persistent data formats, including metadata, WAL, and snapshots.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

plz clarify - why we need such a requirement ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants