Oracle's Commitment to Prevent this Problem from Happening Again

From Oracle Support: The plan is for clients to tag date-time values with a timezone identifier which will be stored in the database. The timezone specified would depend on the context that the meeting is being created in -- usually the timezone for the current "view". Clients would still store UTC values though. In theory, this will allow a calendar server to "fix" some date-time values later on if it knows that certain timezone definitions have changed.