It's all about the answers!

Ask a question

Is this something to worry about ?


Kevin Ramer (4.5k6172190) | asked Nov 08 '10, 3:54 p.m.
On RTC servers recently updated to 2.0.0.2 ifix4 I see "unusual" versioning
of com.ibm.team.rtc.server.feature as shown below:


Provision Status
CRJAZ0303I The profile install from "file:../update-site" was started at "Sat Oct 23 10:35:26 EDT 2010".

CRJAZ0300I Installing the feature "com.ibm.team.rtc.server.feature_3.0.0.I200910271201-7Y79CX9svm-gdr4YZ04SsCFbcS7W".
CRJAZ0300I Installing the feature "com.ibm.team.repository.server.feature_1.0.2.I200911052100-7f7QVAacQE_Ks-0oLgcabsNNEiEE".
CRJAZ0300I Installing the feature "com.ibm.team.repository.server.emf.feature_1.0.2.I200910052001-7_7I2AgI99r9IDhDDDX".

Cosmetic ?

3 answers



permanent link
Nick Edgar (6.5k711) | answered Nov 09 '10, 4:44 p.m.
JAZZ DEVELOPER
That does seem odd. I've asked someone from the releng team to investigate.

permanent link
Nick Edgar (6.5k711) | answered Nov 10 '10, 2:30 p.m.
JAZZ DEVELOPER
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.

permanent link
Kevin Ramer (4.5k6172190) | answered Nov 11 '10, 9:55 a.m.
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.

Your answer


Register or to post your answer.