5 1. Project PTL: Hideyuki Tai, h-tai@cd.jp.nec.com, hideyuki
7 - Yes, I have reviewed the PTL Requirements [1]_.
9 2. Project Contact: Venkatrangan Govindarajan, venkatrangang@hcl.com, gvrangan
11 3. Test Contact: Venkatrangan Govindarajan, venkatrangang@hcl.com, gvrangan
13 4. Documentation Contact: Venkatrangan Govindarajan, venkatrangang@hcl.com, gvrangan
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
19 successfully? No Deliverables
21 7. Does your project have any special needs in CI Infrastructure [2]_? No
23 8. Is your project release plan finalized? Yes
25 - `Release plan <https://wiki.opendaylight.org/view/VTN:Oxygen_Release_Plan>`_
27 9. Do you have all APIs intended to be externally consumable listed?
29 - Does each API have a useful short name? - *Yes*
30 - Are the Java interface and/or YANG files listed for each API? - *Yes*
31 - Are they labeled as tentative, provisional, or stable as appropriate for
33 - Do you call out the OSGi bundles and/or Karaf features providing the API
36 10. Have all project dependencies requests on other projects' release plans
37 been acknowledged and documented by upstream projects? Yes
39 11. Will your project have top-level features not requiring system test? No
41 12. Will your project use the OpenDaylight CI infrastructure for testing
42 top-level features requiring system test? Yes
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