version should change after release, not after prior version is tagged

[davidelang]

8.13.0.201509021111-0adiscon1trust1 sorts after 8.13.0-0adiscon1trusty1 so an official release does not replace the intermediate git builds.

A released version should replace self-built intermediate builds.

So either the vesion shouldn't change from 8.12.0 to 8.13.0 until 8.13 is released, or some other change in the string needs to be made so that they sort correctly

[rgerhards]

Mhhh... Its in different repositories (devel vs stable), so this shouldn't
be an issue?

Sent from phone, thus brief.
Am 22.09.2015 20:40 schrieb "davidelang" [email protected]:

8.13.0.201509021111-0adiscon1trust1 sorts after 8.13.0-0adiscon1trusty1 so
an official release does not replace the intermediate git builds.

A released version should replace self-built intermediate builds.

So either the vesion shouldn't change from 8.12.0 to 8.13.0 until 8.13 is
released, or some other change in the string needs to be made so that they
sort correctly

—
Reply to this email directly or view it on GitHub
#27.

[davidelang]

If someone builds their own packages (or installs a devel package), it won't be replaced by the package from the stable repo later.

This hurts testers who try out one (or several) devel versions, but who don't want to be permanently on the devel repo.