[release] YangIDE Boron M3 status
|
an.ho@huawei.com
For Item #9, is there an ETA for the system test template?
Best Regards, An Ho
From: release-bounces@... [mailto:release-bounces@...]
On Behalf Of David M. Karr
YangIDE
Functionality Freeze:
1. Final list of externally consumable APIs defined: NA The YangIDE project does not provide any externally consumable APIs. 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? NA The YangIDE project does not provide any Karaf features. 5. List all top-level, user-facing, and stable Karaf features for your project. NA Documentation: 6. List the kinds of documentation you will provide including at least: ** Installation Guide: Specifies prerequisites and steps for installing the plugin into Eclipse. ** User Guide: Overview of features and steps to utilize each major feature, along with a video exploring all of the major features.
7. Have you checked in the AsciiDoc outlines to the docs repository? Yes
Integration and Test:
8. Have you started automated system testing for your top-level features. No YangIDE does require automated system test, but it runs in a very different container than Karaf, and it will require infrastructure changes for system testting of it to even be possible. 9. Have you filled out basic system test plan template [1] 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
[0] https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan
|
|
|
|
On 06/01/2016 02:30 PM, An Ho wrote:
No. I don't think it's worthwhile to define a process or template until we know that we'll even be able to do this (gui-based automated integration testing) with the ODL infrastructure.
|
|
|
|
an.ho@huawei.com
Projects without automated integration testing with the ODL infrastructure may elect to define manual testing. For example, the most obvious test case could be the following:
1. Download fresh copy of Eclipse 4.5.0 (Mars). Go through “Add Update Site” wizard and add the YangIDE Eclipse Plugin Update Site. Confirm installation is complete.
Best Regards, An Ho
From: David M. Karr [mailto:davidmichaelkarr@...]
On 06/01/2016 02:30 PM, An Ho wrote:
For Item #9, is there an ETA for the system test template?
Best Regards, An Ho
From:
release-bounces@... [mailto:release-bounces@...]
On Behalf Of David M. Karr
YangIDE
Functionality Freeze:
1. Final list of externally consumable APIs defined: NA The YangIDE project does not provide any externally consumable APIs. 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? NA The YangIDE project does not provide any Karaf features. 5. List all top-level, user-facing, and stable Karaf features for your project. NA Documentation: 6. List the kinds of documentation you will provide including at least: ** Installation Guide: Specifies prerequisites and steps for installing the plugin into Eclipse. ** User Guide: Overview of features and steps to utilize each major feature, along with a video exploring all of the major features.
7. Have you checked in the AsciiDoc outlines to the docs repository? Yes
Integration and Test:
8. Have you started automated system testing for your top-level features. No YangIDE does require automated system test, but it runs in a very different container than Karaf, and it will require infrastructure changes for system testting of it to even be possible. 9. Have you filled out basic system test plan template [1] 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
[0] https://wiki.opendaylight.org/view/Simultaneous_Release:Boron_Release_Plan
|
|
|
|
I guess that's better than nothing. I already do that. I'll
start writing that doc then.
toggle quoted messageShow quoted text
On 06/01/2016 02:39 PM, An Ho wrote:
|
|
|
|
Now I remember why it was unfortunate that you ended up creating
the yangide project pages for me. I still don't know how to
create a wiki page from a template. :)
toggle quoted messageShow quoted text
On 06/01/2016 02:39 PM, An Ho wrote:
|
|
|
|
Michael Vorburger
Just re. "be able to do this (gui-based automated integration testing) with the ODL infrastructure", FYI I've had some conversations with Thanh about this, and track status under https://bugs.opendaylight.org/show_bug.cgi?id=5864. This is something I could do some time over the coming weeks (I've just had other priorities so far). Tx, M. -- Michael Vorburger <vorburger@...> | IRC: vorburger @freenode | G/Hangout: michael.vorburger | Skype: mike_vorburger | ~ = http://vorburger.ch
On Wed, Jun 1, 2016 at 11:52 PM, David M. Karr <davidmichaelkarr@...> wrote:
|
|
|