[RELEASE] Release 3.15

[lpalashevski]

Work Plan

Create release x.y :
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 main (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 main)

Pre-release security check

• Execute manual sonatype lift scan on release branch from and communicate findings (needs more formal process in future)

Generate a release image for testing

• Start Release pipeline manually to generate container image

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)
  • check/update the strimzi chart versions
  • check/update the kafka version used for the strimzi CR in each chart
  • check/update the current jupyter lab version & generate a new docker container in egeria-jupyter
  • update the jupyter lab version in the charts

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 and run UI lab)
• Check React UI (rex, tex, glossary author). Some of the steps descibed here
• CTS - graph
• CTS - inmemory

Final Docs

• Update release notes in egeria-docs

Final build and publish

• Check if the Release pipeline rlease artifacts are shown in staging repo in OSS Repository Manager
• '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
• Post on egeria-annouce mailing list
• Additional posts to social media
• Communicate to other repo owners ie for connectors so that they can be rebuilt/shipped as needed (Egeria Dev Projects etc.)

Get Ready for next release

• Open Release Issue for next release

[planetf1]

We typically target the end of the month. I think we should aim for end January, though we need to ensure graph CTS is fixed #7148. Can discuss on next call

[planetf1]

Update - on the tsc/dev call last week we discussed branching early this week as long as CTS fixes are included.
CTS ran clean following PR #7328 so we will shortly branch

[planetf1]

Charts deploy fine. Base chart configures successfully. Initial tests with the notebooks look good ie data catalog.
Presentation server working correctly for dino, tex, rex.

@lpalashevski For some reason my config isn't working with the UI. I'll look tomorrow, but perhaps you might be able to check it looks ok? (the charts are up at prerelease levels)

CTS running across all 3 connectors

[planetf1]

CTS Results

InMemory

              Metadata sharing MANDATORY_PROFILE    CONFORMANT_FULL_SUPPORT [  71657 /      0 ]
              Reference copies  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   8528 /      0 ]
          Metadata maintenance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  14063 /      0 ]
                 Dynamic types  OPTIONAL_PROFILE             UNKNOWN_STATUS [      0 /      0 ]
                 Graph queries  OPTIONAL_PROFILE CONFORMANT_PARTIAL_SUPPORT [    186 /      0 ]
             Historical search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [    530 /      0 ]
                Entity proxies  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2759 /      0 ]
       Soft-delete and restore  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2592 /      0 ]
                Undo an update  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   1218 /      0 ]
           Reidentify instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2650 /      0 ]
               Retype instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  16365 /      0 ]
               Rehome instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   1590 /      0 ]
                 Entity search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  60712 /      0 ]
           Relationship search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   8229 /      0 ]
        Entity advanced search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  40512 /      0 ]
  Relationship advanced search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   9264 /      0 ]

PASS [240855/0]

Graph

              Metadata sharing MANDATORY_PROFILE    CONFORMANT_FULL_SUPPORT [  71657 /      0 ]
              Reference copies  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   8528 /      0 ]
          Metadata maintenance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  14126 /      0 ]
                 Dynamic types  OPTIONAL_PROFILE             UNKNOWN_STATUS [      0 /      0 ]
                 Graph queries  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [    528 /      0 ]
             Historical search  OPTIONAL_PROFILE      CONFORMANT_NO_SUPPORT [    530 /      0 ]
                Entity proxies  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2759 /      0 ]
       Soft-delete and restore  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2592 /      0 ]
                Undo an update  OPTIONAL_PROFILE      CONFORMANT_NO_SUPPORT [    406 /      0 ]
           Reidentify instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2650 /      0 ]
               Retype instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  16365 /      0 ]
               Rehome instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   1590 /      0 ]
                 Entity search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  62878 /      0 ]
           Relationship search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   8256 /      0 ]
        Entity advanced search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  44800 /      0 ]
  Relationship advanced search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   9312 /      0 ]

PASS [246977/0]

xtdb

This is provided for info only -- and does not gate the release

              Metadata sharing MANDATORY_PROFILE    CONFORMANT_FULL_SUPPORT [  71657 /      0 ]
              Reference copies  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   8528 /      0 ]
          Metadata maintenance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  14063 /      0 ]
                 Dynamic types  OPTIONAL_PROFILE             UNKNOWN_STATUS [      0 /      0 ]
                 Graph queries  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [    528 /      0 ]
             Historical search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [    530 /      0 ]
                Entity proxies  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2759 /      0 ]
       Soft-delete and restore  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2592 /      0 ]
                Undo an update  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   1218 /      0 ]
           Reidentify instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   2650 /      0 ]
               Retype instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  16365 /      0 ]
               Rehome instance  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   1590 /      0 ]
                 Entity search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  60728 /      0 ]
           Relationship search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   8229 /      0 ]
        Entity advanced search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [  40496 /      0 ]
  Relationship advanced search  OPTIONAL_PROFILE    CONFORMANT_FULL_SUPPORT [   9264 /      0 ]

PASS [241197/0]

ie CTS PASSES

[planetf1]

I've now checked the business UI including lineage, and it appears to work as usual - on rancher desktop. I couldn't get connected to the ports correctly on openshift, but I think that is not a regression, certainly not for last few releases, and we should revisit when we move to the new UI. Ok @lpalashevski

If anyone wants to do any extra checks/tests please say so. Otherwise I will propose to go ahead on the developer call tomorrow

[planetf1]

Sonatype scan for 3.15 started -> https://lift.sonatype.com/results/github.com/odpi/egeria/01GR67QFPC98J2JJ5CD5D0TXFY

[planetf1]

testing is complete. will progress with release

[planetf1]

All complete

• release has been shipped via github, announced, maven artifacts released charts updated

Not creating a v4 release issue just yet as we have an entire project, and variety of v4 issues that may need some consolidation.