So, having not undertaken any ROS2 porting myself, I have to ask - what's the common (dare I say standard?) practice for repos/branches? Keep the same repo, and create a `ros2` branch? I know that upstream ROS2 repositories tend to follow the `master` + distro branches approach.
Github being what it is, having two essentially 'main' branches (one for ROS1, one for ROS2) is suboptimal in terms of visibility and code search, however creating `ros2_*` repos feels unpleasant as well.
---
[Visit Topic](
https://discourse.ros.org/t/ros-2-collaboration-bulletin-board/2239/58) or reply to this email to respond.
If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates.
______________________________________________________________________________
ros-users mailing list
ros-users@lists.ros.org
http://lists.ros.org/mailman/listinfo/ros-users
Unsubscribe: <
http://lists.ros.org/mailman//options/ros-users>
(text/plain)