[RELEASE] Release 3.9

[planetf1]

Work Plan

Create release 3.9 :

Prior to the release work

• slack post advising of upcoming release & linking to issue
• advance warning in developer/community call
• final agreement to start branch in team call & identification of outstanding issues
• Agree required updates/versions for additional repos including egeria-ui, egeria-reactui, connectors etc

Branching & Correcting versions

• Create branch
• Reassign any issues not being worked on to the next release
• Update version for master (ie x.y-SNAPSHOT > x.y+1-SNAPSHOT)
• Update version for branch (ie x.y-SNAPSHOT -> x.y)

Final updates to the release

• Ensure any remaining fixes are merged into branch (and vice-versa to master)

Generate a release image for testing

• Start release pipeline manually to generate container image

Updating the React UI (as this is part of the notebook test). Note egeria-ui is out of scope other than inclusion of current release

• [N/A] Create branch
• [N/A] Update version in master
• [N/A] Update version in new branch
• [N/A] Ensure new container image is available for testing (there is no distinct release pipeline)

Updating the Helm Charts (egeria-charts repo)

• checker correct container images are on docker.io & quay.io (these are built by the 'merge' build of a release)
• update image versions for helm charts (egeria-charts repo) (using -prerelease for chart version)

Final tests

• Check swagger doc renders (no regressions)
• Verify odpi-egeria-lab chart (pods active/ready)
• Verify egeria-base chart (pods active/ready)
• Check notebooks (config, start, data catalog at a minimum)
• Check polymer UI (only possible to check it runs - no demo scenario for more)
• Check React UI (rex, tex, glossary author)
• CTS - graph
• CTS - inmemory

Final Docs

• Update release notes in egeria-docs

Final build and publish

• Run 'release' pipeline on branch to push candidates to oss.sonatype.org
• 'close' staging repo & Validate artifacts ok (number, structure, validations) on oss.sonatype.org
• Create final github releases for egeria (add link to egeria docs)
• Close repo on oss.sonatype.org (once updated) for egeria, release
• Check 'release' repo on oss.sonatype.org has artifacts
• Update final versions of egeria-charts to release ie x.y
• Publish that release is now shipped via slack #egeria-announce
• Additional posts to social media
• Communicate to other repo owners ie for connectors so that they can be rebuilt/shipped as needed

Additional components

• ReactUI
  • [N/A] Create final github release
• PostGres Connector
  • [N/A] Create branch
  • [N/A] Update version in master
  • [N/A] Update version in new branch of connector, and of prereq egeria artifacts
  • [N/A] Run release action, check sonatype & release
  • [N/A] Create github release

[planetf1]

I would like to propose we branch for the release on Thu 26 May.

[planetf1]

Agreed in face2face meeting AMS that we will do the branch on 26 May

[planetf1]

@davidradl I will do an initial version of our helm charts using the 3.8.1 version of the ecosystem UI.
If you plan to make a 3.9 release, we can update the pre-release charts for testing to use the 3.9.0-rc version when avail. Please let me know which works for you.

[planetf1]

prerelease charts now available for testing:

helm repo update && helm search repo egeria  --devel
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "strimzi" chart repository
...Successfully got an update from the "egeria" chart repository
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
NAME                  	CHART VERSION     	APP VERSION	DESCRIPTION                                       
egeria/egeria-base    	3.9.0-prerelease.0	3.9        	Egeria simple deployment (platform, react UI)     
egeria/egeria-cts     	3.9.0-prerelease.0	3.9        	Egeria Conformance Test Suite deployment to Kub...
egeria/egeria-pts     	3.9.0-prerelease.0	3.9        	Egeria Performance Test Suite deployment to Kub...
egeria/odpi-egeria-lab	3.9.0-prerelease.0	3.9        	Egeria lab environment        

[planetf1]

The following issues were raised during testing:

• [Enhancement] Allow notebooks to be run multiple times egeria-coco-labs#5
• [BUG] Problem registering governance engine / Asset consumer exceptions #6549
• [BUG] Link to admin services incorrect when retrieving registered services #6550
• [BUG] Incorrect link to glossary author view services documentation from swagger UI #6551
• [Regression] CTS failure (3.9) #6552
• [BUG] UI 'lab' fails to find asset egeria-coco-labs#7
• Component status for view services out of sync with code - likely docs error egeria-docs#444
• Dino - cannot retrieve server audit log twice egeria-react-ui#461
• Dino - Indentation levels too small to understand hierarchy egeria-react-ui#462
• Dino - Error retrieving cohort information egeria-react-ui#463
• Repository Explorer - does not adapt to window size sufficiently - key buttons off-screen egeria-react-ui#464
• Repository Explorer - no server selected -> still get search dialog egeria-react-ui#465

However none are critical or known regressions in stable code, so will not impact release

[planetf1]

odpi/egeria-coco-labs#7 was also recently opened - the ui-lab fails to locate assets due to being in wrong zone - but it's likely this has been there in previous releases as this lab needs more elaboration. In addition the UI code level in the charts is back at 3.2.0 since the code is being refactored, so will leave as-is for the release

[planetf1]

First cts test run (inmemory) has failed

        "testFailedCount": 1,

.....

                            "errorMessage": "CTS test repository-entity-reference-copy-lifecycle caught exception EntityNotKnownException from method getEntityDetail whilst trying to retrieve an entity of type APISchemaType.  Exception message was : OMRS-REPOSITORY-404-002 The entity identified with guid 3709ed6f-01c7-4901-bf6f-cdc8cba05334 passed on the getEntityDetail call is not known to the open metadata repository tut.  Method was invoked with parameters: entityGUID : 3709ed6f-01c7-4901-bf6f-cdc8cba05334",
                            "exceptionClassName": "java.lang.Exception"
                        },

See #6552 for further investigation

[planetf1]

CTS - graph passes successfully (results will be posted below)
(And #6549 is also fine with graph repo)

Both #6549 and #6552 may relate to a common cause - regression in the in-memory connector. Or timing ....

[planetf1]

@mandy-chessell ^^ let's discuss early next week

[planetf1]

Initial release notes for 3.9 added. Any additions please submit a PR on egeria-docs

[planetf1]

Agreed in team call 2021-05-31 :

• Add notes on the cts, cohort registration [BUG] Possible cohort initialization issue (timing) #6353, discovery issues (at a minimum) to the release notes
• Continue to ship the release
• Investigate these three issues further in the next week

[planetf1]

Will plan to do a bigger blog/announce for the 3.10 release to round-up the first part of the year's content

[planetf1]

Egeria dev projects updated - odpi/egeria-dev-projects#18
Issue template updated to add ref to dev projects & remove postgres #6553