[67] Publish issue 67. close #224

SwiftWeekly · Apr 27, 2017 · bfc395f · bfc395f
1 parent 96d29ff
commit bfc395f
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/_drafts/2017-04-27-issue-67.md → _posts/2017-04-27-issue-67.md b/_drafts/2017-04-27-issue-67.md → _posts/2017-04-27-issue-67.md
@@ -4,8 +4,8 @@ title: ! 'Issue #67'
 author: btb
 ---
 
-A lot of proposals are being addressed this week, and Apple is working hard on an awesome Swift 4 release - and beyond.
-Also, as it's almost May, we're now just over a month away from WWDC! It will be here before you know it.
+A lot of proposals are being addressed this week, and Apple is working hard on an awesome Swift 4 release &mdash; and beyond.
+Also, it's almost May which means we're now just over a month away from WWDC! It will be here before you know it.
 
 <!--excerpt-->
 
@@ -94,7 +94,7 @@ Jordan Rose [asked for input](https://lists.swift.org/pipermail/swift-dev/Week-o
 > - We'd probably want to tweak the "aka" printing in diagnostics to not look through these typealiases. That's not hard, though.
 > - We can't keep doing this once we have ABI stability. Hopefully framework owners aren't going to continue changing Swift names of types, but we'll probably need to implement my "C name in the mangling" plan anyway, just in case.
 
-Rick Ballard [pitched a proposal](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170424/036203.html) to improve the Swift Package Manager's dependency resolution... coincidentally (?!) [after listening](https://twitter.com/rballard/status/857392666660683777) to the [Swift Unwrapped podcast](https://spec.fm/podcasts/swift-unwrapped) on this topic!
+Rick Ballard [pitched a proposal](https://lists.swift.org/pipermail/swift-evolution/Week-of-Mon-20170424/036203.html) to improve the Swift Package Manager's dependency resolution... coincidentally [after listening](https://twitter.com/rballard/status/857392666660683777) to the [Swift Unwrapped podcast](https://spec.fm/podcasts/swift-unwrapped) on this topic!
 
 > We have a proposal we'd like feedback on to revise how Swift Package Manager dependency resolution, updating, and pinning works. These changes weren't planned in the roadmap we published a few months ago, but it's become clear since then that we have some holes in our dependency resolution behavior that need fixing. We've also come to the conclusion that our original design for pinning was overcomplicated and should be revised.