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)? N/A
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 2. List all top-level, user-facing, and stable Karaf features for your project.
33 - see list of external APIs here:
34 https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Oxygen/Release_plan#Externally_Consumable_APIs.
39 1. List the kinds of documentation you will provide including at least:
41 - One user/operator guide section per user-facing feature.
42 - Release notes (mandatory).
44 2. Have you checked in a reStructuredText outline to the docs repository? No
49 1. Have you started automated system testing for your top-level features?
52 - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-all-oxygen/
53 - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-oxygen/
54 - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-3node-clustering-all-oxygen/
56 2. Have you filled out basic system test plan template for each top-level
57 feature (karaf and not karaf) and a comprehensive system test plan template
58 including functionality, cluster, scalability, performance,
59 longevity/stability for each stable feature? No
61 - no stable features yet
66 1. Were there any project-specific deliverables planned for this milestone?
69 2. Have you updated your project facts with the project type category? Yes
71 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
73 .. [1] Note that you can only reasonably hold a project to something if you
74 formally asked for it during the release planning process and the project
75 team members acknowledged that ask saying they would do it.
76 .. [2] Release notes must be updated prior to a major release. It is a good idea
77 to keep release notes as a living document when significant changes are
79 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html