2.2 Release

[planetf1]

Create 2.1 release

• Create branch for 2.2 (PR not needed)
• Update master to 2.3-SNAPSHOT
• Update branch version from 2.x-SNAPSHOT to 2.x
• Remove release notes from branch
• update release notes & rename
• Verify notebooks
• Check UI
• Run CTS
• Run FVTs (this is only FVTs automated in the build process)
• Check samples (only samples in the build), utilities, client packaging [like 2.0 - there are issues we know of]
• Check swagger doc
• Verify docker image/charts/compose VDC helm chart - IGC & Atlas connectors are no longer aligned with release #3415
• Launch release pipeline
• Approve release
• Verify artifacts all on maven central (check for JCenter & other errors in release logs)
• Create GitHub release
• ensure any fixes ported to master

[planetf1]

Plan to branch later today (25 Aug) as agreed in status meeting

[planetf1]

FYI currently blocked on resolution of #3560

[planetf1]

Now unblocked -- Graph is working again. continuing with checking samples and vdc chart then should be close to starting the release pipeline.

[planetf1]

Will also include #3415 which at least corrects the location of the additional connectors, one step closer in case we have anyone needing a fix for 3560

[planetf1]

Release is being pushed to maven central.

Outstanding issues:

2020-09-13T09:49:36.2977485Z RESULT - Sync analytics-modeling-client:2.2 = {"message":"In order to sync to Maven Central your package must be included in the JCenter repository"}

This is normal - we don't have any client code yet, though the pom suggests there is as it's of type jar -> reported in #3606 . no further action needed

2020-09-13T09:53:03.1207606Z RESULT - Sync open-metadata-conformance-suite:2.2 = {"status":"Sync Failed","messages":"[Failed to close repository: orgodpi-5240. Server response:\n <nexus-error>\n  <errors>\n    <error>\n      <id>*<\u002fid>\n      <msg>Unhandled: Repository: orgodpi-5240 has invalid state: closed<\u002fmsg>\n    
<\u002ferror>\n  <\u002ferrors>\n<\u002fnexus-error>, Dropping existing partial staging repository.]"}

^ This is a process issue. will retry. It's only a plain pom in this case - no code, so not critical

2020-09-13T11:39:33.5768696Z RESULT - Sync stewardship-engine-services-api:2.2 = {"message":"In order to sync to Maven Central your package must be included in the JCenter repository"}
2020-09-13T11:39:33.8078108Z RESULT - Sync stewardship-engine-services-client:2.2 = {"message":"In order to sync to Maven Central your package must be included in the JCenter repository"}
2020-09-13T11:42:05.9249371Z RESULT - Sync stewardship-engine-services-spring:2.2 = {"message":"In order to sync to Maven Central your package must be included in the JCenter repository"}

These are similar to the analytics modeling client - there is no implementation yet - nor has there been for multiple releases. -> no action needed (#3330)

2020-09-13T11:59:26.3756192Z RESULT - Sync subject-area-fvt:2.2 = {"status":"Validation Failed","messages":"[Missing: no javadoc jar found in folder '/org/odpi/egeria/subject-area-fvt/2.2', Dropping existing partial staging repository.]"}

^ test code only, though should have been fixed in #3441 . On checking it seems as if we still don't have javadoc. Therefore will open this issue. However as with 2.1 I don't think this is critical to what is published as it is very unlikely to be consumed as an artifact from maven central, so will aim to fix for 2.3

[planetf1]

Will run the pipeline one more time to try to address the conformance test omission, but as i don't believe it's a blocking issue, in parallel will create the github release/notes.

[planetf1]

this is complete