JSON-RPC2.0 M1 Filled Template for Oxygen

JSON-RPC2.0 M1 information

Change-Id: I09c919036c088d2963cb5686ea682d250ae99d48
Signed-off-by: Anton Ivanov <anton.ivanov@cambridgegreys.com>

diff --git a/docs/release-process/milestone-readouts/m1/jsonrpc.rst b/docs/release-process/milestone-readouts/m1/jsonrpc.rst
new file mode 100644 (file)
index 0000000..6db4cb0
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m1/jsonrpc.rst
@@ -0,0 +1,91 @@
+============
+JSON-RPC2.0
+============
+
+1. Project PTL:
+
+   - Anton Ivanov
+   - anton.ivanov@cambridgegreys.com
+   - kot-begemot
+   - I have reviewed the PTL Requirements
+
+2. Project Contact:
+
+   - Anton Ivanov
+   - anton.ivanov@cambridgegreys.com
+   - kot-begemot
+
+3. Test Contact:
+
+   - Anton Ivanov
+   - anton.ivanov@cambridgegreys.com
+   - kot-begemot
+
+4. Documentation Contact
+
+   - Anton Ivanov
+   - anton.ivanov@cambridgegreys.com
+   - kot-begemot
+
+5. Does your project have any updates on any previously-incomplete items from
+   prior milestone readouts? (Yes/No)
+
+   - No
+
+6. Were project-specific deliverables planned for this milestone delivered
+   successfully? (No Deliverables/Yes/No)
+
+   - Yes
+
+7. Does your project have any special needs in CI Infrastructure [2]_? (Yes/No)
+
+   - No
+
+8. Is your project release plan finalized?  (Yes/No)
+
+   - Yes: https://wiki.opendaylight.org/view/JsonRPC2.0:Oxygen:Release_Plan
+
+9. Do you have all APIs intended to be externally consumable listed? (Yes/No/Not Applicable)
+
+   - Not Applicable
+
+10. Have all project dependencies requests on other projects' release plans
+    been acknowledged and documented by upstream projects? Yes
+
+    - Offset 0 projects - MDSAL, yangtools, controller
+
+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
+
+**FOR NEW PROJECTS ONLY**
+
+Not Applicable - while this is first release, project has been part of ODL
+since Boron.
+
+.. [1] Be sure to read the responsibilities of being a project lead under
+       Leadership & Communication in the Requirements for Participation section
+       of the release plan:
+       https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
+.. [2] Special needs include tools or configuration.  Note that generally, the
+       only available tools in CI are basic RHEL/CentOS linux images with Java.
+       You should note and ask for anything beyond that here.  Email
+       helpdesk@opendaylight.org
+.. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
+       is some HW or SW resource that cannot be installed there.  Update the
+       test plan with explanation on why your top-level features will not be
+       using the OpenDaylight CI Infrastructure:
+       https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
+.. [4] Projects running system test in external Labs are required to report
+       system test results in a timely fashion after release creations, e.g.,
+       weekly, RC, and formal releases.  Update the test plan with plans on
+       testing in external lab:
+       https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
+.. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
+.. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist