Starting now, I will be holding new Noetic ros/rosdistro release PRs with a plan to sync ROS Noetic packages to the main apt repo on 2022-02-14. Please comment here if there are any issues I should know about before performing the sync.
While there are currently 0 packages waiting to sync, this freeze is in anticipation of a release fixing a regression in xacro.
I prepared new releases for xacro and rviz to fix some recently introduced regressions:
Thanks a lot for cutting a new release. Unfortunately, I didnât notice the sync announcement earlier this week. Iâm still struggling with the notification levels available on ROS discourse. I switched now from âTrackingâ to âWatching first postâ. Hope, that helps.
On which communication channel should I announce a regression in future, if the corresponding sync announcement wasnât posted yet?
On which communication channel should I announce a regression in future, if the corresponding sync announcement wasnât posted yet?
If the regression was already syncâd to the main apt repo then an issue on GitHub - ros/rosdistro: This repo maintains a lists of repositories for each ROS distribution or a comment on a release fixing it would be a good place. If it affects Noetic, Iâd be appreciative of an FYI @sloretz comment on the issue on the upstream repo. Otherwise, regressions arenât really a big deal until a sync-to-main is planned. I think catching regressions in the testing apt repo is totally fine.
