Or alternatively, follow a strict release cycle, ie, once a year and publish that. Have all standards follow this cycle. The choices aren't "commit everything

Or alternatively, follow a strict release cycle, ie, once a year and publish that. Have all standards follow this cycle. The choices aren't "commit everything to master" or "commit everything into various versions". A strict release cycle also prevents having some hype extension which only a few people actually use since it takes more effort and dedication to get stuff into the standards.