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 Ionic #1092

Open
azeey opened this issue Dec 5, 2023 · 6 comments
Open

Release Ionic #1092

azeey opened this issue Dec 5, 2023 · 6 comments
Assignees

Comments

@azeey
Copy link
Contributor

azeey commented Dec 5, 2023

Timeline

Current timeline

  • Feature freeze: 2024/07/26 (Friday)
  • Code freeze: 2024/08/28 (Wednesday)
  • Tutorial party: 2024/08/29 (Thursday) ~ 2024/09/13 (Friday)
  • Internal QA: 2024/09/16 (Monday) - 2024/09/20 (Friday)
  • Community meeting: 2024/09/25 (Wednesday)
  • Announcement: 2024/09/30 (Monday)

During development

Feature freeze

Code freeze

Release day

Post-release

  • Pull requests previously targeted at main:
    • Bug fixes:
      • Retarget to the new stable branch.
      • Label with beta
      • They can be merged until code freeze.
    • Backwards-compatible features, either:
      • Retarget them to the new stable branch (but they can only be merged after the stable release), or
      • Keep targeting main and backport after the stable release.
    • Breaking features:
      • Keep targeting main (i.e. they will be delayed until the next major release)
  • Bump all main branches to the next major version (X.0.0~pre1)
    • Source code (example)
    • Add files to gazebodistro (example)
    • Add aliases to homebrew-simulation (example)
    • Create new -release repositories (use this script)
    • Enable nightlies for all main branches on gzdev (example)
    • Execute the tick-tock's "tock" for deprecations (example)
  • Enable Jenkins CI for new stable branches (example)
  • Remove pre-release for release branches on gzdev (example)

Status tracker

Repo Version Release Branch Feature frozen Synced with previous versions? Prerelease? Code Frozen Stable release? Open PRs Pending dep release
gz-cmake gz-cmake4 PRs
gz-tools gz-tools2 PRs
gz-utils gz-utils3 PRs
gz-math gz-math8 PRs
gz-plugin gz-plugin3 PRs
gz-common gz-common6 PRs
gz-msgs gz-msgs11 PRs
sdformat sdf15 PRs
gz-fuel-tools gz-fuel-tools10 PRs
gz-physics gz-physics8 PRs
gz-rendering gz-rendering9 PRs
gz-transport gz-transport14 PRs
gz-gui gz-gui9 PRs
gz-sensors gz-sensors9 PRs
gz-sim gz-sim9 PRs
gz-launch gz-launch8 PRs
gz-ionic main PRs
ros_gz rolling PRs

Track stable release of metapackage gz-ionic.

  • ⌛ TODO
  • 🟡 waiting in the buildfarm
  • 🟢 in the repo
  • 🔴 requires action
  • ⚫ no release

Linux

  • Ubuntu:
    • 🟢 Noble/amd64
    • 🟢 Noble/arm64

MacOSX

Windows

@azeey
Copy link
Contributor Author

azeey commented Aug 21, 2024

For maintainers, here's the list of steps to create a stable branch for each library that doesn't already have one for the release. (Note, please monitor this post as the steps might need to be updated)

  • <library name>:
    • Create a changelog PR (example)
    • New branch button on branches page (example). Make sure to set the Source to main.
    • Enable CI for stable branches (example):
    • Update gazebodistro [(example)[https://github.com/Use stable branch for gz-cmake4 gazebodistro#165])). Use script to update all dependencies:
    • Update homebrew (example)):
    • Run the Jenkins DSL generation job
    • Create a small PR targetting the stable branch. This could be used to update build status badges (example). Don't skip this; it is important for the next step:
    • Update branch protections. Remember to include the abi-checker.
    • Make a pre-release. Skip merging the homebrew PR. We want to keep formulas building from source until code freeze to match Ubuntu nightlies and windows

@jennuine
Copy link
Contributor

jennuine commented Aug 23, 2024

@traversaro
Copy link

Windows

* **Conda-forge** (community effort)
  
  *

The gz-sim9 and gz-launch8 is now available on conda-forge, and according to my preliminary tests they are working fine (at least without any additional regression on top of known Windows issues).

@azeey
Copy link
Contributor Author

azeey commented Oct 2, 2024

Awesome. Thanks @traversaro!!

@scpeters
Copy link
Contributor

scpeters commented Oct 2, 2024

I opened the following ticket to remind us to add the new SDFormat spec version to http://sdformat.org/spec

we should consider adding this to the collection release issue template as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants