Hey everyone, I was looking at the remaining tickets for the release of Tracks when I came across this issue:
http://dev.rousette.org.uk/ticket/584#preview I was able to reproduce the bug behavior that the user reported. The issue is occurring due to a known issue with the TimeZone library that comes bundled with Rails. See http://dev.rubyonrails.org/ticket/4551 for more information. I would like to install the plugin tzinfo_timezone as it, unlike the TimeZone library, supports Daylight Savings Time. However, it requires the tzinfo gem and I'm not sure what the Tracks project's policy is on requiring users to do things like install gems. Or if there isn't one, what it should be. I didn't feel comfortable installing a plugin that would require users and developers to install the gem. What do you all think? Thanks! Jacqui As a sidenote, if we agree that using a time zone library that supports such modern (hehe) concepts as DST is the right thing to do and I switch it, I would need to change calls to the TimeZone#adjust method (as seen in http://www.rousette.org.uk/svn/tracks-repos/trunk/tracks/app/models/user.rbline 153 in the time method) to call utc_to_local instead. I didn't see any calls to TimeZone#unadjust but those would also have to change to local_to_utc. This isn't a big deal at all, I just wanted to make sure I documented it along with the rest of this info in case I forgot.
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
