Wirelessly posted (Mozilla/5.0 (iPhone; CPU iPhone OS 5_0 like Mac OS X) AppleWebKit/534.46 (KHTML, like Gecko) Version/5.1 Mobile/9A334 Safari/7534.48.3)
Btw, WHY can't apple get DST right? How hard is it?
Because this problem is going to happen with almost everything, every time.
You've got hundreds (maybe thousands) of laws defining DST across the world, all different, differing based on what country you're in, what territory/state you're in, and even what city you're in. These change frequently, and often on little-to-no notice. (I believe Russia decided not to call off switching from DST this year, two weeks before it was supposed to)
In addition, you need that massive database to keep track of all the timezone shifts, and that database may not necessarily be guaranteed to be accurate, or even available. The one for Linux was DMCA'd on a copyright dispute for a couple weeks about a month ago.
In short - "What time is it?" is probably the most deceptively difficult question you've ever asked someone in programming.
---
This isn't an argument for Apple - just a contextual argument on the general subject of time in computing. I would assume the bug comes from these devices basing their Time Zone information on certain information, and when daylight savings occurs, they don't ping out to get that information again for a good while. (i.e. their geolocation and their pinging of time servers aren't connected)