Wednesday, June 22, 2011

Demajoring the Major Version Number

PCWorld recently ran an article stating that Firefox's new release cycle will fail. The rational stems from the idea that version numbers actually need to mean something. Unfortunately the business world strongly feels this is the case. Typically, IT organizations only allow minor updates to be pushed out to the users. With major version changes needing approval.

There is an upcoming shift in the way software is versioned. Chrome was one of the first major pieces of software to switch to the new model. With the shift to agile development, it was inevitable for software updates become more frequent.  Once updates become a norm instead of the exception does a major number version number still make sense?

Businesses will need to adapt to the changing world. Technology is always changing and for a magazine focusing on technology to make the suggestion that it shouldn't is a bit ridiculous. Someone needs to tell them not to be a Dodo Bird and to evolve.

1 comment:

  1. I've loved the way Chrome has updated since the beginning. If I did happen to find into a bug, it was usually fixed within a day or two in an update. I think it's a great practice for browsers but maybe not for some other programs. My best example in that regard would be Adobe who updates their Flash, Reader, etc. quite often and sometimes wants me close windows and then that's annoying (but they're probably patching up another security vulnerability haha).