Closed wendigo closed 2 months ago
Historical transitions for Mexico have been updated based on
official Mexican decrees. The affected timestamps occur during
the years 1921-1927, 1931, 1945, 1949-1970, and 1981-1997.
The affected zones are America/Bahia_Banderas, America/Cancun,
America/Chihuahua, America/Ciudad_Juarez, America/Hermosillo,
America/Mazatlan, America/Merida, America/Mexico_City,
America/Monterrey, America/Ojinaga, and America/Tijuana.
(Thanks to Heitor David Pinto.)
The Joda-Time project has been running for many years now, and the codebase is stable. Java SE 8 contains a new date and time library that is the successor to Joda-Time. As such Joda-Time is primarily in maintenance mode and there are few things worthy of being raised as an issue.
As a general rule, you should raise a question at Stack Overflow, not here.
Before raising an issue, please check the FAQs. Please also search Stack Overflow and the issue history at GitHub. In particular, if the issue is Android specific, you are unlikely to get any assistance here. Please bear in mind that I work on Joda-Time in my spare time, so there is no guarantee on response time.
In the unlikely event you still think you've found an issue, please delete the text above and describe the problem as follows:
Key information
Joda-Time 2.13.0
Result of
TimeZone.getDefault()
sun.util.calendar.ZoneInfo[id="Europe/Warsaw",offset=3600000,dstSavings=3600000,useDaylight=true,transitions=165,lastRule=java.util.SimpleTimeZone[id=Europe/Warsaw,offset=3600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]]
Result of
DateTimeZone.getDefault()
Europe/Warsaw
Problem description
In 2.12.7:
In 2.13.0:
28800000
(1 hr difference)Test case