Jon Bjornstad wrote: >What is the best way to get these changes so >we are current?
Simplest is the "cpan" command-line tool: $ cpan Time::OlsonTZ::Data DateTime::TimeZone This updates both of the named modules. >Does installing the latest version of this module >automatically propagate the information >into DateTime::TimeZone? No, they're separate. DateTime::TimeZone has its own copy of the timezone database. DT:TZ 1.29, also based on version 2011c of the Olson database, was released to CPAN about 5.5 hours after T:OTZ:D 0.201103. Dave hasn't been announcing new versions of DT:TZ on the list recently, though he used to. (Looks like Dave's getting around to releasing new DT:TZ versions fairly promptly, by human standards. However, the T:OTZ:D release process is completely automatic, and (if sanity checks pass) releases the updated module within an hour of the Olson release. The first version to actually go out with no manual intervention was 0.201102 (2011b).) The present arrangement is an intermediate state. We've been talking about rewriting DT:TZ to use T:OTZ:D internally, via DateTime::TimeZone::Olson. There are a handful of effects pushing us in that direction. Once that happens, you'd want to update T:OTZ:D rather than DT:TZ. -zefram