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 3.13 #6988

Closed
29 of 31 tasks
planetf1 opened this issue Oct 10, 2022 · 9 comments
Closed
29 of 31 tasks

Release 3.13 #6988

planetf1 opened this issue Oct 10, 2022 · 9 comments
Assignees
@planetf1 @lpalashevski
Labels
release Work to create a new releae

Comments

@planetf1
Copy link
Member

planetf1 commented Oct 10, 2022 •
edited by 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 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 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

Get Ready for next release

  • Open Release Issue for next release
@planetf1 planetf1 added the release Work to create a new releae label Oct 10, 2022
@planetf1 planetf1 self-assigned this Oct 10, 2022
@planetf1
Copy link
Member Author

RELEASE NOTES

As of this release, the release notes will be written by date, ie
'November 2022' which will then list all the major updates done during the prior month - ie the development for Egeria 3.13, but also updates to UIs, connectors, docs, community.

cc: @mandy-chessell

@planetf1
Copy link
Member Author

Planning to BRANCH for this on ~31 October. (cc: @lpalashevski )

@lpalashevski lpalashevski pinned this issue Oct 26, 2022
@lpalashevski
Copy link
Contributor

@planetf1 based on the security call agreement, can you approve #7003 ?
This change is to be included in the release and I prefer to do it before branching out.

@planetf1
Copy link
Member Author

@lpalashevski have added comment

@mandy-chessell
Copy link
Contributor

@planetf1 @lpalashevski Here is the monthly newsletter https://egeria-project.org/release-notes/october-2022/
this is the current state of the 3.13 release notes: https://egeria-project.org/release-notes/next/.

I suggest continue to have a page for each Egeria Core release listing the updates and fixes - and then link to it from the monthly newsletter. WE plan to review it on the community call this week.

@planetf1
Copy link
Member Author

planetf1 commented Nov 2, 2022

As we have the meeting shortly, I generated a list of PRs that we have included in 3.13:

Full Changelog: V3.12...V3.13

@planetf1
Copy link
Member Author

planetf1 commented Nov 2, 2022

Additional reminders of checks needed each release that are not covered in the current docs or checklists but that I've been doing (all now done for 3.13 thanks @lpalashevski ):

  • 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

@lpalashevski
Copy link
Contributor

CTS Results

GraphRepo Run summary:

{
  "testCaseCount": 6104,
  "testPassCount": 6104,
  "testFailedCount": 0,
  "testSkippedCount": 0
}

GraphRepo Profile:

{
  "profile": "Metadata sharing",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Reference copies",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Metadata maintenance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Dynamic types",
  "status": "UNKNOWN_STATUS"
}
{
  "profile": "Graph queries",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Historical search",
  "status": "CONFORMANT_NO_SUPPORT"
}
{
  "profile": "Entity proxies",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Soft-delete and restore",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Undo an update",
  "status": "CONFORMANT_NO_SUPPORT"
}
{
  "profile": "Reidentify instance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Retype instance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Rehome instance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Entity search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Relationship search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Entity advanced search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Relationship advanced search",
  "status": "CONFORMANT_FULL_SUPPORT"
}

InMemory Run summary:

{
  "testCaseCount": 6104,
  "testPassCount": 6104,
  "testFailedCount": 0,
  "testSkippedCount": 0
}

inMemory Profile:

{
  "profile": "Metadata sharing",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Reference copies",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Metadata maintenance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Dynamic types",
  "status": "UNKNOWN_STATUS"
}
{
  "profile": "Graph queries",
  "status": "CONFORMANT_PARTIAL_SUPPORT"
}
{
  "profile": "Historical search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Entity proxies",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Soft-delete and restore",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Undo an update",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Reidentify instance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Retype instance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Rehome instance",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Entity search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Relationship search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Entity advanced search",
  "status": "CONFORMANT_FULL_SUPPORT"
}
{
  "profile": "Relationship advanced search",
  "status": "CONFORMANT_FULL_SUPPORT"
}

@lpalashevski
Copy link
Contributor

lpalashevski commented Nov 22, 2022 •
edited

Closing the issue as the release 3.13 is complete now.
Next release tracked under #7126

@davidradl davidradl unpinned this issue Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@planetf1 planetf1

@lpalashevski lpalashevski

Labels
release Work to create a new releae
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@planetf1 @mandy-chessell @lpalashevski