Is this something to worry about ?

That does seem odd. I've asked someone from the releng team to investigate.

So it turns out that, though unusual, that version stamp is actually correct. It was intentionally bumped to 3.0.0. This is because plugin and feature versions should reflect API compatibility, not product versions.

It's likely that one of the plugins (or child features) under com.ibm.team.rtc.server.feature had its major version bumped. Perhaps this was due to an API incompatibility (though I wouldn't expect that in a point release), but more likely due to someone incorrectly assuming a plugin they modified should have its version bumped from 1.x to 2.x or something, just because we were then in a 2.x release.

If you want to know the gory details, see comment 6 of
96672: Automate verification of "version bumping" during a release.

So it turns out that, though unusual, that version stamp is actually correct. It was intentionally bumped to 3.0.0. This is because plugin and feature versions should reflect API compatibility, not product versions.

It's likely that one of the plugins (or child features) under com.ibm.team.rtc.server.feature had its major version bumped. Perhaps this was due to an API incompatibility (though I wouldn't expect that in a point release), but more likely due to someone incorrectly assuming a plugin they modified should have its version bumped from 1.x to 2.x or something, just because we were then in a 2.x release.

If you want to know the gory details, see comment 6 of
96672: Automate verification of "version bumping" during a release.

Thanks, Nick.