<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class="">Hi everyone,</div><div class=""> </div><div class="">In mid-February we kicked of "stage 2" for the discussion of evolution proposals for Swift 4:</div><div class=""> </div><div class=""> <a href="https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170213/032116.html" class="">https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170213/032116.html</a></div><div class=""> </div><div class="">The timetable set forth was to have discussions for "stage 2" go through April 1. The intent of that timetable was to (a) timebox discussions on proposals to help *focus* them within the theme/focus areas of the release and to (b) provide time after discussion to *implement* approved proposals for Swift 4.</div><div class=""> </div><div class="">While the April 1 date for the end of stage 2 has passed, it is clear that by looking at where we are in the development of Swift 4 and what remains to be done that there are still important discussions happening on swift-evolution concerning changes possibly impacting Swift 4. Those discussions should continue and given the opportunity to converge. That said, we have reached to point where we need to be increasingly circumspect on what topics remain in scope for Swift 4.</div><div class=""><br class=""></div><div class="">At this point, discussions about changes impacting Swift 4 should generally focus in the following areas:</div><div class=""><ul class=""><li class="">Anything fitting in the "stage 1" phase for the release, such as (among others) the `String` re-evaluation and the memory ownership model remain priority topics to discuss.<br class=""><br class=""></li><li class="">*Existing* topics we have already covered during "stage 2" also remain relevant to discuss for the release, although the scope of actual change we will consider for Swift 4 is rapidly diminishing.</li></ul></div><div class="">The distinction of what is "out-of-scope" may not always be clear to everyone, and the Core Team will try and provide clear guidance as discussions happen on swift-evolution where appropriate to indicate whether or not something is in scope for Swift 4.</div><div class=""> </div><div class="">Looking beyond Swift 4, serious discussion about Swift 5 will likely start up in July as the themes and focus areas of that release are identified.</div><div class=""><br class=""></div><div class="">Thank you to everyone who has contributed to the discussions so far to help shape Swift 4!</div><div class=""><br class=""></div><div class="">Ted</div></body></html>