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?
19 Karaf Features Defined:
20 -----------------------
22 1. Are all your project's features that are intended for release added to the
23 features.xml and checked into integration git repository? Yes
25 - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;
27 2. List all top-level, user-facing, and stable Karaf features for your project.
29 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/nemo.rst;
34 1. List the kinds of documentation you will provide including at least:
36 - User Guide, Developer Guide, Tutorials
38 2. Have you checked in a reStructuredText outline to the docs repository? Yes
40 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/nemo-user-guide.rst;
41 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/nemo-developer-guide.rst;
46 1. Have you started automated system testing for your top-level features? Yes
48 - https://jenkins.opendaylight.org/releng/view/nemo/
50 2. Have you filled out basic system test plan template for each top-level
51 feature (karaf and not karaf) and a comprehensive system test plan template
52 including functionality, cluster, scalability, performance,
53 longevity/stability for each stable feature? Yes
55 - https://wiki.opendaylight.org/view/NEMO:Integration_Test
60 1. Were there any project-specific deliverables planned for this milestone? No deliverables
62 2. Have you updated your project facts with the project type category? Yes
64 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
66 .. [1] Note that you can only reasonably hold a project to something if you
67 formally asked for it during the release planning process and the project
68 team members acknowledged that ask saying they would do it.
69 .. [2] Release notes must be updated prior to a major release. It is a good idea
70 to keep release notes as a living document when significant changes are
72 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html