DateTimeZone.forID("EST") returns different iID in 2.12.7 and 2.13.0

[llyuan]

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 version: 2.13.0
• Result of TimeZone.getDefault()

  sun.util.calendar.ZoneInfo[id="America/New_York",offset=-18000000,dstSavings=3600000,useDaylight=true,transitions=235,lastRule=java.util.SimpleTimeZone[id=America/New_York,offset=-18000000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=3,startMonth=2,startDay=8,startDayOfWeek=1,startTime=7200000,startTimeMode=0,endMode=3,endMonth=10,endDay=1,endDayOfWeek=1,endTime=7200000,endTimeMode=0]]

• Result of DateTimeZone.getDefault()

  America/New_York

Problem description

DateTimeZone.forID("EST") returns different iID in versions 2.13.0 vs 2.12.7.

In 2.12.7, .toZoneId() returns EST:

In 2.13.0, .toZoneId() returns America/Panama:

Test case

[jodastephen]

This was detailed in the release notes. The IANA time-zone database decided to deprecate old IDs like EST, and Joda-Time is now auto redirecting the ID.