Project Name: OpenFlow Plugin

1. Does your project have any updates on any previously-incomplete items
from prior milestone readouts?
   No

2. Were project-specific deliverables planned for this milestone delivered
successfully?
   Yes

3. Does your project have any special needs in CI Infrastructure [2]?
   No

4. Is your project release plan finalized?
   Yes - (subject to reasonable changes).
   Link to final release plan wiki page:
https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Oxygen_Release_Plan


5. Do you have all APIs intended to be externally consumable listed? Yes -
no change.
   Does each API have a useful short name? Yes - no change
   Are the Java interface and/or YANG files listed for each API?  Yes - no
change
   Are they labeled as tentative, provisional, or stable as appropriate for
each API?   Yes - no change
   Do you call out the OSGi bundles and/or Karaf features providing the API
for each API?   Yes - no change

6. Have all project dependencies requests on other project's release plans
been acknowledged and documented by upstream projects?
   Depends on some offset 0 projects like ODL parent, controller, MD-SAL,
etc. These have been acknowledged previous releases - no new dependencies &
hence do not need to be acknowledged.

7. Will your project have top-level features not requiring system test?
   No

8. Will your project use the OpenDaylight CI infrastructure for testing
top-level features requiring system test?
   Yes

** FOR NEW PROJECTS ONLY **
9. Have you completed the project checklist [1]? (Yes/No)
   (link to a merged patch in gerrit)
   (link to a mail from your mailing list)
   (link to a bug for your project; you can create a dummy one and close it
if need be)
   (link to an artifact published from your project in nexus)
   (link to a sonar report)
   (link to your root pom file)

[0]
https://wiki.opendaylight.org/view/Simultaneous_Release:Oxygen_Release_Plan
[1]
https://wiki.opendaylight.org/view/GettingStarted:Project_Main#New_Project_Checklist
[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
[email protected]
[3] It is recommended to use the OpenDaylight CI infrastructure unless
there is some HW or SW resource that cannot be installed there.  Update the
test plan with explanation on why your top-level features will not be using
the OpenDaylight CI Infrastructure:
https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
[4] Projects running system test in external Labs are required to report
system test results in a timely fashion after release creations, e.g.,
weekly, RC, and formal releases.  Update the test plan with plans on
testing in external lab:
https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template#Test_Infrastructure
_______________________________________________
openflowplugin-dev mailing list
[email protected]
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to