Update website.rst: Packages no longer out of date

[Lesik]

The stable/LTS (recommended) distributions of Debian and Ubuntu contain gtimelog 0.11, which according to the releases page of this repository is the most recent release.

As the popularity of a piece software among GNU/Linux users often depends on whether or not said software is included (and up-to-date) in their distribution's repository, I propose to update the gtimelog website to reflect this fact.

[Lesik]

Additionally, I think it's wiser to recommend the official repositories first, then refer to pip.

[mgedmin]

Yes, but it's 0.11.0, with known bugs that were fixed in newer releases. Even eoan only has 0.11.2. (0.11.3 was released to PyPI in April.)

I agree that pip does not have the best user experience. Or the PPA (especially given that it's outdated too, I need to automate so many things ....). My best hopes for user-friendliness and a non-outdated version is a flatpak on flathub, which is slowly coming along (#106).

I keep forgetting that GitHub releases exist. I wonder if there's a way to automate updating them when I make new releases on PyPI? I should at least add an echo Go and create a GitHub release, you absent-minded numpty reminder to the Makefile for the release rule.

[ericzolf]

Our Travis.yml at https://github.com/rdiff-backup/rdiff-backup is perhaps not the nicest one but it does the job and you can ask me if you need help.