README, RELEASES: update security email
Signed-off-by: Stephen J Day <stephen.day@docker.com>
This commit is contained in:
		| @@ -196,7 +196,7 @@ For sync communication we have a community slack with a #containerd channel that | |||||||
|  |  | ||||||
| ### Reporting security issues | ### Reporting security issues | ||||||
|  |  | ||||||
| __If you are reporting a security issue, please reach out discreetly at containerd-security@googlegroups.com__. | __If you are reporting a security issue, please reach out discreetly at security@containerd.io__. | ||||||
|  |  | ||||||
| ## Copyright and license | ## Copyright and license | ||||||
|  |  | ||||||
|   | |||||||
| @@ -114,7 +114,7 @@ one of three ways: | |||||||
| 2. Open a PR with cherry-picked change from master. | 2. Open a PR with cherry-picked change from master. | ||||||
| 3. Open a PR with a ported fix. | 3. Open a PR with a ported fix. | ||||||
|  |  | ||||||
| __If you are reporting a security issue, please reach out discreetly at containerd-security@googlegroups.com__. | __If you are reporting a security issue, please reach out discreetly at security@containerd.io__. | ||||||
| Remember that backported PRs must follow the versioning guidelines from this document. | Remember that backported PRs must follow the versioning guidelines from this document. | ||||||
|  |  | ||||||
| Any release that is "active" can accept backports. Opening a backport PR is | Any release that is "active" can accept backports. Opening a backport PR is | ||||||
|   | |||||||
		Reference in New Issue
	
	Block a user
	 Stephen J Day
					Stephen J Day