Skip to content

alter wording in SIP process about flags #1970

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 26, 2021
Merged

alter wording in SIP process about flags #1970

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions _sips/sip-submission.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,10 +150,11 @@ the formal evaluation phase.

### Merging the proposal

If the SIP is accepted, the committee will propose a release date to the
compiler maintainers, where the role of the committee ends. Accepted SIPs will
then be merged under a flag. When SIPs introduce intricate changes and they
cannot be merged under a flag, the compiler maintainers will merge it directly.
If the SIP is accepted, the committee will propose a release date to
the compiler maintainers, where the role of the committee ends.
(Compiler maintainers may choose to merge changes under a flag
initially, for testing, or directly, as they deem appropriate,
taking committee and community feedback into consideration.)

## Structure of the process

Expand Down