I wonder if V1 could move to semantic versioning of the releases. Semantic versioning reduces the barriers to understanding the importance of a code update, and makes it easier to spin-off code branches into maintenance mode. In particular, it makes it easier to backport fixes without creating new releases for mainline code.
For instance, seeing as Archim is en route to deprecation as a result of of several upstream choices which have impacted the project negatively, it’s completely reasonable to stop the development at 507, which is the last fully-supported Arduino version. However, an important fix was added in https://github.com/V1EngineeringInc/MarlinBuilder/issues/44. Because there is currently a monolithic sequential release tag, the bug fix wound up getting bundled into a new feature set. Ideally, this would have been a patchfix on top of the major.minor branch.
I don’t want to get too verbose, in case this is already something the devs have considered. https://semver.org/ explains it much better than I could anyway.