These are the stages that an individual RFC advances through before being released for general availability in the Elastic Common Schema (ECS). See the Contributing Guide for broader details about contributing changes to ECS through the RFC process.
Stage | Goals during this stage | Criteria for consideration for this stage | Acceptance into this stage signifies | Acceptable changes to schema in this stage | Breaking changes expected after acceptance into this stage | Recommended types of usage implementation | |
---|---|---|---|---|---|---|---|
0 | Strawperson |
|
Opened RFC pull request for this strawperson at elastic/ecs | The premise of these changes is not obviously useless or inappropriate for ECS | None | Major | N/A |
1 | Draft |
|
|
ECS team accepts the premise of the addition and commits to considering this proposal as it advances. | Draft field definitions can be committed to the ECS schema as "experimental" fields | Major | Proof of concepts, demos |
2 | Candidate | Identify a comprehensive set of field definitions that could be appropriate for real-world usage |
|
The initial field definitions comprehensively model the addition to the schema. Fundamental questions and concerns are resolved, though some less significant questions remain open. | Candidate field definitions can be committed to the ECS schema as "beta" fields | Iterative | Experimental features |
3 | Finished | Indicate that the addition is ready for GA release in ECS |
|
There are no further open questions or unaddressed concerns, and the field definitions are complete based on the information and usage experience we have. | Field definitions can be committed to the ECS schema as "GA" fields | None outside major versions | Any |
X | Abandoned | The changes are no longer being actively pursued. |
|
The proposal will no longer advance. | Any candidate field definitions will be removed from the ECS schema. | N/A | N/A |