Hi Tim! On Tue, Nov 26, 2024 at 08:07:54PM +0100, Tim Düsterhus wrote: > Willy, > > On 11/26/24 16:48, Willy Tarreau wrote: > > HAProxy 3.1.0 was released on 2024/11/26. It added 41 new commits > > after version 3.1-dev14. > > Congratulations on the release.
Thanks! > I've had regretfully little time / energy to > follow the development and the list in the past year or so (I still owe you > a response on the UUIDv7 patch), but it would not be a proper release > without an email of mine :-) No need to be sorry about that, we all have periods of more busy times and that's normal and expected. Simply don't be shy to come back more often once you have more time again. BTW I indeed remember a past discussion about UUIDv7, but no worries, don't add mental load for stuff that's not on a critical path. > I'm pretty sure we've had this already the last time and you told me that it > was fixed, but the "Changelog" column for 3.1 uses dashes instead of slashes > for the date separator. I just don't understand how I manage to do that each time, especially since I'm duplicating the line and restarting a script. I *suspect* that the full release script vs the dev release just use different formats, which might explain why it reproduces each time. But I could be wrong. I should check them because the date format is inconsistent between release date and the changelog. I used to use slashes a lot in the past until I realized that the dash is more universal and the digits more readable with a dash than a slash. I'll leave it as-is for now so that I can test the scripts. > I'm also noticing that the "Release date" column has > a tilde for 3.0 and 3.1, but now that the versions are relased it's no > longer an approximate date :-) At least this one is caused by my copy-paste of the first line which contains it! I'll adjust my note to put a mention about it ;-) > > - automatic encoding: logs can now be emitted in a structured way, > > using JSON or CBOR, with each field named after its original name or > > via an explicit alias described in the log-format line (using > > "%(...)", see sections 8.2.6 and 8.3.5). This naming will later also > > permit to perform some operations, matching, or on-the-fly > > transformations. > > This is interesting. I did not yet look into how exactly it works, but > perhaps this would also enabled structured logging with systemd-journald, > i.e. this issue: https://github.com/haproxy/haproxy/issues/771? Hmmm possibly. I don't even remember that issue and I suspect I missed it. I'm not seeing anything controversial in it so it should at least have got responses :-( I'll let Aurélien have a look, as he's definitely becoming the log expert :-) Cheers, Willy
