[swift-build-dev] [swift-evolution] [Review] SE-0150 Package Manager Support for branches

David Hart david at hartbit.com
Wed Jan 25 00:59:29 CST 2017



> On 24 Jan 2017, at 19:18, Daniel Dunbar via swift-evolution <swift-evolution at swift.org> wrote:
> 
> Hello Swift community,
> 
> The review of SE-0150 “ Package Manager Support for branches" begins now and runs through January 31, 2017. The proposal is available here:
> 
>  https://github.com/apple/swift-evolution/blob/master/proposals/0150-package-manager-branch-support.md
> 
> 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
>  https://lists.swift.org/mailman/listinfo/swift-build-dev
>  https://lists.swift.org/mailman/listinfo/swift-evolution
> 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:
>  https://github.com/apple/swift-evolution/blob/master/proposals/0150-package-manager-branch-support.md
> 
> What goes into a review?
> 
> 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:
> 
>    • What is your evaluation of the proposal?

This is going to be immensely useful. I remember depending on many `swift3` branches during the summer on my current iOS dependency manager of choice. Also applies for bug fix branches, experimental feature branches, etc...

>    • Is the problem being addressed significant enough to warrant a change to Swift?

Yes. Very significant.

>    • Does this proposal fit well with the feel and direction of Swift?

Yes.

>    • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

All other dependent managers I've used had this feature and I'v ended up using it fairly often.

>    • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

Quick reading


More information about the swift-build-dev mailing list