Following up on the verification program discussion in the TSC call this week:
In the Nov 28, 2017 TSC meeting<http://meetbot.opnfv.org/meetings/opnfv-meeting/2017/opnfv-meeting.2017-11-28-14.00.html>, we discussed ways of planning for future releases of the OPNFV Verified Program.. During the Danube cycle, we adopted a pragmatic approach of working from bottom-up (i.e. what the community had already done), but noted its limitations as well as top-down analysis of overall program requirements. The details are documented in this Addendum<http://docs.opnfv.org/en/stable-danube/submodules/dovetail/docs/testing/user/cvpaddendum/index.html>. Specifically, the Addendum called out areas where either features or test cases fall short in OPNFV release (Danube), and future test area considerations based inputs from the community and EUAG. I added a table in the following wiki as an attempt to organize the information in an easy format with an intent to facilitate community discussions, which, hopefully lead to actions to identify where the priorities are, and efforts from all projects to fill those gaps. Please provide feedback, ideas/comments, and also join the meetings in next week's Plugfest. Thank you. https://wiki.opnfv.org/display/dovetail/Dovetail+Future+Release+Priority+Inputs Regards Wenjing
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
