3 ms·
Relatedly, the version number you peg on something is entirely a marketing decision, and not even that important of one these days. (Since I don't charge for u
by patio11 17y ago
Relatedly, the version number you peg on something is entirely a marketing decision, and not even that important of one these days. (Since I don't charge for upgrades, literally the only use I have for it is reproducing bugs. You won't find one written on my website anywhere.)
Back in the "all software users are software enthusiasts" days, all that stuff you learned about "point upgrades" and "beta releases" and whatnot actually made sense to people. Your mother does not care about the difference between a .1 and .01 point release, and never will. Make sure your website distributes the newest and best version, and make upgrading between not-the-newest-and-best-version and the-newest-and-best-version as automatic and painless as possible, to the limit of your business model's ability to do so.
Adjust as required if your product has to be compatible with other things. (Not ordinarily a worry of mine in B2C land.)
(I really envy you web-only guys some days. "The website has the latest version of the software on it" and "All users are using the latest version of the software" being axiomatic are so cool.)
- oliverkofoed 17y agoTheres a flipside to that envy though: The time needed to make sure the html+css+javascript renders the same on all the different browsers and their different versions. ... especially when they like to radically change everything all the time for no good reason. I'm looking at you IE. Why couldn't they just use mozilla or webkit, and concentrate on adding innovative features like chrome did.