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), these numbers are generally assigned in increasing order and correspond to new developments in the software. At a fine-grained level, revision control is often used for keeping track of incrementally different versions of electronic information, whether or not this information is actually computer software.
Welcome to CWAnswers
CWAnswers is your guide to the sprawling world wide web. The directory aims to provide a useful guide made by users. You can share your knowledge as well - simply sign up and edit your first entry. For questions just contact the team at support - at - cwanswers.com.
Weblinks for Versioning
Top 10 for Versioning
Things about Versioning you find nowhere else.
Select content modules
Easy Blog Post Versioning with Dropbox
For me, the biggest part of writing is rewriting. ... WordPress does have a versioning feature for posts, but most other blog software does not. ...www.bloggingtips.com/2009/04/10/easy-blog-post-versioning-wi...Windows PowerShell Blog : CTP: Versioning
The purpose of this email is to set your expectations about the CTP. Versioning The ... 09, 2007 6:45 PM by Joel Stidley's Exchange and PowerShell Blog ...blogs.msdn.com/powershell/archive/2007/11/02/ctp-versioning....Creative Versioning — Blogs, Pictures, and more on WordPress
LiveTechnology Blog. Small Medium Enterprises ... Creative Versioning LinkedIn Group Formed ... Creative Versioning: Targeting Your Local Market ...en.wordpress.com/tag/creative-versioning/Random Musings of Jeremy Jameson : Versioning Blog Posts in WSS v3 and ...
Complementing the Work Items list that I described in a previous post , we use a blog site (creatively called the "DevBlog") in Microsoft Office SharePoint Server ...blogs.msdn.com/jjameson/archive/2008/04/23/versioning-blogs-...Todd Biske: Outside the Box " Blog Archive " Revisiting Service Versioning
... posted her perspective on service versioning on the SOA Consortium's blog. ... If this is the case, versioning effectively goes away, the explicit ...www.biske.com/blog/?p=242Software 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), these numbers are generally assigned in increasing order and correspond to new developments in the software. At a fine-grained level, revision control is often used for keeping track of incrementally different versions of electronic information, whether or not this information is actually computer software.
Software Versioning schemes
A variety of version numbering schemes have been created to keep track of different versions of a piece of software. The ubiquity of computers has also led to these schemes being used in contexts outside computing.
Sequence-based identifiers
In sequence-based software versioning schemes, each software release is assigned a unique identifier that consists of one or more sequences of numbers or letters. This is the extent of the commonality, however: schemes vary widely in areas such as the quantity of sequences, the attribution of meaning to individual sequences, and the means of incrementing the sequences.
Change significance
In some schemes, sequence-based identifiers are used to convey the significance of changes between releases: changes are classified by significance level, and the decision of which sequence to change between releases is based on the significance of the changes from the previous release, whereby the first sequence is changed for the most significant changes, and changes to sequences after the first represent changes of decreasing significance.
For instance, in a scheme that uses a four-sequence identifier, the first sequence may be incremented only when the code is completely rewritten, while a change to the user interface or the documentation may only warrant a change to the fourth sequence.
This practice permits users (or potential adopters) to evaluate how much real-world testing a given software release has undergone. If changes are made between, say, 1.3rc4 and the production release of 1.3, then that release, which asserts that it has had a production-grade level of testing in the real world, in fact contains changes which have not necessarily been tested in the real world at all. This approach commonly permits the third level of numbering ("change"), but does not apply this level of rigor to changes in that number: 1.3.1, 1.3.2, 1.3.3, 1.3.4... 1.4b1, etc.
In principle, in subsequent releases, 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. A typical product might use the numbers 0.9 (for beta software), 0.9.1, 0.9.2, 0.9.3, 1.0, 1.0.1, 1.0.2, 1.1, 1.1.1, 2.0, 2.0.1, 2.0.2, 2.1, 2.1.1, 2.1.2, 2.2, etc. Developers have at times jumped (for example) from version 5.0 to 5.5 to indicate that significant features have been added, but not enough to warrant incrementing the major version number, though this is improper.
