Closed dirk-thomas closed 8 years ago
So if we delete the indigo-devel
branch, can we close this issue?
Since Hydro has been EOLed since the ticket was created we could not care about those. But wouldn't it be easy to create a hydro-devel
branch to make it easy if people do want to build it?
Ok, so we could:
indigo-devel
onto the 0.2.5 taghydro-devel
from 0.2.4 tagIs that it?
Yes, that should be good as far as I can tell.
Ok, I created hydro-devel
and rebased indigo-devel
accordingly.
The state of this repository has diverged significantly from what is actually being used / has been released latest. Currently it is not clear where future patches should be applied and how they could be released:
console_bridge
To match user expectation I think the repo needs some clean up:
console_bridge
version being used by ROS Indigo(The general rules apply that no version number should ever be reused or be available from different branches containing different code.)