The March 5th 2023 update was the first update in 2.5 months. And it was made after I wrote my post about this thread losing its purpose.
One update in 2.5 months can’t be considered “regular” particularly when there’s been releases every week or two this year.
As for:
“The more recent posts are mostly others speaking up when they have a problem with a certain Webcore related function, or something is not operating the way they are expecting it to within Webcore.”
Do you really believe it is the best solution for a multitude of support problems to be mixed into a disorganised mega-thread whose topic was intended for update announcements? There is an entire category in the Hubitat forums dedicated to Webcore. In forums like this different issues are usually addressed in individual topics of their own. That’s just how things are usually done. Disorganised Mega-threads like this aren’t helpful.
Just some constructive feedback. That’s not really the issue I care about anyway.
But I do care about release notes being available. I’m a software engineer myself. Releases should not happen without release notes. It’s the duty of the software engineer to provide these. People need to be able to make an informed choice about whether or not to take the update.
I always take the “if it ain’t broken don’t fix it” route so I always look for release notes before I make a decision. Personally I think dedicated read-only threads work best such as the approach taken by the Hubitat engineering team:
