Open oleole39 opened 2 days ago
Ah, thank you for consistently educating me on best practices :) Yes, this would be the correct way, and we should do this, going forward. Am I correct to understand that this would apply to all future releases? or are you suggesting that we retroactively do this?
Not sure if/how you can do it for past releases without it being a complicated mess. But that would be great if you were doing it for current release (1.4.0) and future ones, yes.
Hello,
Would you consider creating release tags in Github at each new version? That would help to go back at a previous version easily or for third party use of the repo (for instance I would like to package the app for YunoHost and package autoupdate mechanism would work better with release tags. If not it will have to be based on commits, but technically a new commit is not necessarily a new version).
Would you be not familiar with release tags under Github, I mean:
v.1.4.0