Closed marc-hanheide closed 8 years ago
indeed. that's the point. when we currently try to release to indigo it'll try to release 0.1.19 which won't work because that is already existing. Hence I wanted to bring the version number in indigo in sync, so I can then release 0.1.20 from the indigo branch. better would be we prefix the tags and configure the tracks with that prefix. However that'll break auto release wizard but that might be the price to pay... Anyway. I think PR is valid and should be merged so we can rerelease to indigo. If not suggest an alternative please.
Oh, sorry, didn't it release when I did it?
well, yes it did, but only in the jade branch. We need to merge that change of version number back into the indigo branch. Which is what I propose here.
This makes my head hurt. Can you give me a call on Monday morning and we can work through this?
sure :-) pick your time at https://doodle.com/mhanheide your's looks fully booked...
No, there's a complicated issue with releasing across two ROS tracks where I don't think we can make the same release numbers as they are tags on different branches (for us), but the tags are branch-neutral so if we do this I will have to release 0.1.20 on indigo and 0.1.21 on jade.