-
Notifications
You must be signed in to change notification settings - Fork 9
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
Packaging and CI for Jammy #566
Comments
This was referenced Nov 19, 2021
We should also look into Debian Bullseye |
scpeters
added a commit
to gazebosim/gz-plugin
that referenced
this issue
Feb 15, 2022
Part of gazebo-tooling/release-tools#566. Signed-off-by: Steve Peters <[email protected]>
This was referenced Feb 15, 2022
This was referenced Feb 25, 2022
chapulina
pushed a commit
to gazebosim/gz-plugin
that referenced
this issue
Mar 1, 2022
Part of gazebo-tooling/release-tools#566. Signed-off-by: Steve Peters <[email protected]>
8 tasks
This was referenced Mar 4, 2022
This was referenced Mar 5, 2022
7 tasks
Closed
This was referenced Mar 22, 2022
8 tasks
This was referenced Apr 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ubuntu Jammy isn't officially released yet, and I don't know what would be the best time to setup CI for it. Considering we're trying to push all of Fortress upstream, I imagine we should make sure Fortress works properly on Jammy before its official release.
We'll only be supporting Jammy from Fortress, as documented in gazebo-tooling/action-gz-ci#41
This issue is to track:
Enabling Jammy releases for all of Fortress and Garden (i.e. adding jammy to the
-release
repos)Packaging all Fortress (stable) and Garden (nightly) for Jammy
Enabling GitHub actions CI for Jammy on all Fortress and Garden branches (using Jammy branch action-gz-ci#41)
@j-rivero , let me know if I forgot anything.
The text was updated successfully, but these errors were encountered: