Development on rdiff-backup has stagnated for the last while. I think
that this is attributable to several reasons:
* Andrew has dropped of the face of the earth, (he's working on graduate
studies, IIRC) and I've been busy with other things. Since we're the two
core maintainers, that tends to slow things down.
* I started work on unicode support, but realized that it requires a
transition period. In current CVS, it's broken just enough to make life
difficult.
* The code isn't structured all that well. This is at least partially
because we don't have good automated tests, so it's hard to refactor
without breaking things.
* We're still using CVS :-)
I propose that we, at least for now, pull the Unicode changes out of
CVS. This is unfortunate for a number of reasons, but hopefully we can
bring back in transition code that will make full support possible.
Additionally, we need to develop a comprehensive test suite that runs on
all supported platforms. Code changes should be accompanied by tests.
Once the unicode changes are pulled back out, I've a fair number of
patches sitting in my own queue that can go in.
Feedback is welcome,
Josh Nisly
_______________________________________________
rdiff-backup-users mailing list at [email protected]
http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
