5 Please provide updates on any previously-incomplete items from prior milestone
11 1. Final list of externally consumable APIs defined: Yes
13 2. Are all your inter-project dependencies resolved (i.e., have the other
14 projects you were counting on given you what you needed)? Yes
16 3. Were there any project-specific deliverables planned for this milestone? No
18 Karaf Features Defined:
19 -----------------------
21 1. Are all your project's features that are intended for release added to the
22 features.xml and checked into integration git repository? Yes
24 - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
26 2. List all top-level, user-facing, and stable Karaf features for your project.
28 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/netvirt.rst
33 1. List the kinds of documentation you will provide including at least:
35 - User Guide, Developer Guide, Tutorials
37 2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
39 - https://git.opendaylight.org/gerrit/gitweb?p=netvirt.git;a=tree;f=docs;h=5eba14dcaa5780e9b4b9052924b2c7f5df7eee0c;hb=HEAD
44 1. Have you started automated system testing for your top-level features? Yes
46 - https://jenkins.opendaylight.org/releng/view/netvirt-csit/
48 2. Have you filled out basic system test plan template for each top-level
49 feature (karaf and not karaf) and a comprehensive system test plan template
50 including functionality, cluster, scalability, performance,
51 longevity/stability for each stable feature? Yes
53 - https://wiki.opendaylight.org/view/NetVirt:Integration_Test
55 3. Have you integrated odlparent 3 / yangtools 2? No
57 - (If yes, link to gerrit patch)
62 1. Were there any project-specific deliverables planned for this milestone? No
64 2. Have you updated your project facts with the project type category? Yes
66 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
68 .. [1] Note that you can only reasonably hold a project to something if you
69 formally asked for it during the release planning process and the project
70 team members acknowledged that ask saying they would do it.
71 .. [2] Release notes must be updated prior to a major release. It is a good idea
72 to keep release notes as a living document when significant changes are
74 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html