Add NEMO M1 Oxygen

Change-Id: If716755b1420b230a40b5ee69c631fe172984944
Signed-off-by: A H <an.ho@huawei.com>

diff --git a/docs/release-process/milestone-readouts/m1/nemo.rst b/docs/release-process/milestone-readouts/m1/nemo.rst
new file mode 100644 (file)
index 0000000..2a86979
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m1/nemo.rst
@@ -0,0 +1,71 @@
+====
+Nemo
+====
+
+1. Project PTL:
+
+   - A H
+   - an.ho at huawei dot com
+   - anipbu
+   - I have reviewed the PTL Requirements
+
+2. Project Contact:
+
+   - A H
+   - an.ho at huawei dot com
+   - anipbu
+
+3. Test Contact:
+
+   - A H
+   - an.ho at huawei dot com
+   - anipbu
+
+4. Documentation Contact
+
+   - A H
+   - an.ho at huawei dot com
+   - anipbu
+
+5. Does your project have any updates on any previously-incomplete items from
+   prior milestone readouts?
+
+   - No
+
+6. Were project-specific deliverables planned for this milestone delivered
+   successfully? (No Deliverables/Yes/No)
+
+   - No
+
+7. Does your project have any special needs in CI Infrastructure? (Yes/No)
+
+   - No
+
+8. Is your project release plan finalized?  (Yes/No)
+
+   - Yes
+   - https://wiki.opendaylight.org/view/NEMO:Nitrogen:Release_Plan
+
+9. Do you have all APIs intended to be externally consumable listed? Yes
+
+   - Does each API have a useful short name? Yes
+   - Are the Java interface and/or YANG files listed for each API? Yes
+   - Are they labeled as tentative, provisional, or stable as appropriate for
+     each API? Yes
+   - Do you call out the OSGi bundles and/or Karaf features providing the API
+     for each API? Yes
+
+10. Have all project dependencies requests on other projects' release plans
+    been acknowledged and documented by upstream projects?
+
+    - Yes
+
+11. Will your project have top-level features not requiring system test?
+    (Yes/No)
+
+    - No
+
+12. Will your project use the OpenDaylight CI infrastructure for testing
+    top-level features requiring system test? (Yes/No)
+
+    - Yes