diff --git a/NEWS b/NEWS index 9b235a29396..b54538aa4a8 100644 --- a/NEWS +++ b/NEWS @@ -1,14 +1,19 @@ News for the tz database -Release 2023b - 2023-03-23 19:50:38 -0700 +Release 2023c - 2023-03-28 12:42:14 -0700 - Briefly: - Lebanon delays the start of DST this year. + Changes to past and future timestamps + + Model Lebanon's DST chaos by reverting data to tzdb 2023a. + (Thanks to Rany Hany for the heads-up.) + + +Release 2023b - 2023-03-23 19:50:38 -0700 Changes to future timestamps This year Lebanon springs forward April 20/21 not March 25/26. - (Thanks to Saadallah Itani.) + (Thanks to Saadallah Itani.) [This was reverted in 2023c.] Release 2023a - 2023-03-22 12:39:33 -0700 diff --git a/tz-art.html b/tz-art.html index 567953415f6..c86c186c09f 100644 --- a/tz-art.html +++ b/tz-art.html @@ -478,22 +478,35 @@ Supernaw.
tz@iana.org well in advance,
-as this will coordinate updates to many cell phones,
+as this will lessen confusion and will coordinate updates to many cell phones,
computers, and other devices around the world.
In your email, please cite the legislation or regulation that specifies
the change, so that it can be checked for details such as the exact times
@@ -311,8 +311,8 @@ which means they will continue to use out-of-date rules.
For these reasons any rule change should be promulgated at least a year before it affects how clocks operate; otherwise, there is a good -chance that many clocks will operate incorrectly after the change, due -to delays in propagating updates to software and data. +chance that many clocks will be wrong due to delays in propagating updates, +and that residents will be confused or even actively resist the change. The shorter the notice, the more likely clock problems will arise; see "On the Timing of Time Zone Changes" for examples. diff --git a/version b/version index 74a7fa8ae9e..7daa77e00d9 100644 --- a/version +++ b/version @@ -1 +1 @@ -2023b +2023c