OpenflowJava M3 status
an.ho@huawei.com
Hi OpenflowJava Team,
For M3, we are missing the Beryllium System Test Plan Wiki Page (#9) for your project. Please take a moment to create one for your project base on the template here [1] or provide an ETA for completion. In the “Feature Pro-activeness” section, remember to include any local ports (e.g. TCP port 6633 for openflow) that your feature needs to bind to.
Projects with an approved system test waiver should still fill out a Beryllium System Test Plan Wiki as discussed here [2].
Best Regards, An Ho
[1] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template [2] https://lists.opendaylight.org/pipermail/integration-dev/2015-October/004942.html
From: Michal Polkoráb [mailto:michal.polkorab@...]
Sent: Thursday, October 01, 2015 7:49 AM To: Release; An Ho Subject: OpenflowJava M3 status
Hello,
please see Openflow Protocol Library (Openflowjava) M3 status below:
Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes 2. Are all your inter-project dependencies resolved (i.e., have the other projects you were counting on given you what you needed)? Yes 3. Were there any project-specific deliverables planned for this milestone? No
Karaf Features Defined: 4. Are all your project's features that are intended for release added to the features.xml and checked into the integration git repository? Yes features.xml are pulled by openflowplugin 5. List all top-level, user-facing, and stable Karaf features for your project. No user-facing features. Top-level feature: odl-openflowjava-protocol - whole openflowjava functionality Top-level features are usually installed by user-facing features.
Documentation: 6. List the kinds of documentation you will provide including at least: - developer guide 7. Have you checked in the AsciiDoc outlines to the docs repository? No - no feature / functionality updates since Lithium
Integration and Test: 8. Have you started automated system testing for your top-level features. No - system test waiver approved
9. Have you filled out basic system test plan template for each top-level feature (karaf and not karaf) and a comprehensive system test plan template including functionality, cluster, scalability, performance, longevity/stability for each stable feature? No - system test waiver approved
Best regards, Michal Polkorab MichalPolkoráb Software Developer
|
Michal Polkorab
Hello An,
I have created System test plan for openflowjava here: https://wiki.opendaylight.org/view/Openflow_Protocol_Library:Beryllium_system_test_plan If there are more steps required, please let me know.
Regards, Michal From: An Ho <An.Ho@...>
Sent: 15 October 2015 02:06 To: Michal Polkoráb; openflowjava-dev@... Subject: RE: OpenflowJava M3 status Hi OpenflowJava Team,
For M3, we are missing the Beryllium System Test Plan Wiki Page (#9) for your project. Please take a moment to create one for your project base on the template here [1] or provide an ETA for completion. In the “Feature Pro-activeness” section, remember to include any local ports (e.g. TCP port 6633 for openflow) that your feature needs to bind to.
Projects with an approved system test waiver should still fill out a Beryllium System Test Plan Wiki as discussed here [2].
Best Regards, An Ho
[1] https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Feature_Integration_System_Test_Template [2] https://lists.opendaylight.org/pipermail/integration-dev/2015-October/004942.html
From: Michal Polkoráb [mailto:michal.polkorab@...]
Hello,
please see Openflow Protocol Library (Openflowjava) M3 status below:
Functionality Freeze: 1. Final list of externally consumable APIs defined: Yes 2. Are all your inter-project dependencies resolved (i.e., have the other projects you were counting on given you what you needed)? Yes 3. Were there any project-specific deliverables planned for this milestone? No
Karaf Features Defined: 4. Are all your project's features that are intended for release added to the features.xml and checked into the integration git repository? Yes features.xml are pulled by openflowplugin 5. List all top-level, user-facing, and stable Karaf features for your project. No user-facing features. Top-level feature: odl-openflowjava-protocol - whole openflowjava functionality Top-level features are usually installed by user-facing features.
Documentation: 6. List the kinds of documentation you will provide including at least: - developer guide 7. Have you checked in the AsciiDoc outlines to the docs repository? No - no feature / functionality updates since Lithium
Integration and Test: 8. Have you started automated system testing for your top-level features. No - system test waiver approved
9. Have you filled out basic system test plan template for each top-level feature (karaf and not karaf) and a comprehensive system test plan template including functionality, cluster, scalability, performance, longevity/stability for each stable feature? No - system test waiver approved
Best regards, Michal Polkorab MichalPolkoráb Software Developer
MichalPolkoráb Software Developer
|