<<On Thu, 9 Jul 2015 17:17:15 +0000, Chris Erskine <chris@cerskine.com> said:
Actually, there are reasons to put this out as soon as you can. If I schedule something today that occurs when the change occurs, then my data will be out of sync. Some organizations will be dependent on future times and need the data update ASAP. These type of organizations will try to turn around changes quickly. Other organizations may not care as much so they will not push to get the update.
Of course, those organizations aren't stuck with just released versions of tzdata, either. The countervailing argument is that, for people who are distributing content derived from tzdata, it would be helpful to batch up changes so that they need not run through their release/QA cycles multiple times for changes that will affect only a small number of customers. -GAWollman