Repository navigation
docs(rfc): fold the shipped resource-ID decision into the workflow RFC - #816
Closed
behinddwalls wants to merge 1 commit into
Closed
behinddwalls wants to merge 1 commit into
behinddwalls wants to merge 1 commit into
Conversation
## Summary ### Why? Queue-scoped decimal IDs shipped (#770, #804), but the decision still lived in a standalone discussion RFC that described "current vs proposed" forms. RFCs describe the system as it is on main, so the decision belongs in the RFC that owns ID minting. ### What? - Add a **Resource IDs** section to `doc/rfc/submitqueue/workflow.md`: format, scope, what `platform/base/id` enforces, and rejected alternatives. - Delete `doc/rfc/scoped-resource-ids.md` and its index entry; the Stovepipe workflow RFC links to the new section. - Fix stale ID descriptions: history ordering no longer "parses the counter" out of `main/10`-style IDs, and the list RFC no longer mentions parsing the queue from an sqid. ## Test Plan ✅ `bazel test //tool/docsite:site_test` (strict link check) ✅ No remaining references to the deleted RFC or to prefixed IDs in Markdown, Go, or proto comments
Collaborator
Author
|
Folded into #815. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why?
Queue-scoped decimal IDs shipped (#770, #804), but the decision still lived in a standalone discussion RFC that described "current vs proposed" forms. RFCs describe the system as it is on main, so the decision belongs in the RFC that owns ID minting.
What?
doc/rfc/submitqueue/workflow.md: format, scope, whatplatform/base/idenforces, and rejected alternatives.doc/rfc/scoped-resource-ids.mdand its index entry; the Stovepipe workflow RFC links to the new section.main/10-style IDs, and the list RFC no longer mentions parsing the queue from an sqid.Test Plan
✅
bazel test //tool/docsite:site_test(strict link check)✅ No remaining references to the deleted RFC or to prefixed IDs in Markdown, Go, or proto comments