Skip to content

Commit

Permalink
proposals: release approval process explain security@ email
Browse files Browse the repository at this point in the history
Expand a bit more information about the security@ alias and who is
involved in a security sensitive release.
  • Loading branch information
Brandon Philips committed Jun 29, 2016
1 parent be10456 commit 86b3087
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion GOVERNANCE.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ OCI projects need a standard process for making releases so the community of mai

## Security fixes

Security fix releases MUST use [email protected] instead of [email protected], but should otherwise follow the standard [list-based voting process](#list-based-voting).
Security fix releases MUST use [email protected] instead of [email protected], but should otherwise follow the standard [list-based voting process](#list-based-voting). The [email protected] email includes all members of the TOB; the TOB will guide the security sensitive release with project maintainers.

## Parallel proposals

Expand Down

0 comments on commit 86b3087

Please sign in to comment.