I read this topic and was amazed, as I know the Brume 2 stable firmware is 4.7.4 but a beta has been available for a long time: 4.8.2.
To my surprise, there is now a second beta firmware available for the Brume 2: v4.9.0.
From a release management perspective, I don’t understand this. Even though I am happy there is a v4.9.0 for the Brume 2, how come 4.8.2 is still in beta? What is required on GL iNet side to release a beta version into the stable channel?
Would it make sense for a user who wants to test to try 4.8.2, or should that version now be ignored?
Many questions, just trying to understand
(I have the Brume2 at home (as Wireguard and Tailscale server and NextDNS DoH) and the Beryl AX on the go.)
A beta version is only promoted to a stable release after it has gone through sufficient testing, including our internal validation processes.
The MT2500 v4.8.x branch had already gone through several rounds of testing, but it is not yet considered stable enough for an official stable release. At the same time, we introduced the v4.9 branch, which is why you currently see both v4.9 beta and v4.8 beta versions available.
The main reason we keep v4.8.x available is that some users may have been running it for a while and have already confirmed that it is sufficiently stable for their particular use cases. If they upgrade to a v4.9 beta build and encounter issues, they can still roll back to a version they know works well for them.
For users who are planning to test a beta version now, it is fine to start directly with the v4.9 beta release.
