• Name of the new release team: libcamera

• Release repositories to add:

  • libcamera
  • camera_ros

• Team members

  • @christianrauch

• Name of the new release team: progtologist

• Release repositories to add:

  • ffmpeg_image_transport
  • There is an existing release repository which should be imported: ffmpeg_image_transport-release

• Team members

  • @progtologist

• Name of the release team: sports

• Release repositories to add:

  • vision_msgs_layers
    • There is no existing release repository
  • soccer_vision_2d_layers
    • There is no existing release repository

• Name of the release team: fictionlab

• Release repositories to add:

  • aruco_opencv

Updates to apriltag membership.

I would like to release the ROS2 packages apriltag_msgs and apriltag_ros and are therefore requesting to join the apriltag release team.

New team members

• @christianrauch
• @christian-rauch

• Name of the release team: universal_robots_team

• Release repositories to add:

  • ur_msgs
    • The existing release repository will still be used for ROS1
  • Universal_Robots_ROS2_Driver

Thank you very much!

Updates to rosbag2 membership.

New team members

• @MichaelOrlov

• Name of the new release team: schunk_svh

• Release repositories to add:

  • schunk_svh_library
  • schunk_svh_ros_driver

• Team members

  • @stefanscherzinger
  • ...

• Name of the new release team: fictionlab

• Release repositories to add:

  • leo_common
    • There is an existing release repository which should be imported: https://github.com/fictionlab-gbp/leo_common-ros2-release
  • leo_robot
    • There is an existing release repository which should be imported: https://github.com/fictionlab-gbp/leo_robot-ros2-release
  • leo_desktop
    • There is an existing release repository which should be imported: https://github.com/fictionlab-gbp/leo_desktop-ros2-release

• Team members

  • @bjsowa
  • @szlachcic
  • @Bitterisland6

Updates to pal_robotics membership.

New team members

• @saikishor
• @jordan-palacios
• @lucamarchionni
  You can find our access levels here: https://github.com/pal-robotics/backward_ros/commits/foxy-devel

@nuclearsandwich
Thank you for getting around to creating the release repositories.

Following bloom instructions, it fails to push to the remote release repositories because they are empty:

fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin master

Cannot push to remote release repository.
Hint: If you just typed in your username/password and you have two-factor authentication,see:
  http://wiki.ros.org/bloom/Tutorials/GithubManualAuthorization

It is just a matter of having an empty README.md in the release repository before performing the release, but the suggestion given to git push --set-upstream origin master in the error is misleading. (can't do much about that)

Is it possible to ensure that the release repositories are initialised with a blank README.md when they are created, or should we add that to the instructions for package maintainers?

Updates to rmf membership.

New team members

• @orensbruli

• Name of the new release team: irobot_education

• Release repositories to add:

  • irobot_create_msgs
    • There is an existing release repository which should be imported:
  • create3_sim
    • There is an existing release repository which should be imported:

• Team members

  • @alsora
  • @justinIRBT
  • @shamlian

• Name of the release team: rt_net

• Release repositories to add:

  • raspimouse_ros2_examples
    • There is an existing release repository which should be imported:
  • raspimouse_slam_navigation_ros2
    • There is an existing release repository which should be imported:
  • rt_manipulators_cpp
    • There is an existing release repository which should be imported: https://github.com/rt-net-gbp/rt_manipulators_cpp-release
  • rt_usb_9axisimu_driver
    • There is an existing release repository which should be imported: https://github.com/rt-net-gbp/rt_usb_9axisimu_driver-release
  • crane_plus
    • There is an existing release repository which should be imported: https://github.com/rt-net-gbp/crane_plus-release

• Name of the release team:
  acceleration_wg

• Release repositories to add:

  • adaptive_component-release, for:
    • adaptive_component

Associated PR created: #40

• Name of the release team: 42dot

• Release repositories to add:

  • foros
    • There is an existing release repository which should be imported:

• Name of the new release team: foxglove_bridge_team

• Release repositories to add:

  • foxglove_bridge
    • There is an existing release repository which should be imported

• Team members

  • @amacneil
  • @defunctzombie
  • @jhurliman
  • @jtbandes
  • @achim-k

Updates to membership.

New team members

Link: https://github.com/intel/ros2_object_msgs/blob/master/package.xml
Users: https://github.com/lewisliupub & https://github.com/ChloeWu1

• Name of the release team: mrpt2

• Release repositories to add:

  • mrpt_msgs](https://github.com/mrpt-ros-pkg/mrpt_msgs/tree/ros2)
    • There is an existing release repository which should be imported: https://github.com/mrpt-ros2-pkg-release/mrpt_msgs-release
  • pose_cov_ops
    • (There is NOT any existing ros2 release repository for neither this one, nor the rest)
  • mrpt_slam
  • mrpt_sensors
  • mrpt_navigation

• Name of the new release team: hatchbed

• Release repositories to add:

  • log_view
    • There is an existing release repository which should be imported: https://github.com/hatchbed/log_view-release
  • asyncapi_gencpp
  • rpad
  • rpad_ros
  • param_util

Team Members:

• @malban
• @pjreed

Updates to tooling_wg membership.

New team members

• @MichaelOrlov

• Name of the release team: apriltag

• Release repositories to add:

  • apriltag_msgs
  • apriltag_ros

• Name of the new release team: teamspatzenhirn

• Release repositories to add:

  • rviz_2d_overlay_plugins

• Team members

  • @ottojo https://github.com/teamspatzenhirn/rviz_2d_overlay_plugins/blob/main/rviz_2d_overlay_plugins/package.xml#L10
  • @authaldo https://github.com/teamspatzenhirn/rviz_2d_overlay_plugins/blob/main/rviz_2d_overlay_plugins/package.xml#L11

• Name of the new release team: 42dot

• Release repositories to add:

  • foros
    • There is an existing release repository which should be imported:

• Team members

  • @huchijwk

• Name of the release team: cascade_lifecycle

• Release repositories to add:

  • cascade_lifecycle
    • There is an existing release repository which should be imported: https://github.com/fmrico/cascade_lifecycle-release.git

Buildfarm is failing to access release repos. (I haven't confirmed whether this is specific to release repos on ros2-gbp).

Exact Error message from Rsrc_uJ__rviz_rendering_tests__ubuntu_jammy__source:

16:26:18 # BEGIN SUBSECTION: get sources
16:26:19 Invoking 'git clone --branch debian/ros-rolling-rviz-rendering_9.1.1-3_jammy --depth 1 --no-single-branch https://github.com/ros2-gbp/rviz-release.git /tmp/sourcedeb/source'
16:26:19 Cloning into '/tmp/sourcedeb/source'...
16:26:19 fatal: unable to access 'https://github.com/ros2-gbp/rviz-release.git/': getaddrinfo() thread failed to start
16:26:19 # END SUBSECTION

Other buildfarm failures:

• https://build.ros2.org/view/Rsrc_uJ/job/Rsrc_uJ__rcss3d_agent_msgs__ubuntu_jammy__source/
• https://build.ros2.org/view/Rsrc_uJ/job/Rsrc_uJ__osrf_testing_tools_cpp__ubuntu_jammy__source/
• https://build.ros2.org/view/Rsrc_uJ/job/Rsrc_uJ__microstrain_inertial_driver__ubuntu_jammy__source/

• Sky^2
• Release repositories to add:
  • Robotino_ROS2
    • There is an existing release repository which should be imported: https://github.com/SkyloveQiu/ROS2_Robotino
  • Team members
  • @SkyloveQiu

• Name of the new release team: rt_net

• Release repositories to add:

  • raspimouse_description
    • There is an existing release repository which should be imported:
  • raspimouse2
    • There is an existing release repository which should be imported: https://github.com/rt-net/raspimouse2-release

• Team members

  • @ShotaAk
  • @shu-rt
  • @Tiryoh

The instructions said that an individual's name is ok, but none of the others currently in the repo seem to be. My package/s will be too small to warrant per-package teams either. I've gone with my name anyway as it matches my Github username, but also happy to go with my "brand" articulated_robotics if that is preferred, in the case of future maintainers joining my projects.

• Name of the new release team: josh_newans

• Release repositories to add:

  • twist_stamper
    • There is an existing release repository which should be imported: https://github.com/joshnewans/twist_stamper-release

• Team members

  • @joshnewans Maintainer tag

• Name of the release team: foxglove_bridge_team

• Release repositories to add:

  • foxglove/ros-foxglove-bridge
    * [ ] There is an existing release repository which should be imported

• Name of the new release team: ros_naoqi

• Release repositories to add:

  • libqi
    • There is an existing release repository which should be imported: https://github.com/ros-naoqi/libqi-release
  • libqicore
    • There is an existing release repository which should be imported: https://github.com/ros-naoqi/libqicore-release
  • naoqi_bridge_msgs
    • There is an existing release repository which should be imported: https://github.com/ros-naoqi/naoqi_bridge_msgs-release
  • naoqi_driver
    • There is an existing release repository which should be imported: https://github.com/ros-naoqi/naoqi_driver-release
  • nao_meshes
    • There is an existing release repository which should be imported: https://github.com/ros-naoqi/nao_meshes-release
  • pepper_meshes
    • There is an existing release repository which should be imported: https://github.com/ros-naoqi/pepper_meshes-release

• Team members

  • @mbusy
  • @suryaambrose
  • @Karsten1987
  • @zygopter
  • @mikaelarguedas
  • @nlyubova

Updates to tooling_wg membership.

New team members

• @james-rms (rosbag2_storage_mcap)

• Name of the release team: rqt

• Release repositories to add:

  • ros-visualization/rqt_tf_tree
    • There is an existing release repository which should be imported: ros2-gbp/rqt_tf_tree-release

Currently it turns out to be complicated to release a new version of rqt_tf_tree for humble.
I was told (ros-visualization/rqt_tf_tree#42) that the correct way to talk about permission topics are issues an PRs in this repository as permissions are automatically generated for the ROS2 release repositories.
The problem with missing releases was also already brought up on discourse.
I actually don't know why this specific rqt repository is not part of the list of repositories available to the rqt release maintainers but maybe it is possible to add this now so we can release rqt_tf_tree for new distributions.

• Name of the new release team: myzhar

• Release repositories to add:

  • ldrobot-lidar-ros2
    • There is an existing release repository which should be imported: https://github.com/Myzhar/ldrobot-lidar-ros2/releases

• Team members

  • @myzhar

• Name of the new release team: fortefibre

• Release repositories to add:

  • fluent_rviz
    • There is an existing release repository which should be imported:

• Team members

  • @shouth
  • @HansRobo

• Name of the release team: universal_robots_team

• Release repositories to add:

  • ur_description

• Name of the release team: Sorry, I don’t know what teams are there.

• Release repositories to add:

  • vrpn
    • There is an existing release repository which should be imported: vrpn-release

Hi team, this is my first time trying to release a third party package. This is preparing for migrating the ROS1 package vrpn_client_ros. I was following the documentation here but please let me know if there are better places for me to host this release repo.

• Name of the new release team: dynamixel_community

• Release repositories to add:

  • dynamixel_hardware

• Team members

  • @youtalk
  • @ijnek
  • @ROBOTIS-Will

• Name of the release team: ijnek

• Release repositories to add:

  • nao_button_sim
    • There is an existing release repository which should be imported: https://github.com/ijnek/nao_button_sim-release.git
  • nao_lola
    • There is an existing release repository which should be imported: https://github.com/ijnek/nao_lola-release.git

• Name of the new release team: the_construct

• Release repositories to add:

  • wall_follower_ros2
    • There is an existing release repository which should be imported: https://github.com/rfzeg/wall_follower_ros2-release

• Team members

  • @rfzeg

Updates to perception membership.

This is a request to get myself added to the perception team.

Currently, vision_opencv is not under listed under ros-perception.tf, but under 00-ros2_core.tf``.

Would you be able to add vision_opencv-release to ros-perception.tftoo? Is it possible to have two teams managing a release repo?

New team members

• @ijnek

• Name of the new release team: cascade_lifecycle

• Release repositories to add:

  • cascade_lifecycle
    • There is an existing release repository which should be imported: https://github.com/fmrico/cascade_lifecycle-release.git

• Team members

  • fmrico

• Name of the release team: moveit

• Release repositories to add:

  • pick_ik
    • There is an existing release repository which should be imported: https://github.com/pickNikRobotics/pick_ik-release
  • rsl
    • There is an existing release repository which should be imported: https://github.com/pickNikRobotics/rsl-release
  • generate_parameter_library
    • There is an existing release repository which should be imported: https://github.com/picknikrobotics/generate_parameter_library-release

Updates to robotwebtools membership.

New team members

• @achim-k

• Name of the release team: ros2-team

• Release repositories to add:

  • rosidl_core

Updates to membership.

New team members

• [@febu1300](LINK TO https://github.com/febu1300/ros2can/blob/master/package.xml Buruk T. Fetene/febu)

Retiring team members

• [@GITHUB_USERNAME](LINK TO SOURCE COMMIT OR PULL REQUEST UPDATING MAINTAINER INFORMATION)

• Name of the new release team: aerostack2

• Release repositories to add:

  • aerostack2
    • There is an existing release repository which should be imported: https://github.com/aerostack2/aerostack2-release.git

• Team members (https://github.com/aerostack2/aerostack2/blob/main/aerostack2/package.xml)

  • @miferco97
  • @pariaspe
  • @RPS98
  • @perezsaura-david

Looking to do a ReleaseThirdParty.

• Name of the release team: sports

• Release repositories to add:

  • rot_conv_lib

• Name of the new release team: mad

• Release repositories to add:

  • create_robot
    • There is an existing release repository which should be imported: https://github.com/MADdantas/create_robot_ros2-release
  • libcreate
    • There is an existing release repository which should be imported: https://github.com/MADdantas/libcreate_ros2-release

• Team members

  • @MADdantas

In #99, there's been some discussion about undergoing ros/rosdistro review procedure before requesting a release repository here on ros2-gbp. I'm going to move this to a dedicated issue so we can discuss further. Quoting the important parts:

The reason I'm pushing for brand-new repositories to be registered in the rosdistro index prior to provisioning their release repositories here is that I'd like the packages to undergo the review procedures we have in place in ros/rosdistro. Not the least of which is the package naming review, which could result in more work here if the name changes. (@cottsay)

A bloom release doesn't have to be the first interaction with the rosdistro database.
There are three stanzas under a repository listing in rosdistro: doc, source, and release. Bloom will offer to create all of them if none exist yet but it's also entirely possible to add source and/or doc entries beforehand, especially for projects in early development.

I can't say definitively but in the days before free CI (Travis, Circle, GitHub Actions, etc) was available I think it was more common for package maintainers to add source entries before the initial release is made in order to make use of devel jobs for their projects' primary CI. (@nuclearsandwich)

We've talked about this once or twice and I agree with the rationale but keep forgetting to put it on the official agenda for discussion in the ROS 2 team and open the review guidelines update PR. (@nuclearsandwich)