Re: [openflowplugin-dev] OpenFlow Plugin M2 Status
Small correction - in-line. On Thu, Dec 1, 2016 at 11:11 PM, Abhijit Kumbhare 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
[openflowplugin-dev] OpenFlow Plugin M2 Status
*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 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
[openflowplugin-dev] OpenFlow Plugin M2 status
1.Have you completed the project checklist [1]? Yes (this is actually applicable to new projects only - this was already done in the previous releases - copying from Beryllium) * (link to a merged patch in gerrit) : https://git.opendaylight.org/gerrit/#/c/25298/ * (link to a mail from your mailing list) : https://lists.opendaylight.org/pipermail/openflowplugin-dev/2015-August/003750.html * (link to a bug for your project; you can create a dummy one and close it if need be) : https://bugs.opendaylight.org/show_bug.cgi?id=4123 * (link to an artifact published from your project in nexus) : https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/openflowplugin/openflowplugin/0.2.0-SNAPSHOT/ * (link to a sonar report) : https://sonar.opendaylight.org/dashboard/index/12170 * (link to your root pom file) : https://git.opendaylight.org/gerrit/gitweb?p=openflowplugin.git;a=blob;f=pom.xml 2.Does your project have any special needs in CI Infrastructure [2]? No 3.Is your project release plan finalized? Yes * https://wiki.opendaylight.org/view/OpenDaylight_OpenFlow_Plugin:Boron_Release_Plan (link to final release plan wiki page) * Do you have all APIs intended to be externally consumable listed? Yes - no API changes are planned. However it is possible there may be modifications (additions/deletions/changes). * Does each API have a useful short name? Yes * Are the Java interface and/or YANG files listed for each API? No, externally consumable APIs are sets of (50+) java interfaces * Are they labeled as tentative, provisional, or stable as appropriate for each API? Yes * Do you call out the OSGi bundles and/or Karaf features providing the API for each API? Yes 4.All project dependencies requests on other project's release plans been acknowledged and documented by upstream projects? Yes 5.Were there any project-specific deliverables planned for this milestone? Yes * If so, were they delivered? Yes Integration and Test: 6.Will your project have top-level features not requiring system test? No 7.Will your project use the OpenDaylight CI infrastructure for testing top-level features requiring system test? No ___ openflowplugin-dev mailing list openflowplugin-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
