From: Kit Lou Date: Wed, 6 Dec 2017 20:45:30 +0000 (+0000) Subject: Merge "SNMP M2 Milestone Readout" X-Git-Tag: release/oxygen~1412 X-Git-Url: https://git.opendaylight.org/gerrit/gitweb?a=commitdiff_plain;h=e25c1a19ea160a47539262103e4e22231144328b;hp=0453de656ac0d884e6ce3e062da4ff6c536d315b;p=docs.git Merge "SNMP M2 Milestone Readout" --- diff --git a/docs/release-process/milestone-readouts/m2/snmp.rst b/docs/release-process/milestone-readouts/m2/snmp.rst new file mode 100644 index 000000000..b2a42a678 --- /dev/null +++ b/docs/release-process/milestone-readouts/m2/snmp.rst @@ -0,0 +1,83 @@ +==== +SNMP +==== + +Please provide updates on any previously-incomplete items from prior milestone +readouts. +None + +Functionality Freeze: +--------------------- + +1. Final list of externally consumable APIs defined: Yes + + - If you had Tentative APIs, have they been moved to Provisional or dropped? + Yes + - If any of your Tentative APIs were dropped, have you notified all projects + that were expecting them? 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 + +3. Were there any project-specific deliverables planned for this milestone? + 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 + + - `Features `_ + +2. List all top-level, user-facing, and stable Karaf features for your project. + + :odl-snmp-plugin: Provides basic Southbound SNMP protocol support + +Documentation: +-------------- + +1. List the kinds of documentation you will provide including at least: + + - One user/operator guide section per user-facing feature. + - One developer guide per top-level feature. + - An installation guide for any top-level features that require more than + feature:install to install. + - Release notes (mandatory) [2]_. + - Optional tutorials and how-tos. + +2. Have you checked in a reStructuredText outline to the docs repository? No + +Integration and Test: +--------------------- + +1. Have you started automated system testing for your top-level features? + No + +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? No + +3. Have you integrated odlparent 3 / yangtools 2? No + + - Not yet, since upstream dependencies haven't fully integrated yet. + +Project Specific: +----------------- + +1. Were there any project-specific deliverables planned for this milestone? + No + +2. Have you updated your project facts with the project type category? Yes + +3. Do you acknowledge the changes to the RC Blocking Bug Policy [3]_? 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