agree wholeheartedly with this - i usually ignore the blog post entirely and just scan the comments to find out what the update is going to be like. if it was more clinical and contained less hyperbolic waffle (“omg awesome wow new this!!!”) i think we’d all be far happier. this is a software update not a carnival concession.
essential notes and info should be succinctly and clearly listed, and the comments are no place for important additional notes - imho.
Too much hyperbole or too cryptic? I find myself agreeing with both. When I gave technical presentations, I’d tally up the comments people left. I knew I’d hit the sweet spot when they were evenly split between “too technical” and “not technical enough.”
The current process and practice has evolved over time. It’s kind of up to the user to figure out what’s important and where to look. Just like all of HA; a very long learning curve.
For example, it took me a long time to realize that “breaking changes” were only a subset of changes which broke something. They are really just intentional breaking changes. Pretty much anything else is a bug, and those are never documented in the change notice. You have to go looking through this forum, Github, Discord, and wherever else people talk about HA to know whether an update will cause you problems or not.
If I’m honest, I agree with you. My point was more that it’s very hard to satisfy everyone. That said, I’m someone on the path of constant improvement, so I always see opportunities for doing things better. It just irks me when people only complain – or are just rude.
A further point on hyperbole: I always saw this as a caveat of this process of a monthly major release cycle. You’re going to lose momentum one way or another and eventually do things for the sake of doing things. I think this is why we’re also seeing that the past 2 releases weren’t huge. I personally think it’s much more sensible to define a handful of big milestones for a year, instead of an artificially relentless pace.
Besides the breaking changes section that I find useful (and often is the first thing I look at when there’s a new release), I think you have a point here: Publishing some known issues. I know all of this is on GitHub, but some kind of ranking of issues and highlighting the biggest known issues might reduce a lot of the noise on the forums.
I have time tried many to update my RPI4 [supervisor.docker.interface same as yours] I normally update through UI not sure how to use the comand line to update do you think this may be fixed in the next update? many thanks
Anyway for assist to not wait until the end of an automation and just accept that it’s happening?
Wanting to use the new sentence triggers for ‘Turn on X device after Y minutes’ (since Google home has stopped it for sockets/switches) but it assist times out after 30 seconds and the automation fails as cancelled
Call a script in the automation so the automation is immediately finished and the delay is in the script. Make sure to use script.turn_on and not call the script directly as the service call
still only seeing release notes through 2023.8.1 on the release page after clearing my cache. I’m sure they will be there eventually, I can wait to update
