<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Reminder: This is still on track to happen today.<div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Jul 31, 2017, at 5:34 PM, Bob Wilson via swift-dev <<a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">We now have a swift-4.1-branch of Clang/LLVM, and it is time to update our “stable” branch to use that. This transition will merge in changes to the Swift master branch from the master-next branch that we maintain to work with upstream LLVM.<div class=""><br class=""></div><div class="">We are planning to make the change <b class="">this Thursday, Aug. 3, around 2:00 pm</b> (PDT).</div><div class=""><br class=""></div><div class="">When this happens, you will need to do a clean build of Clang/LLVM along with Swift. Do not just build the “clean” target — you should completely remove your entire build directory and then rebuild from scratch. There may be some instability after this transition as uncommon problems with the new version of LLVM are discovered.</div><div class=""><br class=""></div><div class="">I’ll send a reminder on Thursday. Let me know if you have any questions or concerns.</div></div>_______________________________________________<br class="">swift-dev mailing list<br class=""><a href="mailto:swift-dev@swift.org" class="">swift-dev@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-dev<br class=""></div></blockquote></div><br class=""></div></body></html>