How come Confluence OnDemand no longer shows an accurate version number

[Bob Swift]

It use to be when you queried Confluence via SOAP APIs (for instance, with getServerInfo) you got an accurate representation of the version you were attached to. Not any more:

Download: Confluence version: 5.4.1, build: 4727

OnDemand: Confluence version: 5.4.0, build: 4913

[Adrien Ragot 2]

Hi Bob,

Version numbering on OnDemand is misleading since multiple features are added/removed compared to the Download version. Besides logins and applinks (which are pre-wired in OnDemand), think about the experiments that Atlassian runs and sometimes confirms and sometimes throws away.

Also, versions are used internally to compare many things, for example for imports/exports and the "What's New" dialog. It is not obvious at all for a developer what "should" be the OD version.

The only things which are wise to consider are:

• On a given date, the OnDemand version is more recent than the latest available Download version,
• On OD, version numbers always increase.
• Build numbers are quite reliable when it's about comparing the features.

Best of luck for whatever you're attempting to perform with those numbers.

[Bob Swift]

Thanks for the answer. The major version number should still be more accurate and it was until something changed around 5.4.x.
This was written up as CONF-33111 after some other discussions with Atlassian.