Skip to content

Annotate 34 in-flight RFCs with process transition status notes#2601

Open
kgeller wants to merge 4 commits intoelastic:mainfrom
kgeller:annotate-in-flight-rfcs
Open

Annotate 34 in-flight RFCs with process transition status notes#2601
kgeller wants to merge 4 commits intoelastic:mainfrom
kgeller:annotate-in-flight-rfcs

Conversation

@kgeller
Copy link
Copy Markdown
Member

@kgeller kgeller commented Apr 3, 2026

Summary

  • Add a process transition status note to each of the 34 RFCs that were still in-flight when the multi-stage RFC process was retired
  • Each note reflects the actual schema state: merged as GA, merged as beta, partially merged, actively being implemented, or never merged
  • 15 finished (stage 3) and 4 already-abandoned (stage X) RFCs are left untouched
  • Stage lines are preserved as-is in every RFC for historical record

This is the third of three PRs: (1) alpha maturity + remove experimental, (2) streamline RFC process, (3) annotate in-flight RFCs.

@kgeller kgeller self-assigned this Apr 3, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 3, 2026

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@kgeller kgeller marked this pull request as ready for review April 3, 2026 20:21
@kgeller kgeller requested a review from a team April 3, 2026 20:21
@trisch-me
Copy link
Copy Markdown
Contributor

Do we use these annotations somewhere? Maybe we should have a tracking table here with status for each proposed RFC? i.e. merged, partially merged, abandoned, actively working on etc.

@kgeller
Copy link
Copy Markdown
Member Author

kgeller commented Apr 7, 2026

Do we use these annotations somewhere?

Nope. I just thought the notes could come in handy for others in the future. As a part of the RFC streamlining process I just wanted to audit the state of things, and this was the output.

Maybe we should have a tracking table here with status for each proposed RFC? i.e. merged, partially merged, abandoned, actively working on etc.

We can, but I'm not sure how we'd plan to use that either.

@trisch-me
Copy link
Copy Markdown
Contributor

ok, fine with me. I think it’s nice to see the final result for those that were not properly finished.

@kgeller kgeller requested a review from a team April 8, 2026 13:43
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