My local Jenkins alerts me regularly about new Jenkins releases and links to the Jenkins changelog at https://jenkins.io/changelog/. That changelog often does not contain the changes of the version announced (yet). Therefore I cannot take an informed decision about whether I need to upgrade or not.
Example: The alert says 2.183 is available right now while I write this. The changelog only contains 2.182 and earlier. By tomorrow the changelog might be updated, so I will also defer my local upgrade at least until tomorrow.
This is how it works at the moment unfortunately. The releases usually happen on Sundays, but we do not always prepare changelogs in advance. So there is a lag between a release and a changelog availability.
If you need to make a decision without changelog, there is always a commit history. Changelogs are just a fine-tuned version of the pull requests we integrateover the week.
If you want a changelog on the weekend, you'll need to write it yourself. I've done this for way too many years, now someone else gets to sacrifice their weekends and days off for no reason.
If you want a changelog on the weekend, you'll need to write it yourself. I've done this for way too many years, now someone else gets to sacrifice their weekends and days off for no reason.
To elaborate: While it's _possible_ for anyone to prepare the weekly changelog (except merge the PR, but there are people who do that), with very few exceptions, it's been exclusively written by Oleg or me for the past four years or so. Nobody else bothers.
Which means that when we're out on Sunday, and otherwise busy (or off) on Monday, there's not going to be changelog on Monday.