Noetic release

[destogl]

Are you planning to do noetic release at some point?

[artivis]

Thanks for the reminder.
I sure will release it in Noetic, but there is likely some Python 2 -> 3 port to do first.
I'll have a look asap 👍.

[destogl]

I added the repository in my CI here and got some strange error, probably python 2 -> 3 error

[artivis]

probably python 2 -> 3 error

Yep looks like it.

[jarvisschultz]

I was just trying to build this on Noetic, and ran into a few issues that I think I was able to sort out. See the python3_noetic_conversion.jas branch on my fork. To release, these changes would either need to be updated to support Python 2 and 3 simultaneously, or the repo would have to adopt a Noetic and newer branching strategy as described in the ROS Python 2->3 Migration Guide. Happy to help if @artivis can take the lead on suggestions for how to PR.

[artivis]

Hi @jarvisschultz,
Thanks for taking a shot at the migration! I'm afraid I won't have time to take a look before next week but at first glance I'd say I'm fine with having a separate noetic branch.

[malban]

A noetic release would be great. @jarvisschultz's fork seems to work fine me.

[130s]

I'd vote for a separate branching given the chance of needing maintenance in the future may be slim (last commit on the main branch was back in 2018), and the life of the versions that depend on Python2 is known to end with a fixed term (ROS Melodic, the last LTS with Python2 support, will EoL in 2023).

[robo-jordo]

@artivis Any update on a noetic release here using the fork from @jarvisschultz ?