Preparing for Rolling Sync 2025-12-01

Hello everyone!

It’s been a minute since the last sync and there are several new packages and updates ready to be released for ROS 2 Rolling Ridley! :rolling:

We will hold rosdistro PRs for the sync starting today and will aim to do the sync by 2025-12-02T07:59:00Z or later if the regressions are unresolved.

There are currently 38 regressions :sad_but_relieved_face: and 490+ packages to release :tada:

I’ll make an announcement here once the sync is completed and we can resume merging into rosdistro.

fyi: Some of the regressions come from a deprecation cleanup in ros2_control 6.0.0. I opened PRs to known downstream packages but some haven’t got merged yet.

2 Likes

Thanks for flagging! Will follow up to get the PRs merged :+1:

1 Like

These deprecation are removed within 5 months of declaring them deprecated.

Is there a policy how long such deprecation should exist?
I don’t mind though, but I also didn’t feel the urgency to fix it asap.

Perhaps put the EOL date in the deprecation next time :slightly_smiling_face:

5 months should be ample time. The expectations should be that deprecations go away starting from the next Rolling release.

We don’t want to stall like ROS1 did.

2 Likes

@Yadunund Some of the failures look like random ssh-agent failures to start up in the build machines, for example: 1, 2 … any action required by the maintainers here? Or just waiting for it to retry and resolve on its own? :thinking:

All “rel_import-package” jobs are also broken since 24th Nov.:

  1. Hrel_import-package [Jenkins]
  2. Jrel_import-package [Jenkins]
  3. Rrel_import-package [Jenkins]

related to git:

08:08:15 Cloning repository https://github.com/ros-infrastructure/reprepro-updater.git
08:08:15  > git init /home/jenkins-agent/workspace/Rrel_import-package/reprepro-updater # timeout=10
08:08:15 ERROR: Error cloning remote repo 'origin'
08:08:15 hudson.plugins.git.GitException: Could not init /home/jenkins-agent/workspace/Rrel_import-package/reprepro-updater

Hi everyone.

For all that faced issues in the buildfarm for the last week (and @jlblancoc, @christian which mentioned it), this was a problem we had with some unattended upgrades in our servers.

It is now solved. So please, if you find any similar issues, feel free to ping me or write on the #Infrastructure General Zullip channel

1 Like

Hi all,

Apologies for the delay here.

I’ve managed to get the number of regressions down to 22 and have created these tickets to let maintainers know their packages will be removed with this sync.

Proceeding with the sync :rocket:

1 Like

The sync is complete.