What is going on with the development team? Is anyone in charge of release cycle with 4 releases in 7 days during this Christmas break? Is anyone doing full regression testing on these releases? It is starting to looking like an Android app development team with a new broken release everyday! Not cool!
Each of these releases has been tiny clean-up hot fixes. All thoroughly tested. We are right at the end of the 2.3.7 release cycle. This is not uncommon as we finish up.
And you don't need to update if everything is running fine.
This is common after a new major release (regardless of time of year), as just happened with 2.3.7. FWIW, many of these changes plus the entire last release you noted are minor enhancements to new-ish features rather than bug fixes. This release had some big changes under the hood that the variety of setups in the beta group apparently still didn't catch (though if you enjoy this kind of thing, you can normally join when they have one).
If you want to wait until things calm down, waiting a week or two after initial release will normally do that. As you know, if or when to update is entirely within your control.
While it may not have been the case here, or maybe it was... A rapid set of releases, does not necessarily mean the changes were all crammed into that timeframe, some could have been worked on over a longer period and simply reached the point where they could be released shortly after other changes were completed. There can be overlapping streams of development and testing happening at the same time.
Further to what @bertabcd1234 says above, 145 is tentatively the last 2.3.7 hot fix. We had thought 144 might be it, but had a long weekend to find a few more nits...
Hopefully, 2.3.8 beta will come along soon. It's planned to be a small-ish release with a relatively short release cycle -- pending how beta goes.
Just to note... Most major iPhone upgrades are followed by a bunch of small fix packages... Mister Android Developer trash talker.
I am just impressed with the Hubitat Team for getting these fixes out during the Holidays!!!
Thank you, Hubitat Team.
@bravenel
I for one welcome the hotfixes even after the release.
We Beta testers can't find every glitch; it takes a thousands of users to see into the dark corners.
Well done team.
Somebody better tell @gopher.ny to stop working so hard…
@pgreen you're like me and feel compelled to do every upgrade, but are a little annoyed at the frequency you could do what I did and automate the upgrade process.
It checks for an available update, and if there is one available, it emails the details, then performs the update.
So is 2.3.7.x stable now?
I’m home from vacation in a few days and I’ve been restraining myself from from doing a remote upgrade on my hubs.
Ive been looking for this for YEARS!
As you can see in this post, Ive been quite frustrated with the lack of auto-update in Hubitat. Well, now my Pi successfully auto-updated the Hubitat! Now I'm down to ZERO manual updates in my IOT system!
I owe you a coffee!
Sounds like we have come full circle from the OP
For something as important as your home automation hub, auto updates are not really a good idea. It’s safer to send yourself a notification when there’s an update available and let you choose when to do it.
I can only recall one breaking update that was withdrawn by the Hubitat team, but my point is, no software release is perfect.
I can VPN into my home network at any time to run updates, but I would rather do it while I’m at home - Just in case something doesn’t go to plan.
I agree, but for me this comes down to conflicting neuroces. On one hand, if it ain’t broke, don’t fix it. On the other hand, I always like having the latest and greatest. In this case, the latest and greatest won out.
My finger hovers over the update button but I always back down due to the family traffic that comes though my home though the Christmas and New Years Holiday. I love it that I get to choose when to update with the Hubitat and that the hot fixes are quick updates. I have a general rule to only update if the bugs fixed are something you need or is security related. Before my C4 died I only did an update about once per year. With my C7's I usually update in January with the end of year release and then watch the notes for the updates.
All options are equally valuable. I certainly fall into the "send me a notification" camp, but would not want to deny people the option to sit on the bleeding edge, with all the "eyes wide open" that is involved. Living alone I could probably be in the "to hell with the consequences" camp, but I would still choose to control the changes I even inflict on myself... Though now I think about it, I haven't chosen that option for updates in HPM.... somehow I seem to trust Community dev's more than those in charge of the platform.... Hmmm.... we don't release any breaking changes do we...?
I do too, but I wait a couple of days to ensure there were no serious escaped defects in each release.