On Fri, 2023-02-03 at 08:28 +0000, c.buhtz@posteo.jp wrote:
Am 02.02.2023 17:44 schrieb BiT dev:
I think our released version 1.3.3 does still show the "dev" postfix when asking for the version number via "backintime --version":
https://github.com/bit-team/backintime/blob/8495f9dc3953343a0352bb3ffbdcfab7...
Moin. I don't think so.
"main" says "1.3.3" https://github.com/bit-team/backintime/blob/e22c7f253fa048fab9119f4cbea34c0f... or https://github.com/bit-team/backintime/blob/main/common/config.py
I have discovered the "v1.3.3-dev" release in wild while hunting an Arch Linux error.. It's no big deal at all and the only reason I am mentioning this here because we will get new issues for 1.3.3-dev which *may* be in fact the release version 1.3.3. The reason for this is visible in the commit tree (see screen shot): - The Git tag v1.3.3 was added first (and the config file still contains "1.3.3-dev") - The release commit incl. the config file change to "1.3.3" was done AFTER that The github "release" (which is NO Git but a Github concept!) is referencing the Git tag v1.3.3 (not "main"!). To prove this I have downloaded the zipped source code from the "Github release page" and checked the config.py file: https://github.com/bit-team/backintime/releases That is why all distro packages will publish the BiT release as v1.3.3-dev now ;-) Again: No big deal, we just have to be aware of this in case of issues... I think for future releases we have to prepare everything (incl. version numbers) first in "main" (or a relase candidate branch that is merged into "main" finally) and add the release Git tag AT THE END. Optionally we could patch this and inform the package maintainers (we mostly don't know I guess).
