add project p4plugin m4-readouts

Change-Id: Ic6ea6cc45d4d33081567d9d153b09590e4575643
Signed-off-by: Wsx25289 <10200860@zte.com.cn>

diff --git a/docs/release-process/milestone-readouts/m4/p4plugin.rst b/docs/release-process/milestone-readouts/m4/p4plugin.rst
new file mode 100644 (file)
index 0000000..8225e71
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m4/p4plugin.rst
@@ -0,0 +1,42 @@
+=========
+P4 Plugin
+=========
+
+1. Do you have any previously-incomplete items from prior milestone
+   readouts? Yes, we are busy with automated system test now.
+
+2. Has your project met code freeze [1]_? Yes
+
+3. Are all externally visible strings frozen to allow for translation &
+   documentation? Yes
+
+4. Is your documentation complete [2]_? Yes
+
+5. Were project-specific deliverables planned for this milestone delivered
+   successfully? No Deliverables
+
+6. Are you running at least one basic automated system test job for each
+   top-level feature? Yes
+
+   - https://jenkins.opendaylight.org/releng/view/p4plugin/job/p4plugin-csit-1node-basic-all-oxygen/
+
+7. Do you have any CLM violations? No
+
+**Stable Features (Only for Projects with Stable Features)**
+
+A. Do your stable features fulfill quality requirements [3]_? (Yes/No)
+
+   - (If yes, link to sonar report)
+   - (If not, explain why)
+
+B. Are you running several automated system test jobs [4]_ for each stable
+   feature? (Yes/No)
+
+   - (If yes, link to test reports)
+   - (If not, explain why)
+
+.. [1] Only bug fixes are allowed from now on
+.. [2] Only editing and enhancing should take place from now on
+.. [3] Unit and/or integration test coverage of at least 75%
+.. [4] These test jobs include functionality, cluster, scalability, performance,
+       longevity/stability