doc: clarify security pre-release end of embargo date
authorFerruh Yigit <ferruh.yigit@intel.com>
Mon, 17 Jun 2019 16:06:47 +0000 (17:06 +0100)
committerThomas Monjalon <thomas@monjalon.net>
Sun, 24 May 2020 23:04:36 +0000 (01:04 +0200)
commit4f0416968bb7d559facfc7b743788c00ee8c7981
treef024eccd8597694f05b036fc3b59bd852da88718
parentd7e66b69ddc947a1263e8d489483a5bd7c7aa6b5
doc: clarify security pre-release end of embargo date

Clarify that a fixed date will be used for end of embargo (public
disclosure) date while communicating with downstream stakeholders.

Initial document got a review that it gives an impression that
communicated embargo date can be a range like 'less than a week' which
is not the case. The range applies when defining the end of the embargo
date but a fix date will be communicated.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
Acked-by: John McNamara <john.mcnamara@intel.com>
doc/guides/contributing/vulnerability.rst