Template:
- What your team has achieved
- Block issues / help needed
- Test
- Conducted CSIT Q&A session to answer questions from the community
- Creation of Jira Filters & Dashboard:
- Integration Dashboard: https://jira.onap.org/secure/Dashboard.jspa?selectPageId=10307
- List of defect created by the Integration Team: https://jira.onap.org/issues/?filter=10564
- Release / O-Parent
- Artifact versioning:
ONAP will support individual artifacts having their own versions and release schedules
Move the declared artifact version list outside the build in order to avoid SNAPSHOT dependencies.
- Provide a tool (plugin or script) to automatically warn against outdated dependencies vs. the declared version list.
- Define the official ONAP version string (e.g. "ONAP R1 Amsterdam Release") inside the oparent artifact or POM.
- Require that all artifacts be built against the latest oparent release version for the ONAP release. Note that the oparent artifact version itself might be something like 1.0.2 which is distinct from the official ONAP version string contained within.
- Work on defining JJB jobs and process for project teams to version bump and release their own artifacts
- Blocking Issue: Need input/response from LF staff on a process to officially release artifacts (i.e. to actual Releases repo, not just to Staging)
- Investigated tools to help with with Maven artifact version dependencies:
- Use maven-enforcer-plugin to avoid SNAPSHOT dependencies
- Help Needed: Need help finding or creating a Maven plugin that can check against an explicit artifact version list such as the ONAP version manifest
- Ongoing work on docker image build guidelines/approach for OPEN-O seeded microservices
- Ongoing code reviews and assistance to the community on ci-management and environment issues
- Artifact versioning: