[doctoboggan]

Hi Balloob, great project, thanks for all your work! I've been using it for over 10 years now.

I am wondering if you've ever considered a change to your release rules. Monthly releases are great, but having breaking changes in every release can get to be a bit of a burden. I think it would make end users lives easier if you were able to limit breaking changes to only once (or twice) per year.

I try to read the breaking changes list every time, but sometimes I don't mess with HA for a few months as it's all running smoothly. Then when I do log back in I have a large backlog of breaking changes to review. Usually at this point I just don't upgrade and the problem keeps getting worse. If instead I knew that certain upgrades do no include breaking changes I could more easily keep up to date, and only look more closely at the yearly (or bi-yearly) update that includes the breaking changes.

[balloob]

We've actively managing our backwards incompatible changes, but sometimes it's out of our control (ie an API change). For things we deprecate in Home Assistant, it is a minimum of 6 months period where we print warnings with alternatives. Integrations set up via the UI, will only change for improvement if we can ensure there is a migration path (sometimes requiring adding some extra info).

Some backwards incompatible changes like requiring a new Z-Wave JS version are also able to be managed automatically by Home Assistant. However, because of choice, there are many ways Home Assistant can be installed and we're not always responsible for the installation.

I believe that we can do better in knowing what integrations you use, and mapping that against the integrations that require changes.