# About this demo

THIS SOFTWARE IS CURRENTLY IN BETA, USE WITH CAUTION, DOUBLE CHECK EVERYTHING

This UI allows to see what changes must be applied to your systems whenever a change occurs in the tzdb/zoneinfo/Olson database.

In order to do so, your system must adhere to the following rules:

1. All timestamps must be stored in UTC/seconds since the epoch, leap seconds ignored (as UNIX does).
2. To display a local time, the representation uses some form of the tzdata, and your system/users configure an official timezone name like 'America/Santiago', ie: not 'UTC-4'.
3. You must store somewhere in your system what version of the tzinfo is currently being used, like '2013c'.

Given the above, Choose your current timezone/version on the left (ex: 'America/Santiago', '2016c') and then the new timezone/version on the right (ex: 'America/Santiago', '2017a'). You can choose any other zone, for example 'America/Punta_Arenas', '2017a'.

You can share the URL, Click here for the example above.

Time in software is kind of a mess, so please take that into account. In particular, timestamps after 2037 are not really meaningful (yet!).

# Acknowledgments

• The data comes from our a0-tzmigration-ruby gem, which in turns take the data from the tzinfo-data ruby gem, which in turns uses the original IANA Time Zone Database.
• The cool timeline is from visjs.org.
• The page is powered by VuePress, the demo is coded using Vue.js.