One thing I wanted to mention was that @gerkey stated the above 8-9 person-months for an average ROS1 LTS release. I’d like to get an estimate of what it will be to do the Python2 → Python3 conversion in addition to the ‘normal’ library upgrades and such of an average new LTS release. My guess is that it’s significantly more, thus my original proposal.
Also, I think the idea of the community taking up the work to do it is a completely valid one. If people don’t want to move to ROS1, then nothing should stop them from self-organizing and taking on the work of doing the Python2->3 port themselves and creating a new LTS in 2020.
So maybe the transition plan could be a combination of things:
- A migration script to do 80% of the ROS1 → ROS2 conversion for those who want to migrate
- An improved ROS1 bridge for running hybrid systems?
- ROS2 support in 2020 on both 18.04 and 20.04
- Support of Melodic until 2023
- Better documentation of ROS2 (see @mikeferguson thread)
Anything I missed there that is discussed in this thread?