Version of some fragments seem not to be updated

[laeubi]

While working on

eclipse-platform/eclipse.platform.releng.aggregator#3131

I noticed that some fragments are still on version 6, even though most of them are at version 12, see for example this one:

cdt/core/org.eclipse.cdt.core.linux/META-INF/MANIFEST.MF

Line 5 in fec29d7

Bundle-Version: 6.1.100.qualifier

[jonahgraham]

Is that wrong? The host bundle in that case is also 6.x. For versions like this I mostly rely on API tools & tycho compare + replace.

I don't have a strong objection to aligning the fragment versions with the host version if that is best practice and that doesn't negatively affect API consumers, but I don't think I can increase org.eclipse.cdt.core.native major version without a major CDT release.

The fragments that have actually compiled code change for each release due to how the native code is signed - this changed in 919f0a0 - and eventually I found it easier to keep these bundles aligned with the CDT version so that I didn't have to do extra work to bump the version numbers of them. Now that I am using tycho-versions-plugin:bump-versions (see upcoming PR #1190) this probably isn't needed.

[laeubi]

Is that wrong?

Not in general I just has had the feeling that the other ones are updated according to the release number so I was curious, but as you explained it is all as intended I'll close the issue.