Closed mikeferguson closed 4 years ago
Thanks @mikeferguson! I wasn't previously aware of the possibility to use a branch for both melodic and noetic, but makes sense in retrospect (with the little bit of bloom experience I have).
It seems like for almost everything (i.e. packages anything w/o python that's not compatible with both 2/3), we could just operate with noetic and melodic both being released from the melodic-devel branch. That would save a lot of potential backports; any reasons not to do this?
Absolutely no reason to create separate branches. I'd also suggest at some point renaming it to "ros1" when you start to have a "ros2" branch (which I'll probably be bugging you about in a few weeks - working on a port).
I'm fine with going ahead and merging this, @mikeferguson
This should support both melodic and noetic on same branch: