Each library is maintained in its own repository, allowing decentralized ownership and independent release cycles.

The rationale for branches is simple. Each snap in the Snap Store has a default track called ‘latest’ in which there are four channels named ‘stable’, ‘beta’, ‘candidate’ and ‘edge’. These are all typical buckets in which snaps are published for an extended period, perhaps months or maybe even years. Branches on the other hand are short-lived silos for publishing snaps. 

In the rolling-release model that most browsers follow these days the alpha -> beta -> stable cycle is short so the typical "alpha slowly gets more stable & when it gets stable enough we mark it as beta" model doesn't and cannot apply here.see more0

This issue is going backwards in the process, not forwards. Surely, Gitlab should be focusing on things that have already been allocated milestones, especially ones that have had milestones pushed continuously for 3 years. You can argue that it shouldn't have had a milestone added in the first place, but maybe Gitlab should focus on clearing the "backlog" of issues that have already been issued milestones, and backlog new issues until some of the older issues have been solved.

Ubuntu 20.04 LTS