After all it will still have all the features that you bought it for initially. If after a year you find yourself not needing any new features that are being added, you can stop there and just keep on using the version you have. So the idea here is that when you buy a license, you get the current release, a lifetime of maintenance (bugfix) updates and a year worth of new releases. It allows more people to actually notice, explore and make use of all the features that are being added. I like this model better, because a stream of smaller incremental changes is easier to follow and digest. Basically wrap every new feature into a release of its own and ship it out as soon as it's ready. If you look at the list of Bvckup 2 releases from the past several years, then under this model we would've been up to Bvckup 6 or 7 already.Īn alternative model is to make releases smaller, but ship them more frequently.
#Bvckup free upgrade#
Then entice existing users to upgrade and through this generate additional revenue to cover development costs. Product versioning option is something that I've been spending some time on recently and I am now leaning towards to keeping all further development under the Bvckup 2 name.Ĭonventional and widely-used model is to batch new features as they are developed and ship them out on annual basis as a new product "edition" (Something 2019).
0 kommentar(er)
