[swift-evolution-announce] [swift-build-dev] [swift-evolution] [Review] SE-0145: Package Manager Version Pinning (Revised)
daniel_dunbar at apple.com
Fri Dec 2 11:07:20 CST 2016
> On Nov 28, 2016, at 9:44 AM, David Sweeris via swift-build-dev <swift-build-dev at swift.org> wrote:
> On Nov 19, 2016, at 23:48, Anders Bertelrud <anders at apple.com <mailto:anders at apple.com>> wrote:
>> Hello Swift community,
>> The review of "SE-0145: Package Manager Version Pinning" begins again after revisions, starting now and running through November 28th. The proposal is available here:
>> https://github.com/apple/swift-evolution/blob/master/proposals/0145-package-manager-version-pinning.md <https://github.com/apple/swift-evolution/blob/master/proposals/0145-package-manager-version-pinning.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-build-dev>
>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> or, if you would like to keep your feedback private, directly to the review manager.
>> What goes into a review?
>> The goal of the review process is to improve the proposal under review through constructive criticism and contribute to 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?
>> * Is the problem being addressed significant enough to warrant a change to Swift?
>> * Does this proposal fit well with the feel and direction of Swift?
>> * If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
>> * How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
>> More information about the Swift evolution process is available at
>> https://github.com/apple/swift-evolution/blob/master/process.md <https://github.com/apple/swift-evolution/blob/master/process.md>
>> Thank you,
>> Anders Bertelrud
>> Review Manager
>> swift-evolution-announce mailing list
>> swift-evolution-announce at swift.org <mailto:swift-evolution-announce at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution-announce <https://lists.swift.org/mailman/listinfo/swift-evolution-announce>
> Just to pick a couple nits...
> I'm not sure "pinning" is the best word, but I don't have any thoughts on what would be better.
> Does the pinning info have to be in an optional file? Would it be better to have it be an optional part of the manifest? There'd be one less file to carry around.
Even if we wanted to do this, we do not yet have the technical ability to mechanically edit the manifest file, so it needs to be separate in order to be implementable in the short term.
> I didn't follow the discussion thread very closely... If either of these "issues" were debated there, I do *not* want to start rehashing them. Furthermore, IMHO both are pretty minor (especially the first one... it's completely subjective).
> +1, either way
> - Dave Sweeris
> swift-build-dev mailing list
> swift-build-dev at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution-announce