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

Kairos release v3.1.3 #2827

Closed
32 of 34 tasks
mauromorales opened this issue Aug 28, 2024 · 0 comments
Closed
32 of 34 tasks

Kairos release v3.1.3 #2827

mauromorales opened this issue Aug 28, 2024 · 0 comments
Labels

Comments

@mauromorales
Copy link
Member

mauromorales commented Aug 28, 2024

🗺 What's left for release

🔦 Highlights

Bug fixes

✅ Release Checklist

  • Stage 0 - Finishing Touches
  • Stage 1 - Manual testing
    • How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned
      • Generic hardware install
      • RPi Standard Install (helps validate that partition expansion is working)
        • Manual upgrade
        • Passive booting
        • Recovery booting
        • Manual recovery reset
        • Automatic reset
        • /oem exists
        • k3s is running - the only flavor in which we include k3s is ubuntu 24.04 which is not working
      • Go through any of the known issues https://kairos.io/docs/
  • Stage 3 - Release
    • Tag the release on master
    • Update the release with any known issues
  • Stage 4 - Announcement
    • Merge docs updates for kairos and k3s version updates
    • Create a branch vX.Y.Z on the docs (not tagging), so the new release can be built and displayed on the menu. Ideally open a PR so we can review and add/remove some commits if needed (in case we have documented WIP which is not available on the given release)
    • Blog post announcement - We decided to skip it this time
@mauromorales mauromorales assigned mudler and unassigned mudler Aug 28, 2024
@mauromorales mauromorales added the triage Add this label to issues that should be triaged and prioretized in the next planning call label Aug 28, 2024
@jimmykarily jimmykarily removed the triage Add this label to issues that should be triaged and prioretized in the next planning call label Sep 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

3 participants