ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

When to release build increment?

asked 2013-09-03 05:26:59 -0600

130s gravatar image

updated 2013-09-03 07:45:40 -0600

William gravatar image

Related to a discussion at this release request.

Even looking at this, I still feel like making only build-increment release, when I add to upstream/development repository that's only a change that has nothing to do with functionality. Especially when the change is an attempt to pass buildfarm, which I think ideally should have been included in the "first" release (ie. 0 build increment) but somehow missed and found on buildfarm. I just want to confirm in the situation like this do we still need to release a new version? If it is defined I'd appreciate that. Thanks!

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2013-09-03 07:49:27 -0600

William gravatar image

If you change the upstream repository then you must increase the upstream version. Period. If you don't want to have to make a lot of patch releases, then you should make sure it builds before you commit it to the farm.

The release increment is only to be used for when you change the release of the package without touching the upstream. This includes running the release again for new rosdep rules, running for new release targets (like os or platform), or to add a patch in the release repository (should ideally be reserved for third party packages).

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2013-09-03 05:26:59 -0600

Seen: 151 times

Last updated: Sep 03 '13