A few years ago, I was working on a legacy system that required preparing changesets for a release by hand. There was no version control. The entire release workflow was manual. The release sizes were massive. During those days, it was given that a release would take an entire day. We were averse to Friday deployments then.
Fast forward a few years, we now have version control, a proper CI/CD with rollbacks for failure and small well-scoped releases. Cutting down the release sizes had two positive effects: easier rollbacks and, quick and precise feedback about the release's status. These days, we release things whenever they are ready and Friday is no different than any other day.
Completely agree. Also, we have significantly lower usage on Friday into the weekend. Would rather catch a bug and quickly rollback Friday with fewer users impacted, rather than arbitrarily force devs to wait until Monday to queue up their releases during our peak usage.
As in most things, context matters. Tired of "always do x" and "never do y" opinions.
Fast forward a few years, we now have version control, a proper CI/CD with rollbacks for failure and small well-scoped releases. Cutting down the release sizes had two positive effects: easier rollbacks and, quick and precise feedback about the release's status. These days, we release things whenever they are ready and Friday is no different than any other day.