Small correction - in-line.

On Thu, Dec 1, 2016 at 11:11 PM, Abhijit Kumbhare <abhijitk...@gmail.com>
wrote:

> *OpenFlow Plugin*
>
> 1. Does your project have any updates on any previously-incomplete items
> from prior milestone readouts?  (Yes/No)
>   No
> 2. Were project-specific deliverables planned for this milestone delivered
> successfully? (No Deliverables/Yes/No)
>    Yes
> 3. Does your project have any special needs in CI Infrastructure [2]?
> (Yes/No)
>    No
> 4. Is your project release plan finalized?  (Yes/No)
>    Yes
>  https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Carbon_
> Release_Plan
>
> 5. Do you have all APIs intended to be externally consumable listed?
> (Yes/No)
>   Yes - no API changes are planned for previous features. However it is
> possible there may be modifications (additions/deletions/changes). There
> may be additional APIs for bundles feature
>
>    Does each API have a useful short name? (Yes/No)
>  Yes
>
>    Are the Java interface and/or YANG files listed for each API? (Yes/No)
> No, externally consumable APIs are sets of (50+) java interfaces
>
>    Are they labeled as tentative, provisional, or stable as appropriate
> for each API? (Yes/No)
> No labeling has been done on the OpenFlow Plugin API - no existing
> external API are planned to be changed.
>
>    Do you call out the OSGi bundles and/or Karaf features providing the
> API for each API? (Yes/No)
> Yes (There is a Karaf feature - odl-openflowplugin-flow-services which
> provides all the API. Individual API do not have a separate Karaf feature.)
>
> 6. Have all project dependencies requests on other project's release plans
> been acknowledged and documented by upstream projects?  (Yes/No)
>   Yes - in process (OpenFlow Java, MD-SAL & controller - these are the
> projects on which OpenFlow Plugin is directly dependent on in some way)
>
> 7. Will your project have top-level features not requiring system test?
> (Yes/No)
>    No
>
> 8. Will your project use the OpenDaylight CI infrastructure for testing
> top-level features requiring system test? (Yes/No)
>    Yes
>
>
> [0] https://wiki.opendaylight.org/view/Simultaneous_Release:
> Carbon_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
> helpd...@opendaylight.org
> [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
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev

Reply via email to