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?
16 - NA https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Oxygen_Release_Plan
18 2. Are all your inter-project dependencies resolved (i.e., have the other
19 projects you were counting on given you what you needed)? No new dependencies
21 3. Were there any project-specific deliverables planned for this milestone?
24 Karaf Features Defined:
25 -----------------------
27 1. Are all your project's features that are intended for release added to the
28 features.xml and checked into integration git repository? No
32 2. List all top-level, user-facing, and stable Karaf features for your project.
34 - **odl-lispflowmapping-msmr**: This is the core feature that provides the Mapping
35 Services and include the LISP southbound plugin feature as well.
40 1. List the kinds of documentation you will provide including at least:
45 2. Have you checked in a reStructuredText outline to the docs repository? Yes
47 - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/lisp-flow-mapping-user-guide.rst;h=db9419246f3e707f23c48d6ed965f11de7911c48;hb=HEAD
52 1. Have you started automated system testing for your top-level features? Yes
54 - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-msmr-all-oxygen/
55 - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-1node-performance-only-oxygen/
56 - https://jenkins.opendaylight.org/releng/view/lispflowmapping/job/lispflowmapping-csit-3node-msmr-all-oxygen/
58 2. Have you filled out basic system test plan template for each top-level
59 feature (karaf and not karaf) and a comprehensive system test plan template
60 including functionality, cluster, scalability, performance,
61 longevity/stability for each stable feature? Yes
63 - https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Oxygen:All_Integration_System_Test
68 1. Were there any project-specific deliverables planned for this milestone?
71 2. Have you updated your project facts with the project type category? Yes
73 3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? Yes
75 .. [1] Note that you can only reasonably hold a project to something if you
76 formally asked for it during the release planning process and the project
77 team members acknowledged that ask saying they would do it.
78 .. [2] Release notes must be updated prior to a major release. It is a good idea
79 to keep release notes as a living document when significant changes are
81 .. [3] https://lists.opendaylight.org/pipermail/tsc/2016-December/006468.html