Skip to content

Commit 66539b9

Browse files
authored
Make feature name required for Experimental (#3859)
We have discussed this in community meetings and Slack, and have informally agreed that a conformance Feature Name must be set for a GEP to graduate to Experimental. This commit adds changes to the GEP process page and the GEP template to make this official. Signed-off-by: Nick Young <[email protected]>
1 parent ed2bd6b commit 66539b9

File tree

2 files changed

+4
-0
lines changed

2 files changed

+4
-0
lines changed

geps/gep-696/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,8 @@ Every feature should:
4747
3. Not exceed 128 characters.
4848
4. Contain only letters and numbers
4949

50+
GEPs cannot move to Experimental without a Feature Name.
51+
5052
### Conformance tests
5153

5254
Conformance tests file names should try to follow the `pascal-case-name.go` format.

geps/overview.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,6 +151,8 @@ use the `experimental` Golang build tag to denote experimental functionality.
151151
Some other requirements must be met before marking a GEP `Experimental`:
152152

153153
- the graduation criteria to reach `Standard` MUST be filled out
154+
- the GEP must have at least one Feature Name for features described inside that
155+
will need to be tested by conformance tests.
154156
- a proposed probationary period (see next section) must be included in the GEP
155157
and approved by maintainers.
156158

0 commit comments

Comments
 (0)