Conversation
|
Thanks for the continuing work on Sorry for the delay in responding here. ECS has entered the feature freeze for the 1.10 release, and the For this PR, we'll need to ensure there are no open questions or unaddressed concerns and that the field definitions are complete based on the info and experience with have with them. I'll add some criteria in the description to help us track what's outstanding. |
exekias
left a comment
There was a problem hiding this comment.
Thank you for your contribution @ferozsalam!
ebeahan
left a comment
There was a problem hiding this comment.
LGTM!
Thanks all for iterating and moving those forward! 🎉
I'll set the advancement date and merge. You'll see a separate PR implementing the changes in the schema shortly.
* master: Stage 2 changes for RFC 0018 - extending the `threat.*` field set (elastic#1438) Remove deprecated `host.user.*` fields (elastic#1439) Explicitly include user identifiers in `related.user` field description (elastic#1420) Set the merge date on RFC 0018 stage 2 (elastic#1429) [RFC] Extend Threat Fieldset - Stage 2 Proposal (elastic#1395) [Tooling] Add --exclude flag to Generator to support field removal testing (elastic#1411) Add `host.user.*` deprecation notice in field reuse description (elastic#1422) Stage 2 changes for RFC 0015 - `elf` header (elastic#1410) Stage 3 changes for RFC 0012 - `orchestrator` field set (elastic#1417) Support `match_only_text` in Go code generator (elastic#1418) Stage 3 Orchestrator RFC (elastic#1343) moving into folder (elastic#1416) removing use-cases (elastic#1405) removing --oss (elastic#1404) Set the merge date on RFC 0015 stage 2 (elastic#1409) Consolidate `Breaking changes` sections in `CHANGELOG.next` (elastic#1408) RFC-Stage-0: Proposal to add a "ticket" schema / field definition to ECS (elastic#1383) [RFC] `match_only_text` type migration - Stage 0 (elastic#1396) Client port is wrongly documented (elastic#1402) (elastic#1406)
RFC document preview
Criteria: