I think you misunderstood me. I wasn’t talking about rushing anything. If you read my various posts and this one too. I am saying you should pace to a higher rate of release which would lead to much greater software quality by taking smaller steps each time. Right now we are observing long intervals between releases and very large amount of changes which are poorly tested and as far as the community can see… poor quality. You don’t need to rush anything to release bad quality… Look at the vera history
If you take smaller steps… say only a handful of commits between releases and allow your community to beta test it so you can fix them before general public releases which would be at a much higher rate, you would get a greater community participation and firmware quality.
As I see 7.0.30 is way too ambitious to be taken as a single step for example. The content could and should have been split into 3-4 releases. The work @edward has done on the luaUPnP program alone could have been 1-2 general public releases which would have greatly improved stability of a large number of customers. It is all about how you manage it… You are taking the risk to have much bigger release increments, much more difficult to troubleshoot for your teams and lower quality overall, as well as a less active community.
For comparison, Home Assistant has a public release every 5-10 days… The state of their software stability is leaps and bounds better than vera, granted with much greater resources. If you could get to a rhythm of even 1/3 of that, you would be in a much better place.
Hubitat likewise when I was following them had a new firmware release every week. No matter how small the changes were. They enabled us to test it and if buggy, get reverted or fixed the following week.