ODL Parent Oxygen M1 read-out

Change-Id: I6af301fbbee37195c8f78806f1e3ef820706b49f
Signed-off-by: Stephen Kitt <skitt@redhat.com>

diff --git a/docs/release-process/milestone-readouts/m1/odlparent.rst b/docs/release-process/milestone-readouts/m1/odlparent.rst
new file mode 100644 (file)
index 0000000..84edda9
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m1/odlparent.rst
@@ -0,0 +1,69 @@
+==========
+ODL Parent
+==========
+
+1. Project PTL:
+
+   - Stephen Kitt
+   - skitt@redhat.com
+   - skitt
+   - I have reviewed the PTL Requirements
+
+2. Project Contact:
+
+   - Stephen Kitt
+   - skitt@redhat.com
+   - skitt
+
+3. Test Contact:
+
+   - Stephen Kitt
+   - skitt@redhat.com
+   - skitt
+
+4. Documentation Contact
+
+   - Stephen Kitt
+   - skitt@redhat.com
+   - skitt
+
+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
+
+7. Does your project have any special needs in CI Infrastructure?
+
+   - No
+
+8. Is your project release plan finalized?
+
+   - Yes: https://wiki.opendaylight.org/view/ODL_Parent:Oxygen_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? N/A
+   - Are they labeled as tentative, provisional, or stable as appropriate for
+     each API? They will be by M2
+   - 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?  N/A
+
+    - No project dependencies
+
+11. Will your project have top-level features not requiring system test?
+
+    - Yes, ODL parent usually gets an automatic waiver
+
+12. Will your project use the OpenDaylight CI infrastructure for testing
+    top-level features requiring system test?
+
+    - No, see above