Comment 12 for bug 240670

ok, I tested this changes again, this is working for me so far.
I will look at the applet over the weekend.

I'm now sure of a periode of local commit until one remote commit makes sense. Ths means if a user does "only" 5 bugs a day, he will wait at least two days until his bugs make it into the statistic, this seems to be a bit long to me. Reducing this number is also not a solution as this won't reduce the bzr-actions for power-users significantly.

Maybe an additional date based check would be a solution, two possibilities came in my mind:
1.) branch.Branch.open() the remote branch, check for the date of the last rev there and use this date to calculate the time since last remote commit.
2.) put timestamp of last commit in a ~/.5-a-day-lastcommit, not as save as 1.) but reduce remote bzr actions

Another thing is: what about allowing to run ./5-a-day --force without a bugnumber, so if a user really wants to remote-commit the changes it is possible without committing a new bug.

Markus