Page History

...

1. The list of repos that are to be included in Amber release under your project.
2. For each repo, provide the following information:
1. License Status:
   1. What license for each repo, Apache 2 or O-RAN?
   2. Whether the LICENSES.txt is included at the root of the repo and whether each code file has a license and copyright claim header?
   3. NOT including any contributing company proprietary information?
2. Code status:
   1. Is the code available (code MUST be in by code freeze date of 11/04)?
   2. Is the code build-able?
   3. Is the building and artifact generation integrated with LF Jenkins? We can mark this item as "yes" if a particular repo implements a (a) verify, (b) merge and (c) daily release job. The group maintaining a repo needs to implement this. 
3. Documentation status:
   1. Following the documentation format, structure, and template provided by DOC project?

      1. It is sufficient to have these files in your repo as per https://wiki.o-ran-sc.org/display/DOC#DocumentationHome-RequiredFiles  as per these templates https://wiki.o-ran-sc.org/display/DOC#DocumentationHome-Templates :     docs/installation-guides.rst,  docs/release-notes.rst ,  docs/developer-guide.rst , docs/api-docs.rst. (docs/index.rst is also needed, but coming from the next step below).  For Amber release the minimum requirement is the release note file.

         1. README.md file at repo root.  (no need to publish to readthedocs.io).
   2. Documentation buildable by the DOC project?
      1. Also implement a Jenkins job for pushing these to https://o-ran-sc.readthedocs.io/en/latest/ . Instructions on how to publish them to via an automatic Jenkins job are here: Configure Repo for Documentation.  (the doc-template directory under the doc repo already contains all the necessary files).
   3. Prepared a video demo for how to build and run your project.

...