Currently, there is no version number listed for this package.
It would be useful to be able to reference which version of this package is being used, e.g., when listing dependencies for another project. That way, it's easy to say things like "This project has been tested with version 1.0.0 of sar_game_command_msgs", and know that when sar_game_command_msgs are updated to a newer version, we may have to test or upgrade the project that uses them.
I've added a version number to the package information. After merging this pull request, you can tag a release as follows from your local command line:
git tag -a v1.0.0 (create a tag titled "v1.0.0" and add a description)
git push origin --tags (will push the tag to the configured upstream repository)
From the github web interface in the "Code" tab, you can click on "Releases", then "Tags", and there's a button to "Add release notes" where you can enter a description of the version (can be the same as what you entered for the tag).
cmhuang
commented
8 years ago
Currently, there is no version number listed for this package.
It would be useful to be able to reference which version of this package is being used, e.g., when listing dependencies for another project. That way, it's easy to say things like "This project has been tested with version 1.0.0 of sar_game_command_msgs", and know that when sar_game_command_msgs are updated to a newer version, we may have to test or upgrade the project that uses them.
I recommend using semantic versioning.
I've added a version number to the package information. After merging this pull request, you can tag a release as follows from your local command line:
git tag -a v1.0.0(create a tag titled "v1.0.0" and add a description)git push origin --tags(will push the tag to the configured upstream repository)