Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: Timezones and versions of Java Followup-To: comp.lang.java.programmer Date: Fri, 27 May 2011 13:09:51 +1200 Organization: Geek Central Lines: 23 Message-ID: References: NNTP-Posting-Host: 118-92-95-178.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1306458591 9526 118.92.95.178 (27 May 2011 01:09:51 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Fri, 27 May 2011 01:09:51 +0000 (UTC) User-Agent: KNode/4.4.7 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4623 In message , Stanimir Stamenkov wrote: > Wed, 25 May 2011 19:49:18 +1200, /Lawrence D'Oliveiro/: > >> In message , Stanimir Stamenkov wrote: >> >>> Java has a TZupdater (Timezone Updater) tool which takes care: >> >> So the answer is “no”: you need to download, install and run a separate >> tool to apply a patch to fix it up. >> >> How many people are going to bother with this? > > People who care or need it, people maintaining servers. Production servers? Are you really going to roll out a code patch willy- nilly across all your production systems? The problem is, why does Java need a CODE patch to apply a DATA update? The tzdata patch I referenced is just a data patch, no changes to any code at all. That’s why folks like Debian feel safe classifying such updates as “volatile”, being immediately applicable even to production systems running “stable” installations.