The release note mechanism has been evolving and is now at the point that the odp repo needs to only contain notes that we as humans wish to add. The automation will add bugzilla, api and abi material to it to form a complete report that necessarily has to be generated from the release is not be in the tagged release.
The generated report can be found on opendataplane.org It is expected that these notes be rewritten for each release and checked in as work progresses so that the content is in place when the tag is made. Signed-off-by: Mike Holmes <[email protected]> --- doc/release-notes/README | 4 ++++ doc/release-notes/odp-known-issues.adoc | 1 + doc/release-notes/odp-new-features.adoc | 1 + 3 files changed, 6 insertions(+) create mode 100644 doc/release-notes/README create mode 100644 doc/release-notes/odp-known-issues.adoc create mode 100644 doc/release-notes/odp-new-features.adoc diff --git a/doc/release-notes/README b/doc/release-notes/README new file mode 100644 index 0000000..239ca4c --- /dev/null +++ b/doc/release-notes/README @@ -0,0 +1,4 @@ +These notes are checked in per release, once a release is tagged these +notes are built along with a bug summary from bugzilla, a specification +documentation diff and an abi diff analysis for the full release notes +published on opendataplane.org. diff --git a/doc/release-notes/odp-known-issues.adoc b/doc/release-notes/odp-known-issues.adoc new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/doc/release-notes/odp-known-issues.adoc @@ -0,0 +1 @@ + diff --git a/doc/release-notes/odp-new-features.adoc b/doc/release-notes/odp-new-features.adoc new file mode 100644 index 0000000..8b13789 --- /dev/null +++ b/doc/release-notes/odp-new-features.adoc @@ -0,0 +1 @@ + -- 2.7.4 _______________________________________________ lng-odp mailing list [email protected] https://lists.linaro.org/mailman/listinfo/lng-odp
