![](https://secure.gravatar.com/avatar/916b389318a09b18b023ea87c76d9466.jpg?s=120&d=mm&r=g)
8 Sep
2022
8 Sep
'22
8:08 p.m.
Definitely, I totally forgot to do this here in my PRs! Can we (for now implicitly) stick to the policy the merge PRs only with extensions of the CHANGES file under a https://github.com/bit-team/backintime/blob/master/CHANGES If 3rd-parties contribute we could update the CHANGES ourselves after merging the PR. After each "release" the VERSION file must be increased and the CHANGELOG file updated: - Subsume noted changes for the released version. - Add new version number with hint "work in progress"