Well, this seems to me like “taking a canon to go duck hunting”, i.e. doing a lot to achieve a little. Why?
Currently, Fedora runs in release cycles twice a year with Beta being branched some two months ahead of the Beta release with a following one month to reach the Final release. This means, that we have Fedora Beta going on for 6 months out of a year, ergo 50% of the time.
Fedora release validation uses criteria that are divided into three groups, such as Basic, Beta, and Final. The basic criteria should always be met, even in Rawhide, therefore we speak of Always Ready Rawhide which receives a fair amount of automated testing every single compose to avoid the most severe or most critical bugs. We rather succeed in this process so there are no terrible crashes in Rawhide most of the time, and there are people out there running Rawhide with no impact on their work.
For Beta release, we also need to spend quite a time on testing out the Beta criteria to make sure that Beta is stable enough to be released. However, this would not be possible without a freeze period when things are made stable and solid enough to meet the Beta criteria. Usually, the freeze period takes about a week or two, and it is not a quiet period, believe me, so there is not much time frame to release weekly updates for Fedora Beta all year round.
Also, why have two rolling stages, Rawhide (Alpha) and Beta when one rolling stage is sure enough?
If you are interested in newer applications (although I believe that Fedora is a distro that is on the front of the development and our applications are fairly new), you have the following strategies that you can adopt without having to change anything in the global Fedora land:
- Use Rawhide, but set up a testing computer that you will update first, make sure it works for you, if not report bugs that bother you and wait until they are fixed or a workaround found, then update to the latest status quo on your main computer. If more people used this strategy, maybe Rawhide could get stable enough for you to use it as you would like to use the Fedora Beta that you are proposing.
- Use stable Fedora and allow the updates-testing repository. You will be getting new packages, usually two weeks before they hit the stable repository, while you will be able to maintain the stability of the entire system.
- Use Silverblue. You will have the stability of the system and you will be getting the newest versions of applications from Flathub.
As @adamwill already stated, currently there are no idle workforces who would be able to sign up for that much testing to make this proposal happen.