Skip to content

Take tooling ecosystem into account #2616

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 11, 2022
Merged

Take tooling ecosystem into account #2616

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions _sips/process-specification.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -218,6 +218,12 @@ An implementation will be reviewed by the compiler team, and once the
implementation is deemed good enough, it can ship as an Experimental feature in
the following practical release of the compiler.

Often, proposals not only need to be implemented in the compiler, but also in
several other tools (IDEs, syntax highlighters, code formatters, etc.). As soon
as a proposal reaches the implementation stage, the Committee notifies the
impacted tools that they should start implementing support for it. A list of
tools of the ecosystem is maintained in [this document][tooling ecosystem].

The implementers may hit challenges that were not foreseen by the Committee.
Early users may also provide feedback based on practical experience with the
Experimental feature. This feedback can be sent back to the Committee by
Expand All @@ -227,12 +233,12 @@ case, the SIP Author and Reviewers will work together with the implementers to
address the feedback. This is again an iterative process. Reviewers may merge
changes to the proposal at their discretion during this phase.

Once the implementation is deemed stable, including appropriate tests, the
implementers and reviewers can schedule the SIP to the next Committee meeting
for final approval. Once again, a SIP needs to gather strictly more than 50%
"Accept" votes to be Completed. If that is not achieved, it may likewise be sent
back for refinements, or be rejected, with the same rules as in the "Design
Stage -- Vote" section.
Once the implementation is deemed stable, including appropriate tests and
sufficient support by the tooling ecosystem, the implementers and reviewers can
schedule the SIP to the next Committee meeting for final approval. Once again, a
SIP needs to gather strictly more than 50% "Accept" votes to be Completed. If
that is not achieved, it may likewise be sent back for refinements, or be
rejected, with the same rules as in the "Design Stage -- Vote" section.

### Completed Stage

Expand Down Expand Up @@ -321,3 +327,5 @@ exceptions to the process, or to refine the process.
## How do I submit?

Follow the [submission tutorial]({% link _sips/sip-tutorial.md %}).

[tooling ecosystem]: https://github.com/scala/improvement-proposals/blob/main/tooling-ecosystem.md