What's your prefered method to name your software releases? Like Microsoft: alpha - beta - final - service pack... Like Google: gmail beta - beta - beta - beta - :) Like some softwares: 0.2 - 0.3 - 0.9999...
The first digit representing major milestones. The second digit represents incrementing the release (I generally release once a week so I increment the second digit). The third digit is used for patches, so if there is a bug in the code that is fixed outside of the normal release schedule I use the third digit.
The version identifier is usually a word, a number, or both. For example, version 1.0 is commonly used to denote the initial release of a program. There is no industry standard for how a version number should be formatted. For this reason, each computer company has their own unique methods of assigning version numbers.
In release management, there are three software release types: major, minor, and emergency. And each release type represents a different impact for your existing users.
The leftmost number (1) is called the major version. The middle number (2) is called the minor version. The rightmost number (3) is called the revision but it may also be referred to as a "point release" or "subminor version".
Microsoft uses version numbering as well as the alpha, beta, GA monikers.
I think version naming depends a lot on what you're trying to accomplish. If you're releasing something for consumption and aren't trying to collect data from a beta period, don't call it beta. If you're not trying to preview the technology, don't call it alpha.
I work mostly with web apps at present, and we just number our versions as incrementing integers by when we deploy (1, 2, 3, 4, 5, etc.). There's no reason to have to get into complicated naming logic if no one cares about the versions anyway.
We don't release alpha/beta software to our customers. Therefore we simply use:
(where x,y = 1,2,...)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With