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.

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

[RELEASE] Release 3.5 #6140

Closed
29 of 30 tasks
planetf1 opened this issue Jan 24, 2022 · 12 comments
Closed
29 of 30 tasks

[RELEASE] Release 3.5 #6140

planetf1 opened this issue Jan 24, 2022 · 12 comments
Assignees
Labels
release Work to create a new releae
Milestone

Comments

@planetf1
Copy link
Member

planetf1 commented Jan 24, 2022

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 docker 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 docker image is available for testing (there is no distinct release pipeline)

Updating the Helm Charts (egeria-charts repo)

  • checker correct docker images are on dockerhub (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 planetf1 added the release Work to create a new releae label Jan 24, 2022
@planetf1 planetf1 self-assigned this Jan 24, 2022
@planetf1
Copy link
Member Author

I will propose we create the release (branch) on Thu 27 Jan, but we will review on the developer
call tomorrow 2022-01-24

@planetf1
Copy link
Member Author

Agreed on call 2022-01-24

  • target branch for Thu
  • Desirable to get some UI function finished. Will review Thu. If it's likely to extent will test/use code as is for release, optional extra UI release after that

@planetf1 planetf1 added this to the 3.5 milestone Jan 25, 2022
@planetf1 planetf1 added triage New bug/issue which needs checking & assigning and removed triage New bug/issue which needs checking & assigning labels Jan 25, 2022
@planetf1
Copy link
Member Author

@sarbull @lpalashevski

Currently the last release of egeria-ui was end/November, coinciding with Egeria 3.4
Do you plan any new version to coincide with the Egeria 3.5 release. Otherwise I will assume we package the same version of the UI in the helm chart as before 3.4.0

@lpalashevski
Copy link
Contributor

Yes lets keep the same. There are no functional changes going on at the moment in the polymer version. The ongoing activities are related to migration to React (in the same codebase).

@planetf1
Copy link
Member Author

@lpalashevski Ok thanks for confirming, will stick with the same polymer ui version.

@planetf1
Copy link
Member Author

planetf1 commented Jan 27, 2022

planetf1 added a commit to planetf1/egeria that referenced this issue Jan 27, 2022
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue Jan 27, 2022
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit to planetf1/egeria that referenced this issue Jan 27, 2022
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
planetf1 added a commit that referenced this issue Jan 27, 2022
#6140 update version to 3.6-SNAPSHOT
@planetf1
Copy link
Member Author

Opened #6158 to address some broken links in the swagger UI docs (but not regression)
Also noted odpi/egeria-react-ui#326 (known issue - work in progress)

@planetf1
Copy link
Member Author

inmemory CTS complete:

	name	description	profilePriority	conformanceStatus
0	Metadata sharing	The technology under test is able to share met...	MANDATORY_PROFILE	CONFORMANT_FULL_SUPPORT
1	Reference copies	The technology under test is able to save, loc...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
2	Metadata maintenance	The technology under test supports requests to...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
3	Dynamic types	The technology under test supports changes to ...	OPTIONAL_PROFILE	UNKNOWN_STATUS
4	Graph queries	The technology under test supports graph-like ...	OPTIONAL_PROFILE	CONFORMANT_PARTIAL_SUPPORT
5	Historical search	The technology under test supports search for ...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
6	Entity proxies	The technology under test is able to store stu...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
7	Soft-delete and restore	The technology under test allows an instance t...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
8	Undo an update	The technology under test is able to restore a...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
9	Reidentify instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
10	Retype instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
11	Rehome instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
12	Entity search	The technology under test supports the ability...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
13	Relationship search	The technology under test supports the ability...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
14	Entity advanced search	The technology under test supports the use of ...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
        "testCaseCount": 5612,
        "testFailedCount": 0,
        "testPassCount": 5612,

@planetf1
Copy link
Member Author

Graph CTS complete:

	name	description	profilePriority	conformanceStatus
0	Metadata sharing	The technology under test is able to share met...	MANDATORY_PROFILE	CONFORMANT_FULL_SUPPORT
1	Reference copies	The technology under test is able to save, loc...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
2	Metadata maintenance	The technology under test supports requests to...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
3	Dynamic types	The technology under test supports changes to ...	OPTIONAL_PROFILE	UNKNOWN_STATUS
4	Graph queries	The technology under test supports graph-like ...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
5	Historical search	The technology under test supports search for ...	OPTIONAL_PROFILE	CONFORMANT_NO_SUPPORT
6	Entity proxies	The technology under test is able to store stu...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
7	Soft-delete and restore	The technology under test allows an instance t...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
8	Undo an update	The technology under test is able to restore a...	OPTIONAL_PROFILE	CONFORMANT_NO_SUPPORT
9	Reidentify instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
10	Retype instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
11	Rehome instance	The technology under test supports the command...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
12	Entity search	The technology under test supports the ability...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
13	Relationship search	The technology under test supports the ability...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
14	Entity advanced search	The technology under test supports the use of ...	OPTIONAL_PROFILE	CONFORMANT_FULL_SUPPORT
        "testCaseCount": 5612,
        "testFailedCount": 0,
        "testPassCount": 5612,

@planetf1
Copy link
Member Author

@wbittles @mandy-chessell I am proposing not to release the Postgres connector as there have been no updates this release cycle. Are you both ok with that?

@mandy-chessell
Copy link
Contributor

@planetf1 yes

@planetf1
Copy link
Member Author

@cmgrote @wbittles FYI in case you wish to make any new release updates to additional connectors. Let me know if you wanted & need any help
@davidradl @lpalashevski Confirming the release is out with ecoui 3.4.0 & genui 3.2.0 - if updates needed before next egeria release, please open issue/PR in the egeria-charts repo

@planetf1 planetf1 closed this as completed Feb 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Work to create a new releae
Projects
None yet
Development

No branches or pull requests

3 participants