duplicity-team team mailing list archive

[Kenneth Loafman <kenneth@xxxxxxxxxxx>]

Michael Terry wrote:
> 2009/8/5 Kenneth Loafman <kenneth@xxxxxxxxxxx>:
>> So far, so good on the feedback.  Don't be afraid to complain if I'm
>> doing something wrong.  I guarantee it won't be the first time.
> 
> So long story short, please consider how any change affects users that
> don't have direct access to the duplicity command line.  I assume you
> originally imagined users just changing their cron jobs for the next
> full backup, so you didn't worry about it.
> 
> This has gotten better!  I again cite the happy willingness to have
> duplicity sync caches without user intervention.  But for a while, it
> was touch and go, with users having to delete their cache directories
> if there were any sync mismatches.

Very good feedback!  I do appreciate it and I think that the process
changes to a one week code freeze will help.  But more importantly, I
think we should publish plans for major changes through the Blueprint
and Milestone mechanisms on LP.

Again, thanks for the feedback, it helps.

...Ken