[ros-release] [Discourse.ros.org] [Release] Maintainer best practices handling changes through ROS releases

Jack O'Quin ros at discoursemail.com
Tue Nov 8 15:31:23 UTC 2016

Formerly, the rule was simple: introduce new features in a new distro, so existing users are not impacted.

With Indigo LTS, I found myself wanting to support new hardware that was not available when Indigo was initially released. An example is the popular Velodyne VLP-16 LIDAR. 

Since I believe I can add that model with minimal disruption to existing users, I've decided to make an exception to the old rule, which made more sense when there was a new ROS distro every six months.

[Visit Topic](http://discourse.ros.org/t/maintainer-best-practices-handling-changes-through-ros-releases/771/5) or reply to this email to respond.

To unsubscribe from these emails, [click here](http://discourse.ros.org/email/unsubscribe/dba037e9de34cc85857e911c36e0d8bfa82ebe073bbe67c90c842de926d80830).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-release/attachments/20161108/258459dd/attachment.html>

More information about the ros-release mailing list