Get support. Expand your Office skills. Was this information helpful? Yes No. Any other feedback? The more you tell us, the more we can help. How can we improve? Send No thanks. Thank you for your feedback! This is the extent of the commonality; 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.
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.
Depending on the scheme, significance may be assessed by lines of code changed, function points added or removed, potential impact on customers in terms of work required to adopt a newer version, risk of bugs or undeclared breaking changes, degree of changes in visual layout, quantity of new features, or almost anything the product developers or marketers deem to be significant, including marketing desire to stress the "relative goodness" of the new version.
Semantic versioning aka SemVer ,  currently the best known and most widely adopted version scheme in this category, uses a sequence of three digits Major. Patch , an optional pre-release tag and optional build meta tag. In this scheme, risk and functionality are the measures of significance. Breaking changes are indicated by increasing the major number high risk , new non-breaking features increment the minor number medium risk and all other non-breaking changes increment the patch number lowest risk.
The presence of a pre-release tag -alpha, -beta indicates substantial risk, as does a major number of zero 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.
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 Blender version 2. 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. It is a common practice in this scheme to lock-out new features and breaking changes during the release candidate phases and for some teams, even betas are lock-down to bug fixes only, in order to ensure convergence on the target release.
Again, in these examples, the definition of what constitutes a "major" as opposed to a "minor" change is entirely subjective and up to the author, as is what defines a "build", or how a "revision" differs from a "minor" change. Shared libraries in Solaris and Linux may use the current. A similar problem of relative change significance and versioning nomenclature exists in book publishing, where edition numbers or names can be chosen based on varying criteria.
Some projects use the major version number to indicate incompatible releases. Semantic versioning  is a formal convention for specifying compatibility using a three-part version number: major version; minor version; and patch.
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. Often programmers write new software to be backward compatible , i. 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.
Often packet headers and file format include a version number — sometimes the same as the version number of the software that wrote it; other times a "protocol version number" independent of the software version number. The code to handle old deprecated protocols and file formats is often seen as cruft.
Software in the experimental stage alpha or beta often use a zero in the first "major" position of the sequence to designate its status. However, this scheme is only useful for the early stages, not for upcoming releases with established software where the version number has already progressed past 0. Semver actually does not specify specific terms for development stages; the comparison is simply in lexicographical order.
There are two schools of thought regarding how numeric version numbers are incremented. Most free and open-source software packages, including MediaWiki , 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. The standard GNU version numbering scheme is major. In some cases, developers may decide to reset the major version number.
This is sometimes used to denote a new development phase being released. For example, Minecraft Alpha ran from version 1. Once the game was fully released, the major version number again reset to 1. When printed, the sequences may be separated with characters. 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 :.
There is sometimes a fourth, unpublished number which denotes the software build as used by Microsoft. Adobe Flash is a notable case where a four-part version number is indicated publicly, as in Some companies also include the build date. Version numbers may also include letters and other characters, such as Lotus Release 1a. Some projects use negative version numbers. One example is the SmartEiffel compiler which started from Many projects use a date-based versioning scheme called Calendar Versioning aka CalVer .
Ubuntu Linux is one example of a project using calendar versioning; Ubuntu This has the advantage of being easily relatable to development schedules and support timelines. Check availability. Cord cutters, this is for you. Shop Fios Plans Now. Score even more with our exclusive offers. No early termination fee. Skip the setup charge. Get a Stream TV on us.
Pair your plans. Get rewarded. Compare Fios to Optimum cable internet. More than 2. More than 25 x Upload speed. Why switch to Verizon Fios? Faster internet speeds How fast is Fios? Speed and reliability Get the fastest and most reliable internet available with Verizon. More reasons to switch to Fios. More ways to stay in control of your Fios account Apps for convenience, tools for support.
Verizon Fios customer support Existing Fios customers can access their account online to pay bills, go paperless or set up Auto Pay through their Verizon Fios Login. Check availability for your new address, then we can take it from there.
Have it all or a little less See the difference fiber optics makes with everything Verizon Fios has to offer: ultra-fast internet, brilliant HD TV and digital home phone service. This is not an official version history or changelog. For the official list, please visit the Minecraft website. For versions 1. For versions prior to Beta 1. Java Edition has been in constant development from May 10, What is now known as Pre-classic refers to the early unreleased versions of Minecraft during the week from May 10 to May 16, The next phase, what was later called Classic , lasted from May 17 to November 10, Indev , short for "in development", lasted from December 23, , to February 23, Infdev , short for "infinite development", lasted from February 27 to June 30, Alpha lasted from June 30 to December 3, , and Beta lasted from December 20, , all the way through to November 11, The full release stage of Minecraft: Java Edition 's development started on November 18, , and has continued until the present day.
At this point of development, the game was considered "complete", having both an " ending " and being ready for ratings and reviews. The game's price also increased from what it was in Beta , but users who previously bought the game were not charged extra.
The Beta development phase started on December 20, and ended on November 18, The main goals of this development stage were a larger focus on polishing gameplay, additional content, and stability.
The Alpha development phase started on June 29, , and ended on December 20, This version also limited the gamemode to Survival, but saw a re-release of multiplayer. At this time, Notch began developing the game full time, causing much more frequent updates. These were also the first versions which had to be purchased, though the price increased in later stages.
The Infdev development phase started on February 27, and ended on June 30,"Remember me" stores your User ID on this computer. You should not use this feature on public computers.