Ask Your Question

Revision history [back]

Version tagging for new releases and distributions

My upstream repository contains a master branch, as well as branches for Groovy, Hydro, and Indigo. Each distro branch is named <ros_version>-devel. How should I handle release tagging in this case? For example, I already have a "0.1.0" tag for my last Hydro release. For Indigo, I only modified my package.xml and threw in a #define to silence some warnings, so the software is, for all intents and purposes, identical. I was hoping to create the same version number for Indigo as I have for Hydro, but even if I bumped it to 0.1.1, how should I tag it? Will bloom be able to handle a tag with a name like "0.1.1-indigo"?

Version tagging for new releases and distributions

My upstream repository contains a master branch, as well as branches for Groovy, Hydro, and Indigo. Each distro branch is named <ros_version>-devel. How should I handle release tagging in this case? For example, I already have a "0.1.0" "v0.1.0" tag for my last Hydro release. For Indigo, I only modified my package.xml and threw in a #define to silence some warnings, so the software is, for all intents and purposes, identical. I was hoping to create the same version number for Indigo as I have for Hydro, but even if I bumped it to 0.1.1, how should I tag it? Will bloom be able to handle a tag with a name like "0.1.1-indigo"?"v0.1.1-indigo"?