🏁 Citadel EOL

[azeey]

Part of #1223

DO NOT MERGE UNTIL Jan 1, 2025

[caguero]

Remove this example line? https://github.com/gazebo-tooling/release-tools/blob/master/bloom/ros_gz/README.md?plain=1#L18

Add the Foxy - Citadel combination to the List of EOL releases section? https://github.com/gazebo-tooling/release-tools/blob/master/bloom/ros_gz/README.md?plain=1#L37

Remove the citadel block from _dashboard_lib.sh? https://github.com/gazebo-tooling/release-tools/blob/master/terminal-dashboard/_dashboard_lib.sh#L9-L26

Remove the citadel block from table.bash? https://github.com/gazebo-tooling/release-tools/blob/master/terminal-dashboard/table.bash

[azeey]

Remove this example line? https://github.com/gazebo-tooling/release-tools/blob/master/bloom/ros_gz/README.md?plain=1#L18

I think this can be left as is, since it's just an example of officially supported ROS/Gazebo pairings. Even though Citadel is EOL, the fact that it was paired with ROS 2 Foxy has not changed.

Add the Foxy - Citadel combination to the List of EOL releases section? https://github.com/gazebo-tooling/release-tools/blob/master/bloom/ros_gz/README.md?plain=1#L37

This list is for unofficial Gazebo/ROS pairings, e.g. Harmonic/Humble while the official one is Fortress/Humble. Since Citadel never had an unofficial pairing, I don't think there's anything to do here.

Remove the citadel block from _dashboard_lib.sh? https://github.com/gazebo-tooling/release-tools/blob/master/terminal-dashboard/_dashboard_lib.sh#L9-L26
Remove the citadel block from table.bash? https://github.com/gazebo-tooling/release-tools/blob/master/terminal-dashboard/table.bash

Is there a reason to do so? Even if it's EOL, I think it's nice to have the ability to generate the citadel dashboard. The table command takes the distro as an argument, so users are not forced to generate Citadel's table if they don't want to.

[j-rivero]

Remove this example line? https://github.com/gazebo-tooling/release-tools/blob/master/bloom/ros_gz/README.md?plain=1#L18

I think this can be left as is, since it's just an example of officially supported ROS/Gazebo pairings. Even though Citadel is EOL, the fact that it was paired with ROS 2 Foxy has not changed.

Not having a strong position here but I usually clean up most references to EOL distributions just to reduce the noise for the people reading the options. I'm fine with it to stay.

Add the Foxy - Citadel combination to the List of EOL releases section? https://github.com/gazebo-tooling/release-tools/blob/master/bloom/ros_gz/README.md?plain=1#L37
This list is for unofficial Gazebo/ROS pairings, e.g. Harmonic/Humble while the official one is Fortress/Humble. Since Citadel never had an unofficial pairing, I don't think there's anything to do here.

👍

Remove the citadel block from _dashboard_lib.sh? https://github.com/gazebo-tooling/release-tools/blob/master/terminal-dashboard/_dashboard_lib.sh#L9-L26

Remove the citadel block from table.bash? https://github.com/gazebo-tooling/release-tools/blob/master/terminal-dashboard/table.bash
Is there a reason to do so? Even if it's EOL, I think it's nice to have the ability to generate the citadel dashboard. The table command takes the distro as an argument, so users are not forced to generate Citadel's table if they don't want to.

Same than in first point, not an strong argument but we probably remove previous versions from the table to reduce the number of lines of code that the dashboard is hosting. I'm also fine with it to stay for some months just in case someone needs it a some point.