HomeSoftware Versioning
Software versioning is the process of assigning either unique version names or unique version numbers to unique states of computer software.
Within a given version number category (major, minor), version numbers are generally assigned in increasing order and correspond to new developments in the software.
• Date
• Year of release
• Alpha nuumeric codes etc.
Numeric Versiong is the most common software versioning scheme, different major releases of the software each receive a unique numerical identifier. This is typically expressed as three numbers, separated by periods, such as version 2.4.13. One very commonly followed structure for these numbers is:
major.minor[.build[.revision]]
or
major.minor[.maintenance[.build]]
The major number is increased when there are significant jumps in functionality, the minor number is incremented when only minor features or significant fixes have been added, and the revision number is incremented when minor bugs are fixed.
The Wine project used a date versioning scheme, which uses the year followed by the month followed by the day of the release; for example, "Wine 20040505".
Identifying software versions by year
for example windows 2003
Identifying versions by alphanumeric code
for example adobe photoshop CS2
Revision control (also known as version control (system) (VCS), source control or (source) code management (SCM)) is the management of multiple revisions of the same unit of information. It is most commonly used in software development to manage ongoing development of application source code. here we discuss about the fallowing version control systems.
• Concurrent Versions System (CVS)
• Subversion (SVN)
Within a given version number category (major, minor), version numbers are generally assigned in increasing order and correspond to new developments in the software.
Software versioning Schemes
• Numeric• Date
• Year of release
• Alpha nuumeric codes etc.
Numeric Versiong
Numeric Versiong is the most common software versioning scheme, different major releases of the software each receive a unique numerical identifier. This is typically expressed as three numbers, separated by periods, such as version 2.4.13. One very commonly followed structure for these numbers is:
major.minor[.build[.revision]]
or
major.minor[.maintenance[.build]]
The major number is increased when there are significant jumps in functionality, the minor number is incremented when only minor features or significant fixes have been added, and the revision number is incremented when minor bugs are fixed.
In most commercial softwares, the first released version of a software product has version 1.0. Numbers below 1 mean alpha or beta versions, i.e., versions for testing purposes or internal use, or versions that aren't stable enough for general or practical deployment.
Versioning by Date
The Wine project used a date versioning scheme, which uses the year followed by the month followed by the day of the release; for example, "Wine 20040505".
Versioning by Year of release
Identifying software versions by year
for example windows 2003
Using Alpha nuumeric codes for versioning
Identifying versions by alphanumeric code
for example adobe photoshop CS2
Revision control (also known as version control (system) (VCS), source control or (source) code management (SCM)) is the management of multiple revisions of the same unit of information. It is most commonly used in software development to manage ongoing development of application source code. here we discuss about the fallowing version control systems.
• Concurrent Versions System (CVS)
• Subversion (SVN)
We provide Software versioning for the educational purposes only. We do not responsiable for the correctness of its contents. the risk of using it lies entirelywith the user.
clinuxpro site Search