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 0.3.0 #494

Closed
24 tasks done
AlfredoG87 opened this issue Jan 14, 2025 · 0 comments
Closed
24 tasks done

Release 0.3.0 #494

AlfredoG87 opened this issue Jan 14, 2025 · 0 comments
Assignees
@mattp-swirldslabs @AlfredoG87
Labels
Release Issues tied to release management functions
Milestone
0.3.0

Comments

@AlfredoG87
Copy link
Contributor

AlfredoG87 commented Jan 14, 2025 •
edited
Loading

Problem

We need to release 0.3.0 version

Solution

Please refer to documentation on release details.

  • Create the next Milestone 0.4.0 if it does not already exists, define the dates (release cadence) every sprint
  • Ensure all tickets related to Milestone 0.3.0 are completed. (except this one "release"). Is possible to move some to the next Milestone if deemed necessary.
  • Ensure that all PRs have appropriate labels, milestone set and assignes.
  • Trigger GHA Release Automation WF with v0.3.0-rc1 using main branch. (this will kick-off the automation release process)
    • Verify TAG v0.3.0-rc1 was created in Block Node Tags
    • Verify Release for v0.3.0-rc1 was created on Releases. Publish as a Pre-Release
    • Verify a Version Bump PR was created fo 0.4.0-SNAPSHOT was created against main branch
    • Review, Approve and Merge the above PR.
    • Verify a container image was created on GHCR packages of Block-Node for v0.3.0-rc1 version
    • Verify a new Helm Chart was created on GH-Pages of BlockNode for v0.3.0-rc1 version
    • Verify a new image was created with the version for the simulator
    • Verify a new Chart was created for the simulator
    • Test Deployment using created helm chart, verify is using the v0.3.0-rc1 version.

If All tests pass on v0.3.0-rc1 version proceed with GA version.

  • Trigger GHA Release Automation WF with v0.3.0 version using release branch: release/0.2
    • Verify TAG v0.3.0 was created in Block Node Tags
    • Verify Draft Release for v0.3.0 was created on Releases. Do not publish yet.
    • Verify a container image was created on GHCR packages of Block-Node for v0.3.0 version
    • Verify a new Helm Chart was created on GH-Pages of BlockNode for v0.3.0 version
    • Test Deployment using created helm chart, verify is using the v0.3.0 version.
  • Publish GA Release Version
    • Generate Release Notes using GH Template and Button.
    • Add a Summary to the Generated Notes that captures the highlights of the release
    • Publish Release as a latest version.
  • Announce the release on Slack Channel of Block-Node.

Alternatives

No response
@AlfredoG87 AlfredoG87 added the Release Issues tied to release management functions label Jan 14, 2025
@AlfredoG87 AlfredoG87 added this to the 0.3.0 milestone Jan 14, 2025
@AlfredoG87 AlfredoG87 mentioned this issue Jan 14, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mattp-swirldslabs mattp-swirldslabs

@AlfredoG87 AlfredoG87

Labels
Release Issues tied to release management functions
Projects
None yet
Milestone
0.3.0
Development

No branches or pull requests
2 participants
@mattp-swirldslabs @AlfredoG87