...

Ultimately this will ensure consistency across ONAP projects, and free individual projects from redundant work whenever the standard configurations need to be changed.

Release Notes

...

Frankfurt

https://docs.onap.readthedocs.ioorg/enprojects/latestonap-integration/submodules/integration.git/docsen/frankfurt/release-notes.html#ohtml#release-parent.notes

How to Implement for Your Project

...

Notes on Releasing OPARENT

1. Update the dependencies/pom.xml and dependencies-clm/pom.xml with any updated versions of upstream projects.
   1. this should be done with the security team to identify the acceptable or better version
   2. project team repos should also be validated to make sure they understand any implications on client code before they up-rev
   3. The merge of this change should create a maven merge job log that can be referenced
   4. This should be X.Y.Z-SNAPSHOT as the revision.
2. Discuss at the PTL call that an updated version of OPARENT will be released.
3. Use the LF self-release process to create the releases/X.Y.Z.yaml file that points to the maven merge job and the release number
   1. https://gerrit.onap.org/r/#/c/oparent/+/94862/
4. The self release jobs should run and publish the maven artifact for X.Y.Z release.
5. After that job runs you need to up-rev the Patch version of oparent
   1. https://gerrit.onap.org/r/#/c/oparent/+/94863/
   2. This changes the revision to X.Y.Z+1-SNAPSHOT (or whatever X,Y,Z combination is appropriate) in all the affected files.
6. oparent repository would now be ready for step 1.

...