On 3/26/25 13:40, Dale Ghent via tz wrote:
I have two options:
And you make good points. However, there is a third option, which I mentioned in [1]. It generates a version number that indicates the "in-between" nature of whatever commit is used and this should mollify (at least to some extent) more astute customers.
For example, with TZDB commit 486e1e890e68d52f9236b2b354484463f57ec692, which is immediately after TZDB's Paraguay changes in October, the third option generates TZDB version 2024b-10-g486e1e8, a version number that sufficiently-astute customers can comprehend.
There is no perfect solution here. Releases are to some extent arbitrary and there is no universal agreement on when they should happen or what should be in them. Some downstream users would prefer releases to be rapid and often; others, not so much. Downstream users that prefer more-rapid releases than the "official" ones can use this third option.
[1]: https://lists.iana.org/hyperkitty/list/tz@iana.org/message/334HGRQ7KWM3JBRVPNCYPHQS7SKSD5FV/
