Hello,
On Sun, Nov 17, 2019 at 09:29:10PM +0000, EricZolf wrote:
Hi,
good question, let me try to summarize the current state:
- migration to Python 3 is finished, there are no known regressions.
- we've fixed a fair amount of smaller bugs and cleaned the repo structure
- testing on Linux is done automatically and regularly so that I'm quite
confident about the quality of the code on this platform
- testing on Windows would need more love - anybody is welcome to test who can
compile rdiff-backup
I developed a small build system:
https://github.com/ardovm/rdiff-backup-build
that makes an self-contained EXE file (as did previous stable
releases) starting from the sources of librsync and rdiff-backup.
It can also make self-contained binaries for Linux, and possibly other
Unix-based systems (to be tested).
Contributions, comments etc. are of course welcome.
[...]
Writing these lines, I realise that I should try to generate a beta release
(even if only manually) so that people can more easily test, without the
trouble of compiling the code.
I was also expecting this. IMHO it is better to have a release tag,
alpha- or beta- is ok, but it must have a name, that we will be able
to refer to in bug reports etc.
Once we have the tag, I could help generating the binaries, if you
think it would be useful.
Best regards,