RICAPP (E Release)

Owned by Matti Hiltunen
Last updated: Feb 15, 2022 by subhash
1 min read


These are the planned versions to be used for the E release.

ComponentImage in release repo (10002) or in staging repo (10004)Gerrit review (to be used to recreate image if disappeared from staging)
ric-app/adnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-ad:0.0.2 (Same as D release)

https://gerrit.o-ran-sc.org/r/c/ric-app/ad/+/6493

ric-app/qpnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-qp:0.0.4https://gerrit.o-ran-sc.org/r/c/ric-app/qp/+/7274
ric-app/bouncernexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-bouncer: TODO
ric-app/ts

nexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-ts:1.2.0

https://gerrit.o-ran-sc.org/r/c/ric-app/ts/+/7279
ric-app/lpnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-lp: 0.3.0https://gerrit.o-ran-sc.org/r/c/ric-app/lp/+/7395
ric-app/hwnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-hw:1.1.1  (same as D release)https://gerrit.o-ran-sc.org/r/c/ric-app/hw/+/3851
ric-app/hw-pythonnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-hw-python:1.1.0https://gerrit.o-ran-sc.org/r/c/ric-app/hw-python/+/7378
ric-app/hw-gonexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-hw-go:1.1.1https://gerrit.o-ran-sc.org/r/c/ric-app/hw-go/+/7560
ric-app/mcnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-mc:1.0.11 (same as D release)https://gerrit.o-ran-sc.org/r/c/ric-app/mc/+/6482
ric-app/rcnexus3.o-ran-sc.org:10002/o-ran-sc/ric-app-rc: TODO
scp/ric-app/kpimonnexus3.o-ran-sc.org:10002/o-ran-sc/scp/ric-app-kpimon:1.0.0 (same as C release)


End-of-release tasks

  1. Complete code upload/update
  2. Double-check from Code coverage reports that all blocker code smells have been addressed as per RC-5 in Release criteria checklist template
  3. If applicable, release binary artifact(s) such as docker container image(s), or libraries.
    1. Instructions: O-RAN Developer's Guide to CI Resources and Processes at the LF
  4. Update references to artifacts in the above table. Also fill in the last column with reference to the gerrit review that can be used to regenerate the artifact.
  5. Update release notes: Make sure you have a release summary as per RC-1 in Release criteria checklist template: "every component must update their rst release notes (in the doc subfolder in the repo)". Based on this per-component description, the PTL will create a release summary.
    1. Release Notes must be published to https://docs.o-ran-sc.org/en/latest/
    2. Instructions for setting up documentation folder for repo: https://lf-o-ran-sc.atlassian.net/wiki/display/DOC/Configure+Repo+for+Documentation
  6. After finishing all the above, branch "e-release" (all lower case).
    1. Repo owners (committers) can create branch. 
    2. There are several ways to create branch.  For example do this: Login to web UI https://gerrit.o-ran-sc.org/r/admin/repos > Find repo, click on repo name > "Branches" in left panel > "Create New"