IANA time zone database - release management

From annawiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Andy Henninger 2013-09-18 21:36:41 UTC http://mm.icann.org/pipermail/tz/2013-September/020282.html

In an ideal world, from my perspective, changes that affect the present or near future time would be kept separate from other changes, and have a fast-track release process. And perhaps substantial cleanup and historical data updates would be kept away from the busy times in March-April, and September-October


gunther vermeir 2013-09-19 11:02:39 UTC http://mm.icann.org/pipermail/tz/2013-September/020292.html

it would be good to have a public update that keep things more or less as they are until

  • there is a consensus about what to change exactly
  • there is time to test if more radical changes actually break things

Tim Parenti 2013-09-20 04:31:53 UTC http://mm.icann.org/pipermail/tz/2013-September/020304.html


Paul Eggert 2013-09-20 06:43:36 UTC http://mm.icann.org/pipermail/tz/2013-September/020305.html

opening up the development process in this way was probably a mistake. It's slowed development, and made it less fun. And let's not discount the cost of making things less fun in a volunteer project. The large quantity of repeated discussion of trivialities has driven one valuable contributor off the mailing list, a person who in the past contributed more useful changes to the data than anybody in this discussion other than ADO and myself. That's a net minus.