You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Before you initiate a pull request**, please read the process document. Ideas should be thoroughly discussed on the [swift-evolution mailing list](https://swift.org/community/#swift-evolution) first.
5
+
**Before you initiate a pull request**, please read the process document. Ideas should be thoroughly discussed on the [swift-evolution forums](https://swift.org/community/#swift-evolution) first.
6
6
7
7
This repository tracks the ongoing evolution of Swift. It contains:
Copy file name to clipboardExpand all lines: process.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -44,15 +44,15 @@ Please state explicitly whether you believe that the proposal should be accepted
44
44
45
45
## How to propose a change
46
46
47
-
***Check prior proposals**: many ideas come up frequently, and may either be in active discussion on the mailing list, or may have been discussed already and have joined the [Commonly Rejected Proposals](commonly_proposed.md) list. Please check the mailing list archives and this list for context before proposing something new.
47
+
***Check prior proposals**: many ideas come up frequently, and may either be in active discussion on the forums, or may have been discussed already and have joined the [Commonly Rejected Proposals](commonly_proposed.md) list. Please [search the forums](https://forums.swift.org/search) for context before proposing something new.
48
48
***Consider the goals of the upcoming Swift release**: Each major
49
49
Swift release is focused on a [specific set of goals](README.md)
50
50
described early in the release cycle. When proposing a change to
51
51
Swift, please consider how your proposal fits in with the larger goals
52
52
of the upcoming Swift release. Proposals that are clearly out of scope
53
53
for the upcoming Swift release will not be brought up for review. If you can't resist discussing a proposal that you know is out of scope, please include the tag `[Out of scope]` in the subject.
54
54
***Socialize the idea**: propose a rough sketch of the idea in the ["pitches" section of the Swift forums](https://forums.swift.org/c/evolution/pitches), the problems it solves, what the solution looks like, etc., to gauge interest from the community.
55
-
***Develop the proposal**: expand the rough sketch into a complete proposal, using the [proposal template](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 *required* 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.
55
+
***Develop the proposal**: expand the rough sketch into a complete proposal, using the [proposal template](0000-template.md), and continue to refine the proposal on the forums. Prototyping an implementation and its uses along with the proposal is *required* 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.
56
56
***Request a review**: initiate a pull request to the [swift-evolution repository][swift-evolution-repo] 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.
57
57
***Address feedback**: in general, and especially [during the review period][proposal-status], be responsive to questions and feedback about the proposal.
58
58
@@ -79,7 +79,7 @@ intent during the review period.
79
79
After the review has completed, the core team will make a decision on
80
80
the proposal. The review manager is responsible for determining
81
81
consensus among the core team members, then reporting their decision
82
-
to the proposal authors and mailing list. The review manager will
82
+
to the proposal authors and forums. The review manager will
83
83
update the proposal's state in the [swift-evolution
84
84
repository][swift-evolution-repo] to reflect that decision.
0 commit comments