23 4. Documentation Contact
29 5. Does your project have any updates on any previously-incomplete items from
30 prior milestone readouts? (Yes/No)
34 6. Were project-specific deliverables planned for this milestone delivered
35 successfully? (No Deliverables/Yes/No)
39 7. Does your project have any special needs in CI Infrastructure? (Yes/No)
41 - Yes, we need NSH (Network Service Header) support in OVS (OpenVSwitch) for some test cases. see `Bug-8488 <https://bugs.opendaylight.org/show_bug.cgi?id=8488>`_
43 8. Is your project release plan finalized? (Yes/No)
45 - Yes, available here: `Release plan <https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Oxygen/Release_plan>`_
47 9. Do you have all APIs intended to be externally consumable listed? (Yes/No/Not Applicable)
49 - Does each API have a useful short name? Yes
50 - Are the Java interface and/or YANG files listed for each API? Yes
51 - Are they labeled as tentative, provisional, or stable as appropriate for
53 - Do you call out the OSGi bundles and/or Karaf features providing the API
56 10. Have all project dependencies requests on other projects' release plans
57 been acknowledged and documented by upstream projects? (Yes/No)
59 - Dependencies: aaa,controller,dlux,faas,honeycomb/vbd,lispflowmapping,mdsal,netconf,neutron,odlparent,openflowplugin,ovsdb,sfc,sxp
60 - Yes. The dependent projects have been acknowledged in previous releases.
62 11. Will your project have top-level features not requiring system test?
66 12. Will your project use the OpenDaylight CI infrastructure for testing
67 top-level features requiring system test? (Yes/No)
70 - There are tests for top level features that are provided via
71 `OPNFV (Open Platform for Network Functions Virtualization) pipeline. <http://testresults.opnfv.org/>`_
72 Documentation for testing via OPNFV is available here: `FDS (FastDataStacks) Testing Euphrates <https://wiki.opnfv.org/display/fds/FDS+Testing+Euphrates>`_