When you should use a JEP#

• When your change requires a design doc. We prefer collecting the designs asJEPs for better discoverability and further reference.

• When your change requires extensive discussion. It’s fine to have relativelyshort discussions on issues or pull requests, but when the discussion getslonger this becomes unpractical for later digestion. JEPs allow to update themain document with a summary of the discussion and these updates can bediscussed themselves in the pull request adding the JEP.

How to start a JEP#

First, create an issue with theJEP label. All pull requests that relate tothe JEP (i.e. adding the JEP itself as well as any implementing pull requests)should be linked to this issue.

Then create a pull request that adds a file named%d-{short-title}.md - with the number being the issue number.

Several early JEPs were converted in hindsight from other documentation,issues, and pull requests, so they might not exactly reflect the processoutlined above.