XSF Discussion - 2022-08-20

Hi, wurstsalat and me would like to clarify the usage of the patch version (last number, e.g., *2* in *0.1.2*, at least by following https://semver.org ) in the version scheme of XEPs. Is the patch version only incremented for fixes?

Use case would be: comparing implemented version with latest version (of XEP-xxxx), and showing a hint if the implemented version is outdated. This would make little sense if patch revisions only mean typo fixes, but no functional changes. Then it would probably better to compare by major.minor only.

And is that somewhere specified?

I think someone said state.major.minor.patch

I could find the advance of the major version (e.g., 1.0 to 2.0) in https://xmpp.org/extensions/xep-0001.html : > Elevation to Stable status (version 1.0) is a major advancement for the XEP, indicating a strong sense on the part of the XMPP Council and XMPP developer community that the specification will be of lasting value. > In order for a XEP to advance from Stable status to Final status (version 2.0), it must be shown to be stable and well-received by the XMPP developer community. That seems to differ from semantic versioning. And I could not find when the minor and patch versions are advanced.

> I think someone said state.major.minor.patch I have never seen such a version for a XEP. Was that a proposal?

Hm, I feel like I have seen such a version, but maybe that was a dream

xD

Anyway, once a XEP hits 1.0 it shouldn't change too much in incompatible ways, and after 2.0 it definitively shouldn't, so almost semver, if you ignore the 2

and semver says anything goes at 0.x, which is the same here

x is experimental/draft/final, y is material updates, z is Editorial changes only.

Thanks. Is that specified somewhere?

Goodness knows :)

`2.5rc3` isn't helping :D (XEP-0030)

Hi folks, I took on the challenge to rework xmpp.org's software section. You've probably seen the new listing (using 'cards', icons, and more) already. I now went a step ahead and added a dedicated page per {client,server,library}, if a DOAP file is provided. This happens automatically, of course. On these pages, compliance categories and levels are shown, and supported XEPs are listed (using some of nav's latest additions). Here comes an example:

https://spacecloud.one/upload/230cfa78-bff7-436e-95db-3a3b8fb5237d/prosody-doap.png

wurstsalat: 👍🥰👍🥰👍👍🥰👍🥰

Neat!

Really helpful!

wurstsalat: absolutely amazing thanks for doing all this

wurstsalat: awesome, I guess that will drive us to make the DOAP more helpful