[quote="peci1, post:5, topic:5112"] I was more curious about how to handle people who are already using the package and just git pull from time to time Probably switching the main development to a different branch than master and adding a build error into master telling the people to switch branches and clean buildfiles? [/quote] That will break them anyway so there's not much point in adding the build error to tell them to switch. You could tag or branch before the rename to allow people to get the older name if they don't want to update immediately they have to switch to the tag for branch. If you're checking out code from `master` there's a level of expectation that you may have to update things. If they can just switch to the archival branch that should be easy for them. Or you could just switch development to a new default branch and leave master as the archival branch. Though that may confuse new users down the line when they don't find the latest content on the master branch. --- [Visit Topic](https://discourse.ros.org/t/announcing-the-tensorflow-ros-package-the-easy-way-to-get-to-c-tensorflow-api-in-ros/5112/6) or reply to this email to respond. If you do not want to receive messages from ros-users please use the unsubscribe link below. If you use the one above, you will stop all of ros-users from receiving updates. ______________________________________________________________________________ ros-users mailing list ros-users@lists.ros.org http://lists.ros.org/mailman/listinfo/ros-users Unsubscribe: