[Box Backup-dev] Error logging

Martin Ebourne boxbackup-dev@fluffy.co.uk
Tue, 19 Dec 2006 10:36:00 +0000


Chris Wilson <chris@qwirx.com> wrote:
> "Please add some code to the client to log on what BackupLocation, =20
> Path, and sub-directory it is working. We had a bbackupd.conf with =20
> <...>
>
> I consider this a bug, since Box Backup was not working and did not =20
> provide enough information to help fix the problem. I've committed a =20
> fix to my merge tree:
>
> [http://bbdev.fluffy.co.uk/trac/changeset/1222]
>
> I know that Martin is against adding random feature requests as bug =20
> tickets, and I can see why, but in cases like this, I would suggest =20
> that we encourage people to add them, and that we create a ticket =20
> for this one. Comments?

Yes, I am against people adding random feature requests in trac, but =20
if there is a feature that one of the box developers is definitely =20
planning to implement then trac is the right place to record this and =20
track it - a task ticket type is best for this. (You'll see I have a =20
couple like this assigned to me already.)

This one is on the fringe between bug and feature request - the code =20
is not broken because it is working as designed, but this is =20
definitely undesirable behaviour. I think an error handling revamp =20
would be an important improvement in the next major version.

It is a good idea for people adding feature requests on the wiki to =20
drop an email to the box list to alert people to the idea. I've =20
updated the TicketHowto to suggest this.

Cheers,

Martin.