From 61306f03b47cb3e36af35f5ef6693e55f043db50 Mon Sep 17 00:00:00 2001 From: jvican Date: Thu, 22 Sep 2016 21:37:38 +0200 Subject: [PATCH 1/2] Make accepted clause clearer Committee asks SIP authors to update the spec and implementation after the final verdict. --- sips/sip-submission.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sips/sip-submission.md b/sips/sip-submission.md index 025a0a28c0..018b5b823f 100644 --- a/sips/sip-submission.md +++ b/sips/sip-submission.md @@ -132,10 +132,10 @@ During every iteration, the appointed reviewer presents the changes (updated design document, progress with the implementation, etc) to the SIP Committee. 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. In certain cases, - accepted proposal may need exceptional follow-up iterations to flesh out all - the details of the proposed specification or implementation. +1. Accepted, in which case the committee proposes a release date to the compiler + maintainers, where the role of the committee ends. The Committee asks authors + to update both the specification and implementation according to the final + verdict. 2. Rejected, in which case the SIP is closed and no longer evaluated in the future. 3. Under revision, in which case the author needs to continue the formal From 709c66484a00d44543031ab7a3e2f4dc34b7324c Mon Sep 17 00:00:00 2001 From: jvican Date: Fri, 23 Sep 2016 11:00:13 +0200 Subject: [PATCH 2/2] Improve wording of "release date" --- sips/sip-submission.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/sips/sip-submission.md b/sips/sip-submission.md index 018b5b823f..d60dccfe5d 100644 --- a/sips/sip-submission.md +++ b/sips/sip-submission.md @@ -132,10 +132,10 @@ During every iteration, the appointed reviewer presents the changes (updated design document, progress with the implementation, etc) to the SIP Committee. Based on the feedback, the SIP is either: -1. Accepted, in which case the committee proposes a release date to the compiler - maintainers, where the role of the committee ends. The Committee asks authors - to update both the specification and implementation according to the final - verdict. +1. Accepted, in which case the committee proposes a target Scala version to the + compiler maintainers, where the role of the committee ends. The Committee + asks authors to update both the specification and implementation according to + the final verdict. 2. Rejected, in which case the SIP is closed and no longer evaluated in the future. 3. Under revision, in which case the author needs to continue the formal