Update CVE releated issues with CVE number (#6949)

It can be hard to find issues associated with CVEs after the fact.  We should update the issue description to include the CVE number once published.
This commit is contained in:
Greg Wilkins 2021-10-18 07:27:54 +11:00 committed by GitHub
parent 2426b34a51
commit 80ddc3ba2d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 0 deletions

View File

@ -53,6 +53,7 @@ This release process will produce releases:
- [ ] Prepare release announcement for mailing lists. - [ ] Prepare release announcement for mailing lists.
- [ ] Publish any [security advisories](https://github.com/eclipse/jetty.project/security/advisories). - [ ] Publish any [security advisories](https://github.com/eclipse/jetty.project/security/advisories).
+ [ ] Edit `VERSION.txt` to include any actual CVE number next to correspondent issue. + [ ] Edit `VERSION.txt` to include any actual CVE number next to correspondent issue.
+ [ ] Edit any issues for CVEs in github with their CVE number
- [ ] Notify downstream maintainers. - [ ] Notify downstream maintainers.
+ [ ] Eclipse p2 maintainer. + [ ] Eclipse p2 maintainer.
+ [ ] Docker maintainer. + [ ] Docker maintainer.