Thank you for responding, but I take issue with your assertions. In fact, you state as much in your own documentation, claiming “We stick to this weekly release schedule regardless of what needs to be released”…….. this is the same flawed logic as saying “we do 3 day sprints”…… WHY? (perhaps you’ve watched too many episodes of Silicon Valley, which is not how quality software is developed). Many of the other assertions are simply dated and/or false. Most reputable companies are backing away from CI/CD (except into testing/staging), because they understand the issues it creates for their customers. Many of your assertions relating to high-frequency releases for products like Chrome (nightly/weekly) relate to canary/dev builds that are targeted at developers, not the general public. Your assertions regarding Firefox, Facebook, Yoast, Elementor, Jetpack are simply false – you might want to check your facts. Firefox is monthly, while the others release in an ad-hoc manner (Elementor, frequent – Jetpack, reasonable).
I’d recommend that you read this: https://hbr.org/2019/01/the-era-of-move-fast-and-break-things-is-over
And this: https://tonyvzampella.medium.com/move-fast-and-break-things-had-enough-yet-d80335149132
In it, there’s a great quote…… “The?Break Things?ideology finds us scaling incompetence and only becoming competent when necessary, on the customer’s dime”
Luminaries from the software world have also referred to the process of strict software release scheduling as “asinine”, “robotic”, and “counterproductive”. See comments from Donald Knuth and Linus Torvalds.
Continue to outsource your testing to your customers (which is what you are doing)…… at your own peril!
