Release 0.254.0 for iron

[azeey]

Going to make a release of 0.254.0 off the iron branch. I wanted to create a PR before tagging it since I'm bumping the version from 0.247.0 to 0.254.0 to align with the versioning scheme mentioned in

ros_gz/RELEASING.md

Lines 36 to 80 in 70fb5dc

	## Versioning
	All `ros_gz` packages are under fast development and haven't reached version
	1.0 yet. The team will make an effort to keep changes backwards compatible
	within a ROS distribution, but API / ABI / behaviour may be broken if necessary.
	The versioning scheme uses the minor version to identify ROS and Gazebo
	versions:
	* 1st digit:
	* ROS 1: 1
	* ROS 2: 2
	* 2nd digit:
	* Melodic: 0
	* Noetic: 1
	* Dashing: 0
	* Eloquent: 1
	* Foxy: 2
	* Galactic: 3
	* Humble: 4
	* 3rd digit:
	* Blueprint: 0
	* Citadel: 1
	* Dome: 2
	* Edifice: 3
	* Fortress: 4
	* Garden: 5
	ROS | Gazebo | Version
	-- | -- | --
	Melodic | Blueprint | 0.100.X
	Melodic | Citadel | 0.101.X
	Noetic | Blueprint | :x:
	Noetic | Citadel | 0.111.X
	Noetic | Dome | 0.112.X
	Noetic | Edifice | 0.113.X
	Dashing | Blueprint | 0.200.X
	Dashing | Citadel | 0.201.X
	Eloquent | Blueprint | 0.210.X
	Eloquent | Citadel | 0.211.X
	Foxy | Blueprint | :x:
	Foxy | Citadel | 0.221.X
	Foxy | Dome | 0.222.X
	Foxy | Edifice | 0.223.X

[azeey]

hmm, I was going to do the same for rolling, but not sure what the version would be. The last release according to the changelogs was 0.246, but looking at the package available on packages.ros.org, it shows 0.245.

[mjcarroll]

It looks like everything except the release happened for 0.246?

[azeey]

I guess we can set the first digit to 3 to indicate rolling and skip the second digit? So it would be 0.34.0. Alternatively, we can designate 14 as the number for rolling going along with the current sequence, but then the version would be 0.2145.0, which would be "older" than 0.245. I guess this whole versioning scheme breaks when the number associated with the ROS or Gazebo distro is no longer a single digit.

[azeey]

It looks like everything except the release happened for 0.246?

Looks like it.

[mjcarroll]

Can we just defer doing anything on rolling and release 0.246 there?

We will likely have to do something once 24.04/jazzy is ready, but maybe that's a good time to bump the major

[azeey]

Can we just defer doing anything on rolling and release 0.246 there?

We will likely have to do something once 24.04/jazzy is ready, but maybe that's a good time to bump the major

Okay, I will look into releasing 0.246 from the tag.

I was thinking we needed some of the recent changes to unblock ros-navigation/navigation2#3634, but it looks like we don't since #453 was merged after 0.245 and 0.246.