Lines Matching full:issue

18 Security Issue Management
54   response to an email, the issue shall be transitioned directly to
57 - Triage: This issue is awaiting Triage by the response team.  The
58   response team will analyze the issue, determine a responsible
60   issue to the Assigned state.  Part of triage will be to set the
61   issue's priority.
63 - Assigned: The issue has been assigned, and is awaiting a fix by the
66 - Review: Once there is a Zephyr pull request for the issue, the PR
67   link will be added to a comment in the issue, and the issue moved to
70 - Accepted: Indicates that this issue has been merged into the
73 - Public: The embargo period has ended.  The issue will be made
99 The guideline for embargo will be based on: 1. Severity of the issue,
100 and 2. Exploitability of the issue.  Issues that the subcommittee
117 numbers that have been assigned to the issue.  The developer instead
125 Each issue that is considered a security vulnerability shall be
165 - The severity of the issue.
167 After acceptance of a PR fixing the issue (merged), in addition to the
177 Each security issue fixed within zephyr shall be backported to the
191 release manager that the backport pull request and issue are addressing