thanks mate, the Lucee teams always appreciate your constant dismissive tone about our efforts I put a lot of time into compiling the release notes and managing releases, don't know how that one slipped thru, anyway the ultimate point of truth is github commits, I put the effort in to tag every single snapshot, so you can always follow the example from all the recent releases notes and pull them up yourself https://github.com/lucee/Lucee/compare/5.3.7.43...5.3.7.48

What dismissive tone? I was (previously, via someone else's identical question on the Lucee forums which came up for me in a google search) directed to that page as where the release notes are for Lucee releases. All good. I checked for two releases 5.3.7.47 and 5.3.7.48 and neither of them were there (I did not cherry pick these btw, they were literally the first two I needed to check for), which indicate that that list is not a reliable source of release notes, as it's... incomplete. These are just facts, and that is how I presented them. It seems to me you went looking for a tone and invented one to react to. And in turn, have adopted a tone in return. Unnecessarily. Still: thanks for the clarification re looking @ git. [checks] Unfortunately I don't think an array of commit messages - which are code and situation specific (eg "error message formatting" to take the first one in front of me) really constitutes "release notes"... they're a bit too granular. What I was after really was a list (or series of lists) alone the lines of:

Release notes for 1.2.3.4

Bugs:

LDEV-123 fixes the thingey

LDEV-234 QoQ ordering on unions fixed

Features:

LDEV-345: added callback param to queryRowData

LDEV-456: added arrayReduceRight

etc

If no such thing exists at that level of accessibility / granularity, that's cool, it's nae bother. It just seemed worth asking about.