Lines Matching refs:will
10 vulnerabilities@zephyrproject.org mailing list. These reports will be
12 Each vulnerability will be entered into the Zephyr Project security
13 advisory GitHub_. The original submitter will be granted permission to
21 Issues within this bug tracking system will transition through a
58 response team will analyze the issue, determine a responsible
60 issue to the Assigned state. Part of triage will be to set the
67 link will be added to a comment in the issue, and the issue moved to
73 - Public: The embargo period has ended. The issue will be made
87 Subcommittee. In the general case, this will include:
99 The guideline for embargo will be based on: 1. Severity of the issue,
101 decides do not need an embargo will be reproduced in the regular
120 The security subcommittee will maintain information mapping embargoed
142 This list will be seeded initially with a contact from each project
144 out the form at the `Vulnerability Registry`_. These parties will be
151 Periodically, the security subcommittee will send information to this
157 When issues have been triaged, this list will be informed of:
168 above, the list will be informed of:
194 Backports will be tracked on the security advisory.
201 a need to know. The following parties will need to know details about
204 - Maintainers will have access to all information within their domain
210 - The Project Security Incident Response (PSIRT) team will have full