Currently there exists a script that creates the timezones.sqlite database file from the zoneinfo database (mozilla\calendar\timezones\update.js). I suggest to add the zoneinfo sources (e.g. zone.tab, ...) used to create the database to the calendar source code repository. This would allow better handling in case of updates, e.g. to check what changed between the used zoneinfo releases, if locals are correctly updated, compose dedicated test cases for changed timezones, etc.
I don't like this approach, since it requires to update/patch a lot of files on updates and I don't yet see any benefit, because the checked in timezones.sqlite can reflect all this data. For a quick overview, I think it's sufficient to attach the update logs to the corresponding bug (as I did last time), so we know what has changed.
How many source files do hold the timezone data? From looking at the script it seems that just zone.tab is required?
The zones.tab file just holds longitude/latitude and TZIDs, no timezone definitions.
Resolving as wontfix based on previous comments.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.