Release candidate for BiT v1.4.0

[aryoda]

I have now prepared a new release.

I discovered and fixed one bug too (incl. updating the CHANGES): #1532

Please review my changes so that I can apply forgotten changes or fix other issues.

Next steps then:

1. Squash-merge PR into dev branch
2. Create a Github release using this merge from dev
3. Squash-Merge the dev branch into release (may not be required in the future if the decide to tag-only
   but currently external package maintainer may still watch or use the release branch for package updates)
4. Prepare and merge another PR to increment the VERSION number and CHANGES in the dev branch
5. Announce "end of code freeze" to all developers via email
6. Optional: Create tarball and Debian package
7. Inform known package maintainers about the new release
8. Create new PR containing my new "how to prepare a release" documentation

[buhtz]

Looks fantastic! 🎈

Just minor changes.

[aryoda]

2nd round:

• I have added our real names into the AUTHORS
• "known problems" are now correctly partitioned into "latest release" and "older releases" in README

[buhtz]

7. Inform known package maintainers about the new release

To my knowledge this should happen automatically via the distro package systems. It is the cause with Debian (watch it) and Arch (watch it @AUR) for sure.

But you can add "Announce the new release on bit-dev mailing list" to your list. 😃

[aryoda]

Does someone know if and where we host the Sphinx documentation of our code (not the end user documentation but the doc of the code functions)?

It may also need to be pushed in sync with the release then...

[buhtz]

Does someone know if and where we host the Sphinx documentation of our code (not the end user documentation but the doc of the code functions)?

Yes, it is also ReadTheDocs. The projects name is "backintime-dev" (in the URL) or "BackInTime-Dev" (in the web-frontend). In this screenshot only the two first entries are relevant for "bit-team".

It may also need to be pushed in sync with the release then...

This happens automatically. In the current setup the code-docu is build on every commit on "dev" branch. In the bottom right on this screenshot you see that "dev" branch is connected to "latest" (kind of a version name on RTD).