Skip to content

Commit ffdd2c3

Browse files
committed
update process to include feature ADR
1 parent 3967de6 commit ffdd2c3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

PROCESS.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -122,11 +122,9 @@ At least two (2) Core Team members must have implemented prototypes before the c
122122

123123
Once a rough consensus for the idea has been reached, a formal proposal will be written, separate from the specification, with the goal of precisely defining specification changes.
124124

125-
The proposal will use the [Proposal Template]() and be stored in this repository's `proposals` folder.
125+
The proposal will use the [Proposal Template](./proposals/proposal-template.md) and be stored in this repository's `proposals` folder.
126126

127-
```diff
128-
@@ TODO: Define Proposal Template and fill in the link. @@
129-
```
127+
Additionally, a draft ADR will be included using the file name of the proposal document with an `-adr` suffix: `{proposal-file-name}-adr.md`. This ADR will include additional information from the "Concept" discussion.
130128

131129
Proposed keywords will be added to the appropriate vocabulary meta-schemas in:
132130

@@ -169,7 +167,9 @@ If a proposal cannot advance to the next stage, it may be removed. The proposal
169167

170168
### Stable
171169

172-
The proposal is incorporated into the specification in the `main` branch, and the feature will be required as of the next release.
170+
The feature is incorporated into the specification in the `main` branch as specified by the proposal document, and the feature will be required as of the next release.
171+
172+
The draft ADR is completed, dated, and moved to the `adr` folder.
173173

174174
The appropriate vocabulary meta-schema in the `main` branch is updated to include a subschema that validates the feature's syntax requirements. This will be made available with the next release.
175175

0 commit comments

Comments
 (0)