[swift-evolution] Process question: breaking proposals for API changes to stdlib?

[Douglas Gregor]

> On Dec 4, 2015, at 1:09 PM, Andy Matuschak <andy at andymatuschak.org> wrote:
> 
> Hello, all! Process question here: if I'd like to propose an API change in stdlib, should I do that here? Open a pull request?

The first step is to post your idea here!

The actual process is described long-windedly over at

	https://github.com/apple/swift-evolution/blob/master/process.md

but the important part is:

How to propose a change

Socialize the idea: propose a rough sketch of the idea on the swift-evolution mailing list <https://swift.org/community/#swift-evolution>, the problems it solves, what the solution looks like, etc., to gauge interest from the community.
Develop the proposal: expand the rough sketch into a complete proposal, using the proposal template <https://github.com/apple/swift-evolution/blob/master/0000-template.md>, and continue to refine the proposal on the evolution mailing list. Prototyping an implementation and its uses along with the proposal is encouraged, because it helps ensure both technical feasibility of the proposal as well as validating that the proposal solves the problems it is meant to solve.
Request a review: initiate a pull request to the swift-evolution repository <https://github.com/apple/swift-evolution> to indicate to the core team that you would like the proposal to be reviewed. When the proposal is sufficiently detailed and clear, and addresses feedback from earlier discussions of the idea, the pull request will be accepted. The proposal will be assigned a proposal number as well as a core team member to manage the review.
Address feedback: in general, and especially during the review period <https://github.com/apple/swift-evolution/blob/master/schedule.md#review>, be responsive to questions and feedback about the proposal.

	- Doug


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20151204/6c3fd914/attachment-0001.html>