Software versioning - Wikipedia. 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 computer software. Modern computer software is often tracked using two different software versioning schemes—an internal version number that may be incremented many times in a single day, such as a revision control number, and a released version that typically changes far less often, such as semantic versioning. The ubiquity of computers has also led to these schemes being used in contexts outside computing. Sequence- based identifiers. 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. If changes are made between, say, 1. A typical product might use the numbers 0. Developers may choose to jump multiple minor versions at a time to indicate significant features have been added, but are not enough to warrant incrementing a major version number; for example Internet Explorer 5 from 5. Adobe Photoshop 5 to 5. This may be done to emphasize the value of the upgrade to the software user, or, as in Adobe's case, to represent a release halfway between major versions (although levels of sequence based versioning are not limited to a single digit, as in Drupal version 7. A different approach is to use the major and minor numbers, along with an alphanumeric string denoting the release type, e. A software release train using this approach might look like 0. If 1. 0rc. 1 turns out to have bugs which must be fixed, it turns into 1. The important characteristic of this approach is that the first version of a given level (beta, RC, production) must be identical to the last version of the release below it: you cannot make any changes at all from the last beta to the first RC, or from the last RC to production. If you do, you must roll out another release at that lower level. Two examples are Apache APR. The patch number is incremented for minor changes and bug fixes which do not change the software's application programming interface (API). The minor version is incremented for releases which add new, but backward- compatible, API features, and the major version is incremented for API changes which are not backward- compatible. For example, software which relies on version 2. API is compatible with version 2.
Often programmers write new software to be backward compatible, i. For example, IBM z/OS is designed to work properly with 3 consecutive major versions of the operating system running in the same sysplex. This enables people who run a high availability computer cluster to keep most of the computers up and running while one machine at a time is shut down, upgraded, and restored to service. The code to handle old deprecated protocols and file formats is often seen as cruft. Designating development stage. Most free and open- source software packages, including Media. Wiki, treat versions as a series of individual numbers, separated by periods, with a progression such as 1. On the other hand, some software packages identify releases by decimal numbers: 1. Decimal versions were common in the 1. Net. Ware, DOS, and Microsoft Windows, but even in the 2. Opera. The choice of characters and their usage varies by scheme. ![]() The following list shows hypothetical examples of separation schemes for the same release (the thirteenth third- level revision to the fourth second- level revision to the second first- level revision): A scheme may use the same character between all sequences: 2. A scheme choice of which sequences to separate may be inconsistent, separating some sequences but not others: 2. A scheme's choice of characters may be inconsistent within the same identifier: 2. Adobe Flash is a notable case where a four- part version number is indicated publicly, as in 1. ![]() Thinking in C++ Vol 1 & 2. Download (2,12 MB) These two powerfull volumes explain C++ from the beginning. They are interesting for beginners and also for experts. BITCOMET CHANGELOG v1.45 2017.1.17 GUI Improved: support login account using email GUI Improved: client IP address moved from status bar to context menu. Some companies also include the build date. Version numbers may also include letters and other characters, such as Lotus 1- 2- 3 Release 1a. Using negative numbers. One example is the Smart. Eiffel compiler which started from - 1. ![]() ![]() ![]() Ubuntu Linux uses a similar versioning scheme—Ubuntu 1. October 2. 01. 1. Some video games also use date as versioning, for example the arcade game. Street Fighter EX. At startup it displays the version number as a date plus a region code, for example 9. ASIA. When using dates in versioning, for instance, file names, it is common to use the ISO 8. ![]() ![]() ![]() The hyphens are sometimes omitted. Microsoft Office build numbers are an encoded date. So 3. 41. 9 is the 1. January of the year the project started. Other examples that identify versions by year include Adobe Illustrator 8. Word. Perfect Office 2. When a date is used to denote version, it is generally for marketing purposes, and an actual version number also exists. For example, Microsoft Windows 9. MS- DOS 7. 0. 0 and Windows 4. Microsoft Windows 2. Server is internally versioned as Windows NT 5. Article ID -- Article Title. FD38847 - Technical Note: Dynamic routing (BGP) over IPsec tunnel 13823 - Technical Note: Fortinet SFP, XFP, SFP+ and QSFP+ transceiver. Since version 3, updates have been indicated by adding an extra digit at the end, so that the version number asymptotically approaches . The current version is 3. This is a reflection of the fact that Te. X is now very stable, and only minor updates are anticipated. Te. X developer Donald Knuth has stated that the . In writing these version numbers as strings, the convention is to omit any parts after the minor version whose value are zero (with . For example, the Microsoft Windows operating system was first labelled with standard version numbers for Windows 1. Windows 3. 1. 1. After this Microsoft excluded the version number from the product name. For Windows 9. 5 (version 4. ![]() ![]() Windows 9. 8 (4. 1. Windows 2. 00. 0 (5. After Windows 2. 00. Microsoft created the Windows Server family which continued the year- based style with a difference: For minor releases, Microsoft suffixed . This style had remained consistent to this date. The client versions of Windows however did not adopt a consistent style. First, they received names with arbitrary alphanumeric suffixes as with Windows Me (4. Windows XP (5. 1) and Windows Vista (6. Then, once again Microsoft adopted incremental numbers in the title, but this time, they were not version numbers; the version numbers of Windows 7, Windows 8 and Windows 8. In Windows 1. 0, the version number leaped to 1. Alpha and beta releases are given decimal version numbers slightly less than the major release number, such as 1. Starting at 9. 00. Java SE 5. 0, for example, has the internal version number of 1. Windows from NT 4 on have continued the standard numerical versions internally: Windows 2. NT 5. 0, XP is Windows NT 5. Windows Server 2. Windows XP Professional x. Edition are NT 5. Windows Server 2. Vista are NT 6. 0, Windows Server 2. R2 and Windows 7 are NT 6. Windows Server 2. Windows 8 are NT 6. Windows Server 2. R2 and Windows 8. NT 6. 3. Note, however, that Windows NT is only on its fourth major revision, as its first release was numbered 3. Windows release number). Pre- release versions. After they mature but are not yet ready for release, they may be called . Generally alpha software is tested by developers only, while beta software is distributed for community testing. Some systems use numerical versions less than 1 (such as 0. This is a common convention in open source software. So the alpha version of the 2. An alternative is to refer to pre- release versions as . A set of releases or versions having the same major or minor version number may be collectively referred to as . Odd- numbered versions for development releases. For example, Linux 2. Linux kernel, and Linux 2. Linux 2. 3 matured into. After the minor version number in the Linux kernel is the release number, in ascending order; for example, Linux 2. Since the 2. 00. 4 release of the 2. Linux no longer uses this system, and has a much shorter release cycle. The same odd- even system is used by some other software with long release cycles, such as GNOME. Apple had their own twist on this habit during the era of the classic Mac OS: although there were minor releases, they rarely went beyond 1, and when they did, they twice jumped straight to 5, suggesting a change of magnitude intermediate between a major and minor release (thus, 8. The complete sequence of versions (neglecting revision releases) is 1. Mac OS X (since renamed mac. OS) departed from this trend, in large part because . As a result, all versions of OS X begin with the number 1. The first major release of OS X was given the version number 1. Instead, it was named version 1. In this system, the third number (instead of the second) denotes a minor release, and a fourth number (instead of the third) denotes bug- fix/revision releases. Because the first number is always 1. OS X is labeled . The developers of MAME do not intend to release a version 1. Version 0. 9. 9 was simply followed by version 0. In a similar fashion Xfire 1. After 8 years of development, e. Mule reached version 0. To describe program history. Due to lack of backward compatibility with plugins and other resources from the major version 2, a new version was issued that was compatible with both version 2 and 3. The new version was set to 5 (2+3), skipping version 4. A slightly different version can be seen in AOL's PC client software, which tends to have only major releases (5. Likewise, Microsoft Access jumped from version 2. Microsoft Word. Microsoft has also been the target of 'catch- up' versioning, with the Netscape browsers skipping version 5 to 6, in line with Microsoft's Internet Explorer, but also because the Mozilla application suite inherited version 5 in its user agent string during pre- 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |