5 Please provide updates on any previously-incomplete items from prior milestone
11 1. Final list of externally consumable APIs defined: Yes
13 - If you had Tentative APIs, have they been moved to Provisional or dropped?
15 - If any of your Tentative APIs were dropped, have you notified all projects
16 that were expecting them? N/A
17 - Also please list all dropped APIs.
19 2. Are all your inter-project dependencies resolved (i.e., have the other
20 projects you were counting on given you what you needed)? Yes
22 3. Were there any project-specific deliverables planned for this milestone?
25 Karaf Features Defined:
26 -----------------------
28 1. Are all your project's features that are intended for release added to the
29 features.xml and checked into integration git repository? Yes
31 - https://git.opendaylight.org/gerrit/#/c/65830/
33 2. List all top-level, user-facing, and stable Karaf features for your project.
35 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/tsdr.rst
40 1. List the kinds of documentation you will provide including at least:
43 - Installation Guide(s).
44 - Release notes (mandatory).
45 - Tutorials and how-tos.
47 2. Have you checked in a reStructuredText outline to the docs repository? Yes
49 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/tsdr-user-guide.rst
54 1. Have you started automated system testing for your top-level features?
57 - https://jenkins.opendaylight.org/releng/view/tsdr/
59 2. Have you filled out basic system test plan template for each top-level
60 feature (karaf and not karaf) and a comprehensive system test plan template
61 including functionality, cluster, scalability, performance,
62 longevity/stability for each stable feature? Yes
64 - https://wiki.opendaylight.org/view/TSDR:TSDR_Oxygen_Testing_with_Results#Test_Cases_.26_Results
69 1. Were there any project-specific deliverables planned for this milestone?
72 2. Have you updated your project facts with the project type category? Yes
74 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
76 .. [1] Note that you can only reasonably hold a project to something if you
77 formally asked for it during the release planning process and the project
78 team members acknowledged that ask saying they would do it.
79 .. [2] Release notes must be updated prior to a major release. It is a good idea
80 to keep release notes as a living document when significant changes are
82 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html