Haven’t had a chance to catch up on the latest discussion, but I just saw that
the Yarn developers posted an excellent piece on lockfiles this week:
They argue lockfiles should be commited by libraries (but still ignored by
applications). The essential point is that this makes it easier for developers
of the library to maintain a coherent build of the library when dependencies
ship a bug. The focus is particularly on new developers, who would otherwise
lack a lockfile.
> On Nov 20, 2016, at 12:48 AM, Anders Bertelrud <and...@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:
> 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
> or, if you would like to keep your feedback private, directly to the review
> 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
> * 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
> Thank you,
> Anders Bertelrud
> Review Manager
> swift-evolution-announce mailing list
swift-evolution mailing list