<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="">Hi Alex,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Oct 12, 2016, at 9:52 AM, Alex Blewitt via swift-corelibs-dev &lt;<a href="mailto:swift-corelibs-dev@swift.org" class="">swift-corelibs-dev@swift.org</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I have a couple of Calendar related fixes into swift-corelibs-foundation master:<div class=""><br class=""></div><div class=""><div class=""><a href="https://github.com/apple/swift-corelibs-foundation/pull/675" class="">https://github.com/apple/swift-corelibs-foundation/pull/675</a></div></div><div class=""><a href="https://github.com/apple/swift-corelibs-foundation/pull/677" class="">https://github.com/apple/swift-corelibs-foundation/pull/677</a></div><div class=""><br class=""></div><div class="">How do I go about cherry-picking these to be in the next release? There are several remote branches that have the 'swift-3' moniker including several 'preview' ones:</div><div class=""><br class=""></div><div class="">&nbsp;&nbsp;origin/swift-3<br class="">&nbsp;&nbsp;origin/swift-3.0-branch<br class="">&nbsp;&nbsp;origin/swift-3.0-preview-1-branch<br class="">&nbsp;&nbsp;origin/swift-3.0-preview-2-branch<br class="">&nbsp;&nbsp;origin/swift-3.0-preview-3-branch<br class="">&nbsp;&nbsp;origin/swift-3.0-preview-4-branch<br class="">&nbsp;&nbsp;origin/swift-3.0-preview-5-branch<br class="">&nbsp;&nbsp;origin/swift-3.0-preview-5-speculative<br class="">&nbsp;&nbsp;origin/swift-3.0.1-preview-2-branch<br class=""><br class=""></div><div class="">Why are we representing previews as branches, instead of tags? If I wanted to submit a pull request for one of these previews, it's not clear which one(s) I should target.</div></div></div></blockquote><div><br class=""></div><div>I agree this is a bit confusing.</div><div><br class=""></div><div>Right now, swift-3.0-branch is the one that is used as the “development” branch for any updates to swift 3.0.</div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">There are also a number of branches that are old (in many cases, over a month):</div><div class=""><br class=""></div><div class="">&nbsp;&nbsp;origin/dabrahams-patch-1<br class="">&nbsp;&nbsp;origin/dabrahams-patch-2<br class="">&nbsp;&nbsp;origin/data-associated-type-fixes-3.0<br class="">&nbsp;&nbsp;origin/more_value_types<br class="">&nbsp;&nbsp;origin/nscoding<br class="">&nbsp;&nbsp;origin/revert-540-SR-2151<br class="">&nbsp;&nbsp;origin/revert-567-pr-grabbag<br class=""><br class=""></div><div class="">Can we get these cleaned up if they are no longer necessary?</div><div class=""><br class=""></div><div class="">Alex</div></div></div></blockquote><div><br class=""></div>Yes, I think we should delete these. I’ll do that for a bunch of these.</div></div><div><br class=""></div><div>- Tony</div><div><br class=""></div></body></html>