use tags for formal releases about osmand

[pavolzibrita]

You can probably use the information in jenkins release job, like here: https://jenkins.osmand.net/job/Osmand-release/32/

[vshcherb]

Just in FDroid case :

1. OsmAnd is not LGPL. It is combined license but source code is covered by GPLv3
2. OsmAnd~ should be published on FDroid, simply because it is not signed with developer certificate.

To publish OsmAnd~ I suggest to use/build one of the nightly build of same date. Actually it could be downloaded from nightly build of that date... I think every release I will create a branch (but not a tag) for maintenance.

[pfalcon]

1. OsmAnd~ should be published on FDroid, simply because it is not signed with developer certificate.

Did you miss "not" somewhere there?

[vshcherb]

Sorry,
OsmAnd is good to publish on FDroid, becuase it is signed with developer certificate (not production)...

[pfalcon]

Thanks for confirming that you're not against publishing on FDroid ;-). But the whole idea of FDroid is to be source-based, and build the apps from scratch, and then FDroid needs to use own keys to sign the binaries.

[dalb8]

With release v1.0.0 the version code is in v1.0.0 branch is 90. A recent commit in master says "release 1.0", which bumps the version to 1.1.0, version code 110. The Jenkins build is from the release 1.0.0 branch but builds version code 99, which is what is on the playmarket. How can these contradictions be explained?

[ruzenkadev]

It is not contradiction. The release is made from the commit before. The commit denotes, that a release was made, and changes the parameters for next release. So now on, the master branch is 1.1.0 alpha stage, because the code before was released as 1.0. Probably the naming could be better, if you know the process behind, it should be not confusing.

[dalb8]

But there is no commit corresponding to version code 99 anywhere. The r1.0.0 branch just got a critical bugfix, yet it is still on version code 90

[ruzenkadev]

yeah, nobody is perfect, probably victor just didn't commit it anywhere, it is just a build:
https://jenkins.osmand.net/job/Osmand-release/71/

[dalb8]

That's ok, the commit info is there, even though the version codes don't match.

[ruzenkadev]

It is changed only in the release build, but not committed. Probably we could do auto tag and commit, but it is not worth of much for this project and developers...