This is EXTREMELY irresponsible
It cannot be fixed across what you call all versions as I have said before - there is only one version system for cPanel, the builds are simply milestones within that version. If you want protection you'll simply have to go to EDGE at this stage. If you want to know when the other trees versions will change, you'll have to contact cPanel. Having cPanel simply change RELEASE to the version that EDGE is at doesn't do anything at all except change the number, nothing in the code will change for it.
Here's what you said:
When a new "edge" version is released, the current "edge" becomes the new "release" version, and the current "release" becomes the new "stable" version.
This means that:
It is EXTREMELY DANGEROUS to run anything other than the "edge" version. Here's why:
When a bug in the "edge" version is fixed in a new "edge" version, all you did is push the bug from the "edge" version to the "release" version where the bug will remain until you do another "edge" release.
When the next "edge" version is released, now the bug has been moved to the "stable" version where the bug will be active until the next "edge"version is released.
The"edge", "release", and "stable" version names are quite misleading.
I'll bet that most cpanel customers think that the "edge" version is a release candidate and that any critical bugs found will be fixed before it becomes the "release" version and that any further critical bugs in the "release" version will be fixed before it becomes the "stable" version.
How often do you do new "edge" versions?
Don't you think it is irresponsible to push a bug from the "edge" version to the "release" version, to the "stable" version?
When the bug is a security exploit, that means "release" version users have a higher chance of getting exploited, and "stable" version users have an even greater chance of getting exploited because the exploit becomes more dangerious as more and more hackers discover the exploit and attempt to hack servers with it.