Interesting idea. Will he able to maintain it, though, when he has versions 2, 3, 4, up to 15 from when he does add major new features, and finds that all those versions have bugfixes? i.e. When fixing a bug means having to fix, test and release it in 14 separate branches? The common model of having only one current version means effectively that there’s a rolling release, and you’re either on the latest release, or you should be updating to it, which keeps costs down for everyone.