2024-07 Release

[mkhansenbot]

Based on last release flow: #153
Before the release window

• Determine the release tag of the form rosdist-year.month.point, for example humble-2024.01.0
• Open a new issue with a title of the form "year-month Release", for example "2024-01 Release"
• Create a milestone that matches the release tag in each repo under the Space ROS organization
• Create a new view in the Space ROS Project filtered by milestone

During the release window

• Tag issues intended for the release with the correct milestone
• Update issue status on the project view for the release

At the end of the release window

• Create release/distro branches on docker, demos, simulation, docs, and process_sarif.
• Update the .repos files to the new versions for the new distro sync.
  Re-run the tests, creating issues for any that failed (Test flow per Define release acceptance tests #102 (comment))
• Build basic space-ros image following instructions in https://github.com/space-ros/docker/tree/main/spaceros.
• Boot into image, run basic commands such as ros2, ikos, just to check that they are installed.
• Build moveit2 image following instructions in https://github.com/space-ros/docker/tree/main/moveit2.
• Build navigation2 image following instructions in https://github.com/space-ros/docker/tree/main/navigation2.
• Build space_robots image following instructions in https://github.com/space-ros/docker/tree/main/space_robots.
• Boot space_robots image. Start Mars rover demo, check that the demo launches, and it's possible to send commands to the rover.
• Start canadarm demo, check that the demo launches, and it's possible to send commands to the robotic arm following instructions in https://github.com/space-ros/demos/tree/main/canadarm
• Boot the Nav2 image and run following the instructions in https://github.com/space-ros/docker/tree/main/nav2_demo#run-the-mars-rover-demo-with-nav2-and-slam-toolbox. Check that the robot is localizing.
• Docker images are already built but only tagged latest, must tag release as release name.

Finish up docs and start next release window

• Add announcements to Website, Docs, and Discourse
• Create next release milestone and tracking issue

After release window

• Open issues based on release experience
• Document lessons learned