Confusing release versions across the downstream package ecosystem

[luzpaz]

Here's a snapshot of the current downstream distribution of gpredict in the package ecosystem:

Ignoring all obsolete and unique entries, notice that there is a mixture of 2.2.1, 2.3, 2.3.x

But we don't see any mention of 2.3 in Github, the release version shows v2.2.1. The NEWS file shows 2.2 (no mention of the minor version 2.2.1 or 2.3).

Would it be possible to bring more uniformity to this situation ? TIA!

PS JFYI, Sourceforge https://sourceforge.net/projects/gpredict/files/Gpredict/ shows:

[csete]

2.2.1 is the latest stable release. 2.3-x are development snapshots from git, and because 2.2.1 is very old now, some distributions have started distributing these snapshots.

[luzpaz]

Thanks for the reply. Would it be possible then to keep the NEWS file up to date? (Adding 2.2.1)