[marcosdumay]

Storing it as an offset from UTC has the effect that the task will run at the wrong time 1/4 of the year.

Now, you'll probably claim that I shouldn't expect time to behave this way. But this is exactly the way everybody expect time to behave, thus, no I won't agree with you.

Anyway, yes, that still does not solve the entire problem. Time intervals are really messy.

[kbenson]

> Now, you'll probably claim that I shouldn't expect time to behave this way. But this is exactly the way everybody expect time to behave, thus, no I won't agree with you.

You shouldn't expect time to behave that way. Cron-like programs also should try to do the right thing. What's really missing is an up-front understanding of what users are to expect when entering a time into a program that supports recurring time. This is a failure of most programs to account for common misconceptions.

This proposal doesn't really help this, as it only detects the instances where we duplicate time, and only where you already have a time zone applied.