Please don’t do this. Please?

Converting a package from rosbuild to catkin mid-release has generally resulted in API instability and surprises for users of your package.

If you do do this, please test the pre-release builds very carefully before they hit the public repositories, to make sure that you haven’t accidentally changed the exposed headers, APIs, etc.

At a minimum, I expect anything compiled with an rpath pointing to your libraries will break when the underlying library moves during the upgrade.

-Austin

On Mar 12, 2014, at 9:55 PM, Dirk Thomas <dthomas@osrfoundation.org> wrote:

Hi Thomas,

I have added you to the dry release repo.

Cheers,
- Dirk


On Wed, Mar 12, 2014 at 9:21 PM, Thomas Moulard <thomas.moulard@gmail.com> wrote:
Hello,
could you please add my account: thomas.moulard@gmail.com to ros-dry-releases?

I would like to remove vision_visp from the repository and release the
new one through
Catkin and Bloom.

Thank you,
--
Thomas Moulard
_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release

_______________________________________________
ros-release mailing list
ros-release@code.ros.org
http://lists.ros.org/mailman/listinfo/ros-release