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

Prepare for release v1.10 minor release #2275

Open
47 tasks
Rozzii opened this issue Jan 24, 2025 · 2 comments
Open
47 tasks

Prepare for release v1.10 minor release #2275

Rozzii opened this issue Jan 24, 2025 · 2 comments
Assignees
Labels
dependencies Pull requests that update a dependency file kind/ci Categorizes issue or PR as related to CI or testing. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. triage/accepted Indicates an issue is ready to be actively worked on.
Milestone

Comments

@Rozzii
Copy link
Member

Rozzii commented Jan 24, 2025

Here we can track the tasks related to release 1.10
For 1.9 tracker : #2137

Tasks

  • Prepare dev-env to acommodate new release related changes and configurations. Prior art: 1, 2, 3
    • PR:
  • Release Ironic, also check new image is created in quay. Prior art: v26.0.0 release, 27.0.0 release
  • Pin Ironic in BMO. Prior art
  • Pin Ironic in metal3-dev-env. Prior art
  • Uplift CAPI to v1.10.0 in IPAM and CAPM3, also check migration guide: Migration guide for providers . Prior art IPAM, Prior art CAPM3, Prior infra
  • Uplift k8s to 1.33? in CAPM3 repo. Prior art
    • PR:
  • Uplift k8s to 1.33 in metal3-dev-env repo. Prior art
    • PR:
  • Uplift k8s to 1.33 in image building pipeline. Prior art: 1, 2
    • PR:
  • Release IPAM (Make release note PR, also check new image is created in quay).
    • Tag PR:
  • Check if BMO needs release. If so, release BMO (Branch out, add branch protection and required tests, also check new image is created in quay). Prior art
    • Tag PR:
  • Bump IPAM and BMO in CAPM3 in main Prior art
    • PR:
  • Release CAPM3 (Branch out, add branch protection and required tests, also check new image is created in quay).
    • PR:
  • Add/edit JJBs to accommodate new build jobs and PR jobs for new release branches. And remove unsupported releases tests for CAPM3 and IPAM. Prior art
    • PR adding 1.10 jobs:
    • PR removing 1.7 jobs:
  • Add Prow jobs for new release branches in Project-infra repo, also remove unsupported releases tests for CAPM3 and IPAM here too Prior art 1 2 3
    • PR IPAM:
    • PR BMO:
    • PR CAPM3:
    • PR remove 1.7 tests:
    • PR add triggers to other repos prior art
  • Check CI if new releases are tested properly or not
  • Update CAPM3 README.md with the new e2e triggers, on both the release-1.10 and on main. Prior art: 1, 2
    • PR main:
    • PR release-1.10:
  • Update IPAM README.md with the new e2e triggers, on both the release-1.9 and on main. Prior art: 1, 2 3
    • PR release-1.10:
  • Update BMO README.md with the new e2e triggers, on both the release-0.10 (if applicable) and on main. Prior art: 1, 2
    • PR main:
    • PR release-0.10:
  • Add BMO upgrade test for release-0.10 -> main, and update all ironic upgrade tests to use release-0.10, also remove tests for release-0.8 Prior art
    • PR:
  • Update Metal3 book. Prior art: 1, 2, 3
    • PR:
  • Announce the releases

Post-release tasks

Do the following on the main branch after the release is done.

  • Add CAPI v1.10 contract. Prior art 1, 2
    • PR:
  • Update clusterctl tests to accommodate new releases. prior art 1, 2, 3
    • PR:
@metal3-io-bot metal3-io-bot added the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jan 24, 2025
@Rozzii
Copy link
Member Author

Rozzii commented Jan 24, 2025

/triage accepted
/kind dependency

@metal3-io-bot metal3-io-bot added the triage/accepted Indicates an issue is ready to be actively worked on. label Jan 24, 2025
@metal3-io-bot
Copy link
Contributor

@Rozzii: The label(s) kind/dependency cannot be applied, because the repository doesn't have them.

In response to this:

/triage accepted
/kind dependency

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@metal3-io-bot metal3-io-bot removed the needs-triage Indicates an issue lacks a `triage/foo` label and requires one. label Jan 24, 2025
@Rozzii Rozzii added release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. kind/ci Categorizes issue or PR as related to CI or testing. dependencies Pull requests that update a dependency file labels Jan 24, 2025
@Rozzii Rozzii moved this from Backlog to CAPM3 WIP in Metal3 - Roadmap Jan 24, 2025
@Rozzii Rozzii added this to the CAPM3 - v1.10 milestone Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file kind/ci Categorizes issue or PR as related to CI or testing. release-note-action-required Denotes a PR that introduces potentially breaking changes that require user action. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
Status: CAPM3 WIP
Development

No branches or pull requests

5 participants