Repository navigation
Add the RFC process - #42
Merged
Merged
Conversation
Contract changes (scene components, splashpack writer) get the rfc label and a seven-day window before they can merge. See RFC.md.
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.
Same process as #30: a pull request that changes what users' scenes or the runtime depend on gets the
rfclabel and can't merge for seven days. The workflow and script are psxsplash's copy unchanged; RFC.md and the stakeholder list are scoped to this repo's contracts, the scene components' serialized fields and the splashpack writer.The
rfc-moratoriumrequirement onmaingoes on after this merges, since the check doesn't exist before then. Open RFCs are tracked in #41.