Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[RELEASE]Release 4 #7553

Closed
33 tasks done
planetf1 opened this issue Mar 22, 2023 · 8 comments
Closed
33 tasks done

[RELEASE]Release 4 #7553

planetf1 opened this issue Mar 22, 2023 · 8 comments
Assignees
@planetf1
Labels
release Work to create a new releae

Comments

@planetf1
Copy link
Member

planetf1 commented Mar 22, 2023 •
edited
Loading

Work Plan

Create release 4.0 :
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 planetf1 added the release Work to create a new releae label Mar 22, 2023
@planetf1 planetf1 self-assigned this Mar 22, 2023
@planetf1
Copy link
Member Author

Opening up issue to track tasks to complete Egeria 4 release.

We've discussed this over many months.

The intent has been to branch this week - I propose that final discussion for this week's developer call

@planetf1
Copy link
Member Author

Agreed in dev call today that we can go ahead and branch once

We are also waiting on a fix for

planetf1 added a commit to planetf1/egeria that referenced this issue Mar 23, 2023
@planetf1
odpi#7553 Update version to 4.0
b7948a8 
Signed-off-by: Nigel Jones <[email protected]>
planetf1 added a commit to planetf1/egeria that referenced this issue Mar 23, 2023
@planetf1
odpi#7553 Update version to 4.1-SNAPSHOT
c2557d3 
Signed-off-by: Nigel Jones <[email protected]>
planetf1 added a commit to planetf1/egeria that referenced this issue Mar 23, 2023
@planetf1
odpi#7553 resolved missing dependencies causing build warnings
e76a902 
Signed-off-by: Nigel Jones <[email protected]>
planetf1 added a commit to planetf1/egeria that referenced this issue Mar 23, 2023
@planetf1
odpi#7553 resolved missing dependencies causing build warnings
2833cda 
Signed-off-by: Nigel Jones <[email protected]>
@planetf1
Copy link
Member Author

Update

Publishing to Sonatype nexus (oss.sonatype.org) :

  • Our bom is going into a seperate staging repo to the other components (threading?) - may not be a problem
  • Every artifact is reporting it is not signed with Missing Signature: '/org/odpi/egeria/database-integrator-api/4.0/database-integrator-api-4.0-javadoc.jar.asc' does not exist for 'database-integrator-api-4.0-javadoc.jar'.
    - BOM is also failing with Invalid POM: /org/odpi/egeria/egeria/4.0/egeria-4.0.pom: Project name missing
    - BOM is also failing with Requires one-of SHA-1: /org/odpi/egeria/egeria/4.0/egeria-4.0.pom.sha1, MD5: /org/odpi/egeria/egeria/4.0/egeria-4.0.pom.md5, SHA-256: /org/odpi/egeria/egeria/4.0/egeria-4.0.pom.sha256, SHA-512: /org/odpi/egeria/egeria/4.0/egeria-4.0.pom.sha512

@planetf1
Copy link
Member Author

Release pipeline now tested & problems fixed. Artifacts upload to staging repository on oss.sonatype.org and validate clean.

Awaiting final fix, and testing to do.

@planetf1
Copy link
Member Author

planetf1 commented Mar 26, 2023 •
edited
Loading

Update of outstanding issues:

The base is now looking much better, and the pipelines are working well.
Unfortunately, interacting with it is harder ... ;-) - these are 'regressions':

There has been a lot of discussion around k8s & memory resources, but this does not appear to be a regression, rather better testing/understanding especially making use of the CIM model import.

@planetf1
Copy link
Member Author

planetf1 commented Mar 28, 2023 •
edited
Loading

Current status: Waiting for UI fix (cannot login to business ui)

@planetf1
Copy link
Member Author

Business UI now deploys correctly, and simple testing is successful (asset search, view lineage, login) albeit with a number of issues found in the UI. They will be addressed through the issue, and potentially release notes

With all the required fixes in, I am now going to progress to creating the final release for egeria 4.0.
I’ve updated release notes, and will add a few more entries including around the business UI where there are some caveats

The charts will follow asap (just a final release of the egeria-react-ui
to increment the dependency for. Purely a version bump, testing is good)

planetf1 added a commit to planetf1/egeria-react-ui that referenced this issue Mar 29, 2023
@planetf1
odpi/egeria#7553 Increment version to 3.10.0 to align with Egeria 4 r…
d0586d7 
…elease

Signed-off-by: Nigel Jones <[email protected]>
@planetf1 planetf1 mentioned this issue Mar 29, 2023
Closed
planetf1 added a commit to planetf1/egeria-charts that referenced this issue Mar 29, 2023
@planetf1
odpi/egeria#7553 Pin notebook version for release
0b01539 
Signed-off-by: Nigel Jones <[email protected]>
@planetf1
Copy link
Member Author

release 4 is now out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@planetf1 planetf1

Labels
release Work to create a new releae
Projects
No open projects
Egeria V4.0 Planning
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@planetf1