When should a ROS package be published?

edit

I think Pete's answer is pretty good. I would like to add a few other suggestions.

1) I would suggest you add a set of unit and integration tests with your package. This will help you with maintenance over the long run.

2) I saw a large bag file (~12MB) in the repository. It is totally reasonable to have a file appropriate for testing, but I would suggest making it as small as you think you can get away with.

3) I would think long and hard about how much effort you want to put into maintaining your package. If you don't think you can make the commitment to maintaining the repo I would find someone else to help you out.

4) If you want to get feedback perhaps go put a post up on ros.discourse.org. It is a good way to get others to look at your code.

There are no hard and fast rules for when to publish a package, but there are a few important things to consider. Your repository looks pretty tidy, you've already got a licence and some examples so could be ready to publish.

Do you expect the API or command line interfaces to your utility to change in the foreseeable future? Packages are expected to be maintained with the same interfaces with deprecation warnings being added before functions are removed. If your package is still in the development phase where these things are being altered then it's probably not time to publish it.

Have you got any feedback off any other users using this? It's always good to get a second pair of eyes to look at (and try and break it) before publishing it officially. Maybe another user reading this question may have a use and will do this for you.