<div dir="ltr"><span style="font-size:12.800000190734863px"> • What is your evaluation of the proposal?</span><div>+ 1<br style="font-size:12.800000190734863px"><span style="font-size:12.800000190734863px"> • Is the problem being addressed significant enough to warrant a change to Swift?</span></div><div>Yes<br style="font-size:12.800000190734863px"><span style="font-size:12.800000190734863px"> • Does this proposal fit well with the feel and direction of Swift?</span></div><div>Yes<br style="font-size:12.800000190734863px"><span style="font-size:12.800000190734863px"> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</span></div><div>Yes. It's about the same.<br style="font-size:12.800000190734863px"><span style="font-size:12.800000190734863px"> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</span><br style="font-size:12.800000190734863px"><span style="font-size:12.800000190734863px">More information about the Swift evolution process is available at</span><br></div><div><span style="font-size:12.800000190734863px">A quick read.</span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 30, 2017 at 3:41 PM, David Sweeris via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
> On Jan 24, 2017, at 10:18 AM, Daniel Dunbar <<a href="mailto:daniel_dunbar@apple.com">daniel_dunbar@apple.com</a>> wrote:<br>
><br>
> Hello Swift community,<br>
><br>
> The review of SE-0150 “ Package Manager Support for branches" begins now and runs through January 31, 2017. The proposal is available here:<br>
><br>
> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0150-package-manager-branch-support.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>proposals/0150-package-<wbr>manager-branch-support.md</a><br>
><br>
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-build-dev and swift-evolution mailing lists at<br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-build-dev" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-build-<wbr>dev</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
> or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:<br>
> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0150-package-manager-branch-support.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>proposals/0150-package-<wbr>manager-branch-support.md</a><br>
><br>
> What goes into a review?<br>
><br>
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:<br>
><br>
> • What is your evaluation of the proposal?<br>
</span>+1<br>
I would even go a bit further and suggest that "Package(url: String, branch: String)” should have “master” be the default value for `branch`, to make it simpler for small developer teams who don’t necessarily have all the collaboration issues of large projects.<br>
<span class=""><br>
> • Is the problem being addressed significant enough to warrant a change to Swift?<br>
</span>IMHO, yes. Particularly since Xcode doesn’t support git tags (that I can find, anyway)<br>
<span class=""><br>
> • Does this proposal fit well with the feel and direction of Swift?<br>
</span>IMOH, yes. This proposal will make development with much easier for programmers whose work-flow is branch-based rather than tag-based.<br>
<span class=""><br>
> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
</span>An embarrassingly long time trying to figure out why a package wasn’t seeing changes I’d committed to one of its dependencies... Somewhere along the line I must’ve accidentally created a branch called “1.0.0”, which lead to me conflating the 1.0.0 tag with the 1.0.0 branch, which has caused me no end of head scratching.<br>
<br>
- Dave Sweeris<br>
<div class="HOEnZb"><div class="h5">______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br></div>