Hi @sloretz . Noetic EOL is coming in a few weeks. Could you please create a timeline (at least a rough one) of merge windows and releases?
Also, do you still consider it possible to update ros_comm, or are all PRs there already doomed?
ROS Resources: ROS Homepage | Media and Trademarks | Documentation | ROS Index | How to Get Help | Q&A Help Site | Discussion Forum | Service Status |
Hi @sloretz . Noetic EOL is coming in a few weeks. Could you please create a timeline (at least a rough one) of merge windows and releases?
Also, do you still consider it possible to update ros_comm, or are all PRs there already doomed?
I believe EOL also means the buildfarm is getting taken down.
Noetic EOL is coming in a few weeks. Could you please create a timeline (at least a rough one) of merge windows and releases?
Will do!
Very roughly I do syncs every two weeks. If there are no regressions, there will be syncs on:
Freezes start two days before. I’m thinking of skipping the May 15th sync and doing a longer freeze for the May 29th sync.
Also, do you still consider it possible to update ros_comm, or are all PRs there already doomed?
I’ll review and merge PRs that make it build on newer Debian/Ubuntu systems.
It’s important to me that the final Noetic sync contains working software, so I’m very reluctant to merge PRs when I think there’s even a small risk of introducing regressions. If there’s a bug fix you really want to get in, reviewing it and describing the steps you took to test it will increase its chances. If you recruit another person to review and test it, it will help even more.
It goes without saying, but PRs that break API or ABI won’t be merged.
I believe EOL also means the buildfarm is getting taken down.
Correct. You’ll still be able to apt-install
ROS 1 packages on Focal, but there will be no updates to those packages. ROS Noetic PR jobs, devel jobs, and doc jobs will stop too.