changelogs

[bsdlp]

It looks like commit messages are just version messages. It would be great if versioning was left up to git tags, and commits were a summary of what was changed.

Alternatively, changelogs

[alexei]

👍

[pklink]

+1

[RainLoop]

👍 :)

Every commit is a new version.
With this approach, there is no sense in git tags.

Now the development of the application is a bit chaotic :).
New versions come out every day and so we do not pay attention to changelogs.

Later, we will post changelogs for new versions.

Thanks.

[alexei]

The main point here, I think, is people don't care about version numbers. They might, however, care about changes in the program. In that regard, commit messages such as "implemented feature X" and "fixed bug #5" are much more useful than, say, "v1.2.3.4". So the suggestion is to use meaningful commit messages and create a new tag every once in a while.

Regarding the chaos: one common approach is to use the Gitflow workflow or something similar, where "master" is the production-ready branch, "develop" is the development branch (i.e. work branch) branched off of "master", and features and hotfixes are dealt with in "feature-" and "hotfix-" branches branched off of "develop" and "master", respectively.

[RainLoop]

Githab repository - it's just a mirror for releases.
In working repository we use Gitflow workflow.

[dvbmgr]

So this is completly useless. Just keep it on your own server(s).