Sounds like a good plan. I'll get the CHANGES file up to speed with the changes committed so far since the 1.3.2 release. Michael On 08.09.2022 22:08, python@altfeld-im.de wrote:
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" _______________________________________________ Bit-dev mailing list -- bit-dev@python.org To unsubscribe send an email to bit-dev-leave@python.org https://mail.python.org/mailman3/lists/bit-dev.python.org/ Member address: foss@michael-bueker.de