...
- No cross-project SNAPSHOT dependencies
- Teams to version and release on own schedule
- Source control central artifact version manifest
- Teams to declare the “correct version” for cross-project use
- TSC to approve version manifest for simultaneous release, e.g. Amsterdam
- Maven plugin to warn against outdated dependencies vs. the manifest
Java (Maven) Artifacts
- Set up -release-version jobs to deploy candidate artifacts to Staging
- Generates candidate “autorelease-xxxx” directories in Nexus
- Email helpdesk@onap.org to select a candidate as formal release artifact
- Specify the specific Jenkins build job that generated the selected candidate build, e.g. https://jenkins.onap.org/view/oparent/job/oparent-master-release-version-java-daily/16/
- LF to sign and release the artifacts to Releases repo
- LF to sign and tag the version in Gerrit repo
- Bump your own version numbers
- SNAPSHOT versions in pom.xml
- Staging/Release version in version.properties
...