[ros-users] [Discourse.ros.org] [Packaging and Release Management] Lack of a velodyne release

Kei Okada ros.discourse at gmail.com
Tue Oct 17 11:23:14 UTC 2017

> I always find that a bit odd: In my experience, running the catkin_generate_changelog, catkin_prepare_release, bloom-release commands takes up maybe 1% of the time in maintaining a package.

I'm completely agree on that, but it is true that a lot of maintainer feel it is hard to do release job. Maybe they're toooo busy or more interested in other projects.

> Does it really make a maintainers job that much easier if somebody else takes over the binary release part?

Main purpose of releasing deb binary from other people is not aiming to reduce original maintainer's job, but to help users waiting for deb package for newer distro, like @kmhallen. 

> And what happens when nobody feels responsible for the remaining 99% of the work?

Of course, that's a big problem. But I'm afraid users waiting for deb packages could not wait until we find solution of this problem, and afraid that many people disappointed to see , for examples, there is no easy way (without source compile) to use velodrome driver on the ROS system.

 1) Releasing deb for new distro helps users who willing to use existing packages on their new machine.
 2) Maintaining source tree helps users who willing to use new features or fixed version of the software

I agree we need to take an effort to find/participate maintainer who responsible of good packages, but at the same time, I feel that we want to find good solution to help users just waiting for existing package on new distro. That's could be solve just a 1% of time of us.

[Visit Topic](https://discourse.ros.org/t/lack-of-a-velodyne-release/2734/6) or reply to this email to respond.

More information about the ros-users mailing list