When you run a software-as-a-service web app, one thing you don’t need to think too hard about is software version numbers. You can roll out new functionality and fixes as soon as they’re ready, and as customers don’t need to make a conscious decision about updating. They’re just always on the latest version.
With desktop apps or on-premise software like Perch the version numbers take on a bit of a dual purpose. Primarily they’re a technical signifier of the code version, but secondarily they perform a marketing function. In order to encourage users to update (and perhaps pay to update)...