Software version numbering system
Software version numbering system
- Subject: Software version numbering system
- From: Chad Armstrong <email@hidden>
- Date: Mon, 24 Nov 2003 13:30:18 -0600
I'm updating a Cocoa-based application, but I'm trying to determine how
to modify the numbering scheme. I looked around on the web and through
this list's archives, but didn't find anything that 100% answered my
queries, so hopefully someone has a more concrete solution. My
software has both a bug fix and a few smaller added features. If it
was just the bug patch, then I would probably bring the software up a
0.0.1 point (to follow after the Major.Minor.Patch numbering scheme).
This becomes a bit more confusing with the smaller feature additions.
They aren't leaps and bounds ahead type of features, but some smaller
areas to improve the program, and I'm trying to determine if this would
justify an entire 0.1.0 jump.
In comparison to other software, such as the Mac OS, it has been a
little odd in its upgrades. I felt that OS 9 should have been named OS
8.7 since I saw very little reason to upgrade (with the exception of
iTools). However, Mac OS 10.2 seemed to have many more additional
features from 10.1 than OS 8.6 to 9.0 ever had. Yet Jaguar was only a
0.1 upgrade, where it felt more like it should have been Mac OS 11.
This can bring up some confusion in how to number software versions.
Ultimately, I'm looking for some suggestions on whether my software
should be a 0.0.1 or 0.1.0 bump, or perhaps even something in the
middle like 0.0.5.
Chad Armstrong
email@hidden
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.