Eli Carter wrote:
> All,
>
> I'm coming to the conclusion that r6012 isn't sufficient to solve #6028.
>
> Having a due /date/ for a milestone is ambiguous once you have users in 
> different timezones.  The due date is taken to be midnight in the setting 
> user's timezone of that day.  When another user only one timezone away looks 
> at that same due date, they may see a different date.
>
> If we specify that the date given is taken to be midnight UTC on that date, 
> the date the user sees may not match the date entered.
>   

If you're talking about different users, then there's no way to ensure 
they will all see the same date, whichever time of the day is chosen.

> I think we really need to make the due date be a date and time.  That avoids 
> the ambiguity.  (It has a plus for businesses that want to specify midnight 
> or 'end-of-business' of a day as when it is due.)
>   

That's a slippery slope leading Trac down the way to micromanagement ... ;-)

More seriously, I don't see how picking up a different starting point in 
the day would help in this case. There will still be users that will see 
a different "date" than the one which was originally entered. What is 
useful however is to remind people about the timezone issues, so maybe 
what we can add to r6012 is to show the full datetime information 
instead of just the date. That's already the case for all displayed 
dates in tooltips btw., just not done in the iCal output.

Maybe the "perfect" solution would be to show to everybody the due date 
using the timezone offset of the user who has set that due date (the 
release manager?), but there's no way this could be done using the 
current schema.

-- Christian


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to