====== Unimgr ====== 1. Project PTL: Donald Hunter, donaldh@cisco.com, donaldh - Yes, I have reviewed the PTL Requirements [1]_. 2. Project Contact: Donald Hunter, donaldh@cisco.com, donaldh 3. Test Contact: Bartosz Michalik, bartosz.michalik@amartus.com 4. Documentation Contact: Charles Eckel, eckelcu@cisco.com 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 [2]_? No 8. Is your project release plan finalized? No 9. Do you have all APIs intended to be externally consumable listed? - Does each API have a useful short name? *Yes* - Are the Java interface and/or YANG files listed for each API? *Yes* - Are they labeled as tentative, provisional, or stable as appropriate for each API? *Yes* - 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? - dlux, not acknowledged - genius, not acknowledged - l2switch, not acknowledged - netvirt, not acknowledged - ovsdb, not acknowledged - vpnservice, not acknowledged 11. Will your project have top-level features not requiring system test? No 12. Will your project use the OpenDaylight CI infrastructure for testing top-level features requiring system test? Yes .. [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