I would keep it to Journal, unless it's the actual change log from the source tree
Internally, it's tightly linked to the source tree; we commit a file into a particular branch of Houdini and some automated systems assemble the log messages into a database and upload them to the web site.
It's definitely not as tightly linked to the source tree as our commit logs, but that would be too much information to sift through, hehe. Instead, it's a chronologically ordered list of notable changes for each build of Houdini, which is, well…, exactly how they describe a change log here: http://keepachangelog.com/ [keepachangelog.com]
Journal seems more appropriate to me given that the information contained in it is not automatically generated and is generally a partial/incomplete list of changes. It's essentially kind of like a “highlights” list.
Agreed, definitely not automatically generated and only showing notable changes. …But again, that's exactly what a change log is.
Or you know, make it an much more accurate and complete change log
Hehe, the intention of it is to be accurate and complete, so if we're missing important things then it's a failure on our part, regardless of whether we call it journal or change log.
Mostly, I'd like to remove one more, albeit small, barrier for new users coming to Houdini by avoiding terminology that's different only for the sake of being different. I slightly worry that those users may not even be seeing this forum post, though, so we may not capture their voice.