Skip to content

Add new proposal state, clarify misunderstanding #542

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
Jul 15, 2016
Merged

Add new proposal state, clarify misunderstanding #542

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
8 changes: 5 additions & 3 deletions sips/sip-submission.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,9 +135,11 @@ Based on the feedback, the SIP is either:
1. Accepted, in which case the committee will propose a release date to the
compiler maintainers, where the role of the committee ends.
2. Rejected, in which case the SIP is closed and no longer evaluated in the future.
3. Postponed, in which case the reviewer responds to the committee’s feedback in
the SIP issue tracker, and the SIP is scheduled for a follow-up discussion
during the next SIP meeting.
3. Postponed, in which case the committee sets aside the SIP under some conditions.
When those conditions are met, the SIP can be resubmitted.
4. Under revision, in which case the author needs to continue the formal evaluation
and address all the committee's feedback. Thus, the follow-up discussion is scheduled
for the next iteration.

If no changes have been made to a SIP in two iterations, it’s marked as dormant
and both the PR and issue are closed. Dormant SIPs can be reopened by any
Expand Down