English 中文(简体)
Starting from which integer is it better to switch to another product brand versioning scheme (year-based, codenames, ...)?
原标题:

Take a few examples:

  • DirectX 11
  • Silverlight 4
  • OpenGL 4
  • Firefox 3

I find that it is a little bit silly to have such high product version numbers: What it will mean when they ll reach version number 20? Products are just evolutions from one version to another, and the psychological impact is inversely proportional to the number magnitude (version 10.0 vs 11.0 compared to version 2.0 vs 3.0).

Common alternatives are:

  • switch to a year-based scheme (Visual Studio 6 => Studio 2005, 2008, 2010)
  • use abbreviation to reset the counter (Adobe CS 2,3,4..)
  • use codename (Windows XP, Windows Vista)
  • use hybrid codename/numbering puns (Windows Seven, MacOS X). Really clever.
  • use sub-release numbers (CATIA V5 R18, R19, ...). The best thing to do IMHO.
  • or even complete product re-branding.

So, starting from which number things are getting counter-productive: 3? 4? 6? 10?

Side question 1: what is the highest public version number you know of?

Side question 2: other interesting versioning alternatives to the one I suggested?

问题回答

As ever, the answer is 42.

EDIT: Oh, alright, I admit that sometimes the answer to questions on SO is Emacs .

One scheme is Ubuntu s: an autoincremented alliterative adjective and animal. For example, we re just getting off "Karmic Koala", and the next big thing will be (darn, can t remember, let s just go with "Leprous Lemur"), and then something like "Malevolent Macaque". Yes, it s easy to make fun of, and the earlier versions weren t alphabetical, but incrementing the letter is probably, for reasons you mentioned, better than incrementing a number. Of course, there s room for speculation for what comes after "Zymurgic Zebra", as there are no adjectives or animal names beginning with "[" or "{" (depending on whether you re looking at uppercase ASCII/Unicode characters or lowercase).

Edit: Also X may be a problem. Xanthippic Xerophyte?

I think it s really rather simple:

Option 1: you rename it every time
Reason 1: Marketing Department are weak and/or outsourced

Option 2: you increment the numeral
Reason 2: Marketing Department can, will, and has at least once already kicked Software Department s ass

Rebranding is a nightmare. Seriously, you guys.





相关问题
Version numbering basics? [closed]

Suppose I have a web application with some basic functions. I want to market it. So I would like to assign a version number - something like 0.0.1. What I want to know is are there any constraints ...

Versioning problem

people. I hope you can help me. In our development process we have a unix based file server with SFTP access (let’s call it A). This server store a large numer of xslt files we are working on. The ...

ECM - Document Control Management / Versioning and CMS

I anticipate this is going to be a very broad question however I shall endevour to be as concise as possible without divulging too much project critical information. For quite some time I have been ...

How do other development teams approach version numbers?

Our application is quite mature, and thus we are up to version 16. However, this can give the impression that the software is old and out of touch (how many commercial applications are there with a ...

SVN avoid storing passwords in plain text?

Under a bare bones setup for SVN on windows (without using VisualSVN), as per the instructions, the passwords are to be entered in the passwd file. Does SVN provide a way to encrypt or atleast mask ...

热门标签