Repository navigation
Package Versioning
Claude edited this page Oct 10, 2026
·
7 revisions
Make sure all packages within this repo have the same version number, as bloom the release tool will be unable to release the package:
bloom will only operate on an entire repo and everything in the repo must be in the same version. This is because the nature of tagging a repo is global across the repo so it asserts that all packages have the same version. And bloom operates on the repo, hiding the files in the local checkout will not work. from: here.
Package versions convention:
-
2.xx.xxfor ROS indigo (gazebo2) -
3.xx.xxfor ROS jade (gazebo5) -
4.xx.xxfor ROS kinetic (gazebo7) -
5.xx.xxfor ROS kinetic (gazebo9) -
6.xx.xxfor ROS melodic (gazebo9) -
7.xx.xxfor ROS noetic (gazebo11) -
8.xx.xxfor ROS 2 jazzy (Gazebo Harmonic)
Controllers
How to add
How to create
- Creating ROS Plugins for Gazebo
- Gazebo and Gazebo ROS Installation
- Gazebo Topic Naming Conventions
- ROS Interface Plugin
- Setup virtual keyboard joystick
How to install
How to generate
How to set
- Setting up CrazyS as Fixed Wing HiL Simulation (Pixhawk, Mavros, Mavlink, QGC)
- Setting up the CrazyS Simulator
How to develop
- Include ordering in cpp and header files
- Interfacing CrazyS through MATLAB
- Interfacing CrazyS with GitHub Action
- Interfacing CrazyS with TravisCI (old)
- Package Versioning
- Software Specifications
- Specifying constants and default values
- Working With Meshes in Gazebo
More information