5 1. Project PTL: Donald Hunter, donaldh@cisco.com, donaldh
7 - Yes, I have reviewed the PTL Requirements [1]_.
9 2. Project Contact: Donald Hunter, donaldh@cisco.com, donaldh
11 3. Test Contact: Bartosz Michalik, bartosz.michalik@amartus.com
13 4. Documentation Contact: Charles Eckel, eckelcu@cisco.com
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? No
25 9. Do you have all APIs intended to be externally consumable listed?
27 - Does each API have a useful short name? *Yes*
28 - Are the Java interface and/or YANG files listed for each API? *Yes*
29 - Are they labeled as tentative, provisional, or stable as appropriate for
31 - Do you call out the OSGi bundles and/or Karaf features providing the API
34 10. Have all project dependencies requests on other projects' release plans
35 been acknowledged and documented by upstream projects?
37 - dlux, not acknowledged
38 - genius, not acknowledged
39 - l2switch, not acknowledged
40 - netvirt, not acknowledged
41 - ovsdb, not acknowledged
42 - vpnservice, not acknowledged
44 11. Will your project have top-level features not requiring system test? No
46 12. Will your project use the OpenDaylight CI infrastructure for testing
47 top-level features requiring system test? Yes
50 .. [1] Be sure to read the responsibilities of being a project lead under
51 Leadership & Communication in the Requirements for Participation section
53 https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
54 .. [2] Special needs include tools or configuration. Note that generally, the
55 only available tools in CI are basic RHEL/CentOS linux images with Java.
56 You should note and ask for anything beyond that here. Email
57 helpdesk@opendaylight.org