[rubidium]

Basic idea: Spread out the release of feature functionality over many "patches" (i.e. M.m.patch) rather than releasing all of feature set all at once.

This is, to my experience, a pretty common way to do things. But it is a different mentality then "a feature set has to be entirely complete and have full functionality", which seemed to be the author's prior mentality.

[jameshart]

There's a lot of value in naming a practice, though, no matter how common it is. I like both the description of the approach, and the name, and if it helps people characterize the difference between flavors of semantic versioning philosophy then that is a good thing.

[amiraliakbari]

In case of mobile Apps, getting people to upgrade frequently is hard. I really like the approach softwares like GitHub for Windows have in checking for updates on every run and somehow forcing continuous upgrades, but it isn't suitable for non-technical audience. "The Big Reveal" seems more interesting to the App users who usually want visible improvements in exchange of their upgrade "effort", or they will become less intrigued to update to later releases.