Lack of properly tagged releases in git / signed source tarballs.

[MrElendig]

Several times now, last with 4.8.6, releases have been made on the download page[1][2] without them being tagged in git. Combined with a lack of (signed/check-summed) source tarball on the download page that makes packaging stable releases of opencpn infeasible.
Linking to a branch[3] on GH is not good enough since that doesn't tell us exactly where in the history/from which commits the release was made.

[1]https://opencpn.org/OpenCPN/info/downloadopencpn.html
[2]https://web.archive.org/web/20180829175255/https://opencpn.org/OpenCPN/info/downloadopencpn.html
[3]https://github.com/OpenCPN/OpenCPN/tree/o486

[tchiwam]

Holding for the version bump in our systems for the same reason.

[greno4ka]

Ping?

[bdbcat]

Hello...
I understand the issue. The point at which branch o486 was forked was not tagged in master. Subsequent changes were made in branch o486. As a result, the actual release content of o486 is not in master. It only exists in branch o486. So a back-tag of master will not help much today.

Branch o486 is tagged at the proper point, if that helps.

Dave

[nohal]

Dave...

The tag does not have to be in master. What o486 branch is missing is the last commit actually changing the version number and then the v4.8.6 tag.

Pavel

[bdbcat]

Done.

Was done locally, just not pushed. Sorry for the lag.

Dave

[nohal]

I have tagged it and created a release.

Closing until next time ;)