5 1. Project PTL: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
7 - Yes, I have reviewed the PTL Requirements [1]_.
9 2. Project Contact: Abhijit Kumbhare, abhijitkoss@gmail.com, abhijitkumbhare
11 3. Test Contact: Luis Gomez, ecelgp@gmail.com, LuisGomez
13 4. Documentation Contact: Shuva Jyoti Kar, shuva.jyoti.kar.87@gmail.com, shuva
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
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/OpenDaylight_OpenFlow_Plugin:Oxygen_Release_Plan>`_
27 9. Do you have all APIs intended to be externally consumable listed? Yes
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 **FOR NEW PROJECTS ONLY**
46 A. Project Main Page: (wiki link)
48 - Use Project Facts Template [5]_
50 B. Have you completed the project checklist [6]_? (Yes/No)
52 - (link to a merged patch in gerrit)
53 - (link to a mail from your mailing list)
54 - (link to a bug for your project; you can create a dummy one and close it if need be)
55 - (link to an artifact published from your project in nexus)
56 - (link to a sonar report)
57 - (link to your root pom file)
59 .. [1] Be sure to read the responsibilities of being a project lead under
60 Leadership & Communication in the Requirements for Participation section
62 https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan#Requirements_for_Participation
63 .. [2] Special needs include tools or configuration. Note that generally, the
64 only available tools in CI are basic RHEL/CentOS linux images with Java.
65 You should note and ask for anything beyond that here. Email
66 helpdesk@opendaylight.org
67 .. [3] It is recommended to use the OpenDaylight CI infrastructure unless there
68 is some HW or SW resource that cannot be installed there. Update the
69 test plan with explanation on why your top-level features will not be
70 using the OpenDaylight CI Infrastructure:
71 https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
72 .. [4] Projects running system test in external Labs are required to report
73 system test results in a timely fashion after release creations, e.g.,
74 weekly, RC, and formal releases. Update the test plan with plans on
75 testing in external lab:
76 https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
77 .. [5] https://wiki.opendaylight.org/view/Template:Project_Facts
78 .. [6] https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist