Re: The snag with a four-week release cycle ...
Erm, they don’t code everything in four weeks, that’s just the release process.
A feature or change can have been worked on for 18 months in a separate branch, compiled, tested etc. Only when they think it’s ready for alpha does it go to alpha. Some changes stay in alpha multiple cycles if issues are detected there. Then beta, where they can still sit multiple cycles if needed.
The benefit of a release cycle like this is that, once you know it’s ready, you don’t have to wait some arbitrary time until some other team has completed their unrelated code that just happened to be scheduled together with your team’s code.