FaaS: Add M2 and M3 status

Change-Id: I7e981cc57c60e741f625053996f5f53b6166d55b
Signed-off-by: xingjun <xingjun.chu@huawei.com>
Signed-off-by: Kit Lou <klou.external@gmail.com>

diff --git a/docs/release-process/milestone-readouts/m2/faas.rst b/docs/release-process/milestone-readouts/m2/faas.rst
new file mode 100644 (file)
index 0000000..5dbc267
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m2/faas.rst
@@ -0,0 +1,70 @@
+====
+FaaS
+====
+
+Please provide updates on any previously-incomplete items from prior milestone
+readouts.  None
+
+Functionality Freeze:
+---------------------
+
+1. Final list of externally consumable APIs defined: Yes
+
+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 deliverables
+
+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
+
+   - https://git.opendaylight.org/gerrit/gitweb?p=integration/distribution.git;a=blob;f=features/repos/index/pom.xml;
+
+2. List all top-level, user-facing, and stable Karaf features for your project.
+
+   - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/release-notes/projects/faas.rst;
+
+Documentation:
+--------------
+
+1. List the kinds of documentation you will provide including at least:
+
+   - User Guide, Developer Guide
+
+2. Have you checked in a reStructuredText outline to the docs repository? Yes
+
+   - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/user-guide/fabric-as-a-service.rst;
+   - https://git.opendaylight.org/gerrit/gitweb?p=docs.git;a=blob;f=docs/developer-guide/fabric-as-a-service.rst;
+
+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? Yes
+
+   - https://wiki.opendaylight.org/view/FaaS:SystemTestPlan
+
+Project Specific:
+-----------------
+
+1. Were there any project-specific deliverables planned for this milestone? No deliverables
+
+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

diff --git a/docs/release-process/milestone-readouts/m3/faas.rst b/docs/release-process/milestone-readouts/m3/faas.rst
new file mode 100755 (executable)
index 0000000..aa226b4
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m3/faas.rst
@@ -0,0 +1,32 @@
+====
+FaaS
+====
+
+1. Do you have any previously-incomplete items from prior milestone
+   readouts? No
+
+2. Has your project achieved API freeze such that all externally accessible
+   Stable or Provisional APIs will not be modified after now? Yes
+
+3. Do you have content in your project documentation? Yes
+
+4. Has your project met the requirements to be included in Maven Central [2]_? No
+
+5. Were project-specific deliverables planned for this milestone delivered
+   successfully? No Deliverables
+
+6. Have you started automated system testing for your top-level features? No
+
+7. Does your project use any ports, including for testing? Yes
+
+   - 6641, 6653
+   - If yes, have you updated the wiki [3]_ with all ports used? Yes
+
+8. Does your project build successfully in Autorelease? Yes
+
+.. [1] Provide a link to a gerrit search for patches modifying the files
+       defined as specifying the API. For example:
+       https://git.opendaylight.org/gerrit/#/q/file:%255Eopendaylight/md-sal/sal-binding-api/.%252B+status:merged+project:controller
+.. [2] http://central.sonatype.org/pages/requirements.html
+.. [3] https://wiki.opendaylight.org/view/Ports
+.. [4] https://wiki.opendaylight.org/view/RelEng/Autorelease/Project_Autorelease_Requirements