5 Please provide updates on any previously-incomplete items from prior milestone
11 1. Final list of externally consumable APIs defined: Yes/No
13 Yes. No tentative API.
15 - If you had Tentative APIs, have they been moved to Provisional or dropped?
19 - If any of your Tentative APIs were dropped, have you notified all projects
20 that were expecting them? (Yes/No) <link to e-mail>
24 - Also please list all dropped APIs.
28 2. Are all your inter-project dependencies resolved (i.e., have the other
29 projects you were counting on given you what you needed)? (Yes/No)
33 3. Were there any project-specific deliverables planned for this milestone?
39 Karaf Features Defined:
40 -----------------------
42 1. Are all your project's features that are intended for release added to the
43 features.xml and checked into integration git repository? (Yes/No)
47 - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml
49 2. List all top-level, user-facing, and stable Karaf features for your project.
51 - odl-coe: https://git.opendaylight.org/gerrit/gitweb?p=coe.git;a=blob;f=features/odl-coe/pom.xml
56 1. List the kinds of documentation you will provide including at least:
59 https://wiki.opendaylight.org/view/COE:Design_doc
60 - An installation guide for any top-level features that require more than
61 feature:install <feature-name> to install.
62 N/A as this is covered by service provider, e.g. netvirt
63 - Release notes (mandatory) [2]_.
64 COE will be doing a release only in Oxygen, will be adding that towards the end
65 - Optional tutorials and how-tos.
68 2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)
72 - https://git.opendaylight.org/gerrit/gitweb?p=coe.git;a=tree;f=docs
77 1. Have you started automated system testing for your top-level features?
80 N/A (System test will be covered by the service provider which is going to be Netvirt)
82 2. Have you filled out basic system test plan template for each top-level
83 feature (karaf and not karaf) and a comprehensive system test plan template
84 including functionality, cluster, scalability, performance,
85 longevity/stability for each stable feature? (Yes/No)
93 1. Were there any project-specific deliverables planned for this milestone?
98 2. Have you updated your project facts with the project type category? (Yes/No)
102 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)
106 .. [1] Note that you can only reasonably hold a project to something if you
107 formally asked for it during the release planning process and the project
108 team members acknowledged that ask saying they would do it.
109 .. [2] Release notes must be updated prior to a major release. It is a good idea
110 to keep release notes as a living document when significant changes are
112 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html