Software life cycle and release management (re: auto upgrade)

Regarding “v7.4rc1 is released!”

I have to admit that I really don’t understand how the current release management process works and the underlying mechanisms behind the scene for this release.

Can someone with some insight please explain to me how MT reasons when they choose to push a test version as a new “Release Candidate” where there are 1) new functions added, 2) plenty of new fixes and 3) old flaws needed to be corrected, instead of just continuing to iterating in “Test channel” where it it belongs IMHO?

Note 1 to @MT: Please do not quick drop RC into Stable this time.

Note 2 to @MT: Please respect dedicated forum users who work completely free of charge to discuss bugs and fixes to test Ros thus move rather than delete posts you feel are off topic, is a sensitive subject or questions you want to avoid in general.