===
COE
===

Please provide updates on any previously-incomplete items from prior milestone
readouts.

Functionality Freeze:
---------------------

1. Final list of externally consumable APIs defined: Yes/No

   Yes. No tentative API.

   - If you had Tentative APIs, have they been moved to Provisional or dropped?

     N/A

   - If any of your Tentative APIs were dropped, have you notified all projects
     that were expecting them? (Yes/No) <link to e-mail>

     N/A

   - Also please list all dropped APIs.

     N/A

2. Are all your inter-project dependencies resolved (i.e., have the other
   projects you were counting on given you what you needed)? (Yes/No)

   Yes.

3. Were there any project-specific deliverables planned for this milestone?
   Yes/No

   No.


Karaf Features Defined:
-----------------------

1. Are all your project's features that are intended for release added to the
   features.xml and checked into integration git repository? (Yes/No)

   Yes

   - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml

2. List all top-level, user-facing, and stable Karaf features for your project.

   - odl-coe: https://git.opendaylight.org/gerrit/gitweb?p=coe.git;a=blob;f=features/odl-coe/pom.xml

Documentation:
--------------

1. List the kinds of documentation you will provide including at least:

   - Coe Design Document
     https://wiki.opendaylight.org/view/COE:Design_doc
   - An installation guide for any top-level features that require more than
     feature:install <feature-name> to install.
     N/A as this is covered by service provider, e.g. netvirt
   - Release notes (mandatory) [2]_.
     COE will be doing a release only in Oxygen, will be adding that towards the end
   - Optional tutorials and how-tos.
     N/A

2. Have you checked in a reStructuredText outline to the docs repository? (Yes/No)

   Yes

   - https://git.opendaylight.org/gerrit/gitweb?p=coe.git;a=tree;f=docs

Integration and Test:
---------------------

1. Have you started automated system testing for your top-level features?
   (Yes/No)

   N/A (System test will be covered by the service provider which is going to be Netvirt)

2. Have you filled out basic system test plan template for each top-level
   feature (karaf and not karaf) and a comprehensive system test plan template
   including functionality, cluster, scalability, performance,
   longevity/stability for each stable feature? (Yes/No)

   N/A as 1.


Project Specific:
-----------------

1. Were there any project-specific deliverables planned for this milestone?
   (Yes/No)

   No.

2. Have you updated your project facts with the project type category? (Yes/No)

   Yes.

3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? (Yes/No)

   Yes.

.. [1] Note that you can only reasonably hold a project to something if you
       formally asked for it during the release planning process and the project
       team members acknowledged that ask saying they would do it.
.. [2] Release notes must be updated prior to a major release. It is a good idea
       to keep release notes as a living document when significant changes are
       made.
.. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html