Closed esteve closed 8 years ago
Actually, I don't know if these entries should point to 'devel' or to 'graveyard/develop', what's the rationale between those two? Thanks.
Life got complicated when I moved out of the rocon project...graveyard is obviously not meant to be used, but still lingering because the continuing team might need those commits at one point in the future.
We've since come back to cherry-pick what is useful to continue on for the gopher project, but that also needed to be done in a way to not break api in the released versions on indigo/kinetic. Hence the re-branching of everything.
devel
are the ones we work onrelease/<version>-<rosdistro>
are the ones we officially release for ros/gopher.I have updated the rocon.rosinstall
files here for you in branches release/indigo
, release/kinetic
, devel
. The kinetic and devel have also been heavily trimmed to only rosinstall those components that continue to be supported/developed.
FYI @tfoote - see above.
Sorry for the minor breakages here and there. Now I've started trimming back I'll look at what's still usable for the turtlebot in kinetic.
@stonier thanks!
@esteve @stonier thanks for the updates.
The 'develop' branch does not exist in several of the repositories referenced in the rosinstall files, but 'devel' does:
https://github.com/robotics-in-concert/rocon_concert/tree/devel https://github.com/robotics-in-concert/rocon_multimaster/tree/devel https://github.com/robotics-in-concert/rocon_msgs/tree/devel https://github.com/robotics-in-concert/rocon_tools/tree/devel https://github.com/robotics-in-concert/rocon_app_platform/tree/devel https://github.com/robotics-in-concert/rocon_tutorials/tree/devel https://github.com/robotics-in-concert/rocon_qt_gui/tree/devel