The provisional results of the SIP committee are in for the current pending SIPS. The http://docs.scala-lang.org/sips website has been updated with the provisional voting status of each SIP. When final action occurs, SIPS will be moved into their new locations. (pending, accepted or rejected).
When a release is drawing near, the SIP committee will hold on provisonal vote on pending SIPs. This vote places sips in one of the current status:
* `Accepted` - The SIP will be included in the next release, pending an acceptable implementation.
* `Deferred` - The committee has concerns that need to be addressed in the SIP before inclusion in the Release. If the concerns are handled before the next release, the SIP will be re-evaluated.
* `Postponed` - The SIP comittee has larger concerns with the state of the SIP and would prefer to wait until a later Scala release to consider inclusion.
* `Not Accepted` - The SIP comittee feels the SIP is not needed for the Scala language and turns down the proposal, with an explanation of why.
What happens for a Scala major release?
Before a Scala release, the committee will make a final decision for each SIP whether it should be accepted, rejected, or delayed for the next release. Accepted SIPs will be rolled into an upcoming Scala release and placed in the accepted folder. Rejected SIPs will be left in the SIP repository under the "rejected sips" section. Delayed SIPs will remain pending.
And without further ADO, the voting status on each sip:
SIP-11 - String Interpolation
This SIP is in `Accepted` status currently. We expect a SIP for 2.11 that will allow the desugared form of interpolated strings in the pattern matcher to become valid syntax. This SIP only allows the sugared interpolated strings to work.
SIP-12 Uncluttering Scala’s syntax for control structures