Before making those changes, I tagged the previous trunk as
tags/boxturtle. So, we should be able to check out that version
instead of trunk for Box Turtle systems.
If anyone can think of a better solution to this problem I am open to
suggestions. I asked on ros-users this morning, but have not gotten
any answers yet.
--
joq
Michael Quinlan <michael...@gmail.com> wrote:
> David noticed that stage no longer compiles. I got out the code and
> the same things happens to me. I noticed in the svn logs that you
> changed something and the log indicates that it doesn't work with with
> 3.01. I suppose my question is, what is the best path forward. Should
> we upgrade out machines (my laptop and one of the vision machines) to
> the new ROS or should we checkout the older code ?
I recommending keeping most of our systems on Box Turtle until
C-turtle is released (probably some time in July). ,Check out the
utexas-art-ros-pkg/tags/boxturtle version, instead of trunk.
A few systems should install latest, so we can fix problems due to ROS
changes (such as the stage version change). Check out the trunk for
this, and make any required changes there.
If we have to update the boxturtle version, we should copy
tags/boxturtle to branches/boxturtle and fix it there. I am hoping
that will not be necessary, because it will require extra effort
back-porting and merging fixes.
I am not particularly happy with that approach. Maybe we can think of
something better. I asked on ros-users, and they recommended using
different branches. That works for them, but I don't think they've
really thought this stuff through from a user perspective very well.
--
joq