Problem releasing a different branch (bloom)

asked 2016-07-19 01:05:35 -0600

cvillar gravatar image

I'm migrating packages from Indigo to Kinetic and releasing them. I've created a new branch named kinetic-devel (locally and at github) where I push the changes I've made. Also, the package appear at kinetic/distribution.yaml as branch kinetic-devel.

After the catkin_prepare_release the version of the package for kinetic is higher than the indigo one (for example, 1.0.5 indigo and 1.0.6 kinetic), i create the tag kinetic-1.0.6 and push it to the repository as usual.

But, when I try to run bloom-release --rosdistro kinetic --track kinetic summit_x_sim --edit it tries to release "kinetic-1.0.5", and if I create this tag it complains about repository version and tag version are not the same.

For a proper release I had to merge kinetic-devel branch into indigo-devel before the bloom_release, it works but it'ś not the way it should be, it is supposed to have different branches for different versions of ros and different releases without merging all branches in one.

What I have to do for releasing a kinetic version of the package without a merge into indigo?

edit retag flag offensive close merge delete

Comments

Upstream Devel Branch: <vcs reference=""> Branch in upstream repository on which to search for the version. This is used only when version is set to ':{auto}'. [None]: kinetic-devel

Here is the solution, I'm dumb as hell

cvillar gravatar image cvillar  ( 2016-07-19 01:44:38 -0600 )edit
2

If I may make a suggestion: when releasing multiple branches from the same repository, it's typically recommended to increase the minor version nr, not the patch (so kinetic would be 1.1.0 in your case, not 1.0.6). If you now need to release a new indigo release, what version will it use?

gvdhoorn gravatar image gvdhoorn  ( 2016-07-19 03:25:44 -0600 )edit
add a comment