Add Groupbasedpolicy M2 offset2 status

Change-Id: Ie545947ea49a82b635e34386b70082b807abd296
Signed-off-by: Michal Cmarada <michal.cmarada@pantheon.tech>

diff --git a/docs/release-process/milestone-readouts/m2/groupbasedpolicy.rst b/docs/release-process/milestone-readouts/m2/groupbasedpolicy.rst
new file mode 100644 (file)
index 0000000..805a5f7
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m2/groupbasedpolicy.rst
@@ -0,0 +1,79 @@
+================
+GROUPBASEDPOLICY
+================
+
+Please provide updates on any previously-incomplete items from prior milestone
+readouts.
+
+Functionality Freeze:
+---------------------
+
+1. Final list of externally consumable APIs defined: Yes
+
+   - 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? N/A
+   - Also please list all dropped APIs.
+
+2. Are all your inter-project dependencies resolved (i.e., have the other
+   projects you were counting on given you what you needed)? N/A
+
+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
+
+2. List all top-level, user-facing, and stable Karaf features for your project.
+
+   - see list of external APIs here:
+     https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Oxygen/Release_plan#Externally_Consumable_APIs.
+
+Documentation:
+--------------
+
+1. List the kinds of documentation you will provide including at least:
+
+   - One user/operator guide section per user-facing feature.
+   - Release notes (mandatory).
+
+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?
+   Yes
+
+   - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-3-node-all-oxygen/
+   - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-1node-6node-all-oxygen/
+   - https://jenkins.opendaylight.org/releng/view/groupbasedpolicy/job/groupbasedpolicy-csit-3node-clustering-all-oxygen/
+
+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
+
+   - no stable features 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