docs: Add work items to the release freeze process
This adds a reminder to the security working group to check security aspects
of the release, the test work group to test, and the community to update the
release notes.
Signed-off-by: Joseph Reynolds <joseph.reynolds1@ibm.com>
Change-Id: Iea855a6c737f90ff231c4f8d122f9b5b6b841908
diff --git a/release/release-process.md b/release/release-process.md
index c0b2965..57313d4 100644
--- a/release/release-process.md
+++ b/release/release-process.md
@@ -60,6 +60,19 @@
How the release freeze will be done with regard to freeze and branch
immediately or to freeze and test, branching on the release date is still TBD.
+The [security working group][] should provide guidance to the
+community about security aspects of the planned release. The idea is
+to provide input for the [release notes][] and actionable advice to the
+[test work group][].
+
+The [test work group][] should indicate what testing was performed and
+the results of that testing. The idea is to fix problems and provide
+input to the [release notes][].
+
+[security working group]: https://github.com/openbmc/openbmc/wiki/Security-working-group
+[test work group]: https://github.com/openbmc/openbmc/wiki/Test-work-group
+[release notes]: https://github.com/openbmc/docs/blob/master/release/release-notes.md
+
#### Release
The release milestone is the release date. It is defined as happening some
time within a targeted release week. It is desired to have the release happen
@@ -72,6 +85,8 @@
have to be included in the next release cycle. The release date will not float
out until the feature is complete.
+The updated [release notes][] should be merged into the project.
+
## Release Content
### Content Input