5 1. Project PTL: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
7 - I have reviewed the PTL Requirements
9 2. Project Contact: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
11 3. Test Contact: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
13 4. Documentation Contact: Anton Ivanov, anton.ivanov@cambridgegreys.com, kot-begemot
15 5. Does your project have any updates on any previously-incomplete items from
16 prior milestone readouts? No
18 6. Were project-specific deliverables planned for this milestone delivered
21 7. Does your project have any special needs in CI Infrastructure [2]_? No
23 8. Is your project release plan finalized? Yes
25 - https://wiki.opendaylight.org/view/JsonRPC2.0:Oxygen:Release_Plan
27 9. Do you have all APIs intended to be externally consumable listed? Not Applicable
29 10. Have all project dependencies requests on other projects' release plans
30 been acknowledged and documented by upstream projects? Yes
32 - Offset 0 projects: MDSAL, yangtools, controller
34 11. Will your project have top-level features not requiring system test? No
36 12. Will your project use the OpenDaylight CI infrastructure for testing
37 top-level features requiring system test? Yes
39 **FOR NEW PROJECTS ONLY**
41 Not Applicable - while this is first release, project has been part of ODL
44 .. [1] Be sure to read the responsibilities of being a project lead under
45 Leadership & Communication in the Requirements for Participation section
47 https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
48 .. [2] Special needs include tools or configuration. Note that generally, the
49 only available tools in CI are basic RHEL/CentOS linux images with Java.
50 You should note and ask for anything beyond that here. Email
51 helpdesk@opendaylight.org
52 .. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
53 is some HW or SW resource that cannot be installed there. Update the
54 test plan with explanation on why your top-level features will not be
55 using the OpenDaylight CI Infrastructure:
56 https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
57 .. [4] Projects running system test in external Labs are required to report
58 system test results in a timely fashion after release creations, e.g.,
59 weekly, RC, and formal releases. Update the test plan with plans on
60 testing in external lab:
61 https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
62 .. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
63 .. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist