Distribution M3 & M4 readout

Change-Id: I56067574eb53f11b629c30659f5ff667e08340eb
Signed-off-by: Luis Gomez <ecelgp@gmail.com>
Signed-off-by: klou <klou.external@gmail.com>

diff --git a/docs/release-process/milestone-readouts/m3/distribution.rst b/docs/release-process/milestone-readouts/m3/distribution.rst
new file mode 100644 (file)
index 0000000..6b65b3c
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m3/distribution.rst
@@ -0,0 +1,40 @@
+========================
+Integration/Distribution
+========================
+
+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
+
+   - :doc:`../../../user-guide/distribution-version-user-guide`
+   - :doc:`../../../developer-guide/distribution-version`
+   - :doc:`../../../developer-guide/distribution-test-features`
+   - :doc:`../../../getting-started-guide/common-features/clustering`
+   - :doc:`../../../getting-started-guide/common-features/persistence_and_backup`
+
+4. Has your project met the requirements to be included in Maven Central [2]_?
+   No, missing GPG signing.
+
+5. Were project-specific deliverables planned for this milestone delivered
+   successfully? Yes
+
+6. Have you started automated system testing for your top-level features? Yes
+
+   - https://jenkins.opendaylight.org/releng/view/distribution
+
+7. Does your project use any ports, including for testing? No
+
+8. Does your project build successfully in Autorelease? Yes
+
+   - https://jenkins.opendaylight.org/releng/view/distribution/job/integration-distribution-validate-autorelease-oxygen
+
+.. [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

diff --git a/docs/release-process/milestone-readouts/m4/distribution.rst b/docs/release-process/milestone-readouts/m4/distribution.rst
new file mode 100644 (file)
index 0000000..40e6f96
--- /dev/null
+++ b/docs/release-process/milestone-readouts/m4/distribution.rst
@@ -0,0 +1,39 @@
+========================
+Integration/Distribution
+========================
+
+1. Do you have any previously-incomplete items from prior milestone
+   readouts? No
+
+2. Has your project met code freeze [1]_? Yes
+
+3. Are all externally visible strings frozen to allow for translation &
+   documentation? Yes
+
+4. Is your documentation complete [2]_? Yes
+
+   - :doc:`../../../user-guide/distribution-version-user-guide`
+   - :doc:`../../../developer-guide/distribution-version`
+   - :doc:`../../../developer-guide/distribution-test-features`
+   - :doc:`../../../getting-started-guide/common-features/clustering`
+   - :doc:`../../../getting-started-guide/common-features/persistence_and_backup`
+
+5. Were project-specific deliverables planned for this milestone delivered
+   successfully? No Deliverables
+
+6. Are you running at least one basic automated system test job for each
+   top-level feature? Yes
+
+   - https://jenkins.opendaylight.org/releng/view/distribution
+
+7. Do you have any CLM violations? Yes
+
+   - The CLM job reports every violation from upstream
+     OpenDaylight projects pulled in by Distribution.
+     Those violations should be addressed by upstream projects themselves.
+
+.. [1] Only bug fixes are allowed from now on
+.. [2] Only editing and enhancing should take place from now on
+.. [3] Unit and/or integration test coverage of at least 75%
+.. [4] These test jobs include functionality, cluster, scalability, performance,
+       longevity/stability