SIP-000-1: SIP Process SIP-000 Upgrade #241
Draft
+935
−0
Conversation
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
… sips/sip-000/replaced SIPs/sip-000-stacks-improvement-proposal-process.md
…eplaced SIPs/readme.md
…ip-000replaced SIP.readme.md
…rovement-proposal-process.md
…1-stacks-improvement-proposal-process.md
…ks-improvement-proposal-process.md
…1-stacks-improvement-proposal-process.md
…ks-improvement-proposal-process.md
…-stacks-improvement-proposal-process.md
… sip-000-1-stacks-improvement-proposal-process.md
…ks-improvement-proposal-process.md
1. Update Abstract to mention this replaces SIP-000 and the rationale 2. Added “## Backwards Compatibility” but it is NA 3. Moved 2 ## SIP Flow subsections together, renamed the first to SIP Status 4. Moved “## SIP Types” to logical order, after “## Layer” 5. New subsection “## SIP Layers” created by moving the explanations from Preambles 6. Preambles’ spec’s ordering of fields reordered to match the SIP_TEMPLATE 7. Added “### SIP Authoring Rules” 8. Added “### Expectation of Minimum Timelines And Rules” 9. Added “### SIP Versioning and Replacement Update Policy” 10. Added “### Documentation, Repo Maintancne, Merging into Main” Unanswered questions requiring agreeing upon: ### Hard Fork SIPs - Define process for code freeze and creation of dedicated release branches. - Only milestone changes for that release may be merged into the fork branch.
|
Added "### Post-CAB Vote Updates" details cc: @whoabuddy |
|
thanks for this! looking it over |
wileyj
reviewed
Oct 24, 2025
sips/sip-000-1/sip-000-1-stacks-improvement-proposal-process.md
Outdated
Show resolved
Hide resolved
|
Moving to draft for now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
SIP-000-1 packs a number of refinement of the SIP Process we've learned over the past few years.
Below is a "Change log" of SIP-000-1
So please welcome to make changes and add/remove suggestions!
Some unanswered questions:
Hard Fork SIPs code freeze rules - Define process for code freeze and creation of dedicated release branches. - Only milestone changes for that release may be merged into the fork branch.
SIP-000 folder naming: I tried both folder naming ideas, whether it's "_1" or "-1" (see images below), might look both little odd and confusing, I'd actually perhaps propose keeping the SIP-000 folder naming as is. Only the the MD files get updated according to the SIP-000 versioning policy, and filed correctly within.
Rider SIPs rules of engagement: How Rider SIPs should be handled approval wise. And documentation wise.