5 Please provide updates on any previously-incomplete items from prior milestone
12 1. Final list of externally consumable APIs defined: Yes
14 - If you had Tentative APIs, have they been moved to Provisional or dropped? No
16 - If any of your Tentative APIs were dropped, have you notified all projects
17 that were expecting them? No API dropped.
18 - Also please list all dropped APIs. - None
20 2. Are all your inter-project dependencies resolved (i.e., have the other
21 projects you were counting on given you what you needed)? Yes
23 3. Were there any project-specific deliverables planned for this milestone? No (Mainly Bug Fixes)
26 Karaf Features Defined:
27 -----------------------
29 1. Are all your project's features that are intended for release added to the
30 features.xml and checked into integration git repository? Yes
32 - `Existing Features <https://git.opendaylight.org/gerrit/gitweb?p=nic.git;a=shortlog;h=HEAD>`_
34 2. List all top-level, user-facing, and stable Karaf features for your project.
36 - **Network Intent Composition (NIC)**:
38 * **odl-nic-inent-common**: User should install this feature if they want to load the NIC project.
43 1. List the kinds of documentation you will provide including at least:
47 * :doc:`NIC User Guide <../../../user-guide/network-intent-composition-(nic)-user-guide>`
49 * **Developer Guide(s):**
51 * :doc:`NIC Developer Guide <../../../developer-guide/network-intent-composition-guide>`
55 2. Have you checked in a reStructuredText outline to the docs repository? No
60 1. Have you started automated system testing for your top-level features? Yes
62 - ` CSIT Tests <https://jenkins.opendaylight.org/releng/view/nic/>`_
64 2. Have you filled out basic system test plan template for each top-level
65 feature (karaf and not karaf) and a comprehensive system test plan template
66 including functionality, cluster, scalability, performance,
67 longevity/stability for each stable feature? No
69 - Not done yet, will be available by M3
71 3. Have you integrated odlparent 3 / yangtools 2? No
76 1. Were there any project-specific deliverables planned for this milestone? Yes (Mostly add new test cases)
78 2. Have you updated your project facts with the project type category? Yes
80 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
82 .. [1] Note that you can only reasonably hold a project to something if you
83 formally asked for it during the release planning process and the project
84 team members acknowledged that ask saying they would do it.
85 .. [2] Release notes must be updated prior to a major release. It is a good idea
86 to keep release notes as a living document when significant changes are
88 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html