1 ========================
2 Integration/Distribution
3 ========================
8 - email: vrpolak@cisco.com
10 - I have reviewed the PTL Requirements [1]_: True.
15 - email: ecelgp@gmail.com
16 - IRC handle: LuisGomez
21 - email: vrpolak@cisco.com
24 4. Documentation Contact
27 - email: ecelgp@gmail.com
28 - IRC handle: LuisGomez
30 5. Does your project have any updates on any previously-incomplete items from
31 prior milestone readouts?
35 6. Were project-specific deliverables planned for this milestone delivered
40 7. Does your project have any special needs in CI Infrastructure [2]_?
44 8. Is your project release plan finalized?
48 9. Do you have all APIs intended to be externally consumable listed? (Yes/No/Not Applicable)
52 - Does each API have a useful short name?
56 - Are the Java interface and/or YANG files listed for each API?
60 - Are they labeled as tentative, provisional, or stable as appropriate for
65 - Do you call out the OSGi bundles and/or Karaf features providing the API
70 10. Have all project dependencies requests on other projects' release plans
71 been acknowledged and documented by upstream projects?
73 Zero requests, so yes.
75 11. Will your project have top-level features not requiring system test?
77 Yes, legacy experimental scripts.
80 12. Will your project use the OpenDaylight CI infrastructure for testing
81 top-level features requiring system test?
85 .. [1] Be sure to read the responsibilities of being a project lead under
86 Leadership & Communication in the Requirements for Participation section
88 https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
89 .. [2] Special needs include tools or configuration. Note that generally, the
90 only available tools in CI are basic RHEL/CentOS linux images with Java.
91 You should note and ask for anything beyond that here. Email
92 helpdesk@opendaylight.org
93 .. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
94 is some HW or SW resource that cannot be installed there. Update the
95 test plan with explanation on why your top-level features will not be
96 using the OpenDaylight CI Infrastructure:
97 https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
98 .. [4] Projects running system test in external Labs are required to report
99 system test results in a timely fashion after release creations, e.g.,
100 weekly, RC, and formal releases. Update the test plan with plans on
101 testing in external lab:
102 https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
103 .. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
104 .. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
105 .. [7] https://wiki.opendaylight.org/view/Integration/Distribution/Oxygen_Release_Plan