Open ylabidi opened 3 years ago
@gonosztopi
I think when a version is released, is a good practice to make new branch with that, and cherrypick bugfixes from master to that branch
I propose for example, next stable version as 2.4.0, and bugfixes can be released inside stable version as 2.4.1, 2.4.2, 2.4.3 ...
and next stable versions 2.5.0, 2.6.0, 2.7.0 ... ...
anyway I think the next version can be done as 3.0.0 because it works with gtk3
I think it's easier to consider the master
branch as the de facto production branch and work with a PR-based workflow to introduce new development. And every time a new release is to be cut, the master branch would be tagged and github will automatically produce a tarball for that tag. Which makes it a lot easier for downstream distros to manage packaging on their end.
Is there a possibility to work on proper versioning and release tags ? The last tag dates back to 2016 and it would help much upstream distros to have a regular release schedule.