What is Software Release Life Cycle?
Pre-alpha version-
Pre-alpha is all the previous activities of testing software software. These programs include recorement analysis, software design, software development and unit testing.
These versions are not usually released.
Alpha
Alpha is the first step in Software Release Life Cycle where software testing is started. Alpha is the first letter of the ancient Greek alphabet, which is used to mean 1. In this step the developers have tested various types of software in the white box testing system, usually there is a separate testing team to perform this task.
Alpha versions are usually unstable. These software may crash or the data may be lost while using it. In spite of the exception, alpha versions are all open to use. Developers try to stabilize it at some time in the user's feedback, so that others can test it properly. Although alpha versions are not very common for everyone to use.
In the Android application version, 'a' means alpha version. Moreover, '0.1', '0.2' and alpha version. At the end of the post will be cleared with an example.
Beta
Beta is a step in software development that needs to be completed after Alpha. It is the second letter of the ancient Greek alphabet, which is used to refer to 2 numbers. This step is started after any software is completed. The main goal of Beta Testing is to make changes to the software through which users are benefited, sometimes with usability testing and included with beta testing. The method of converting betas versions to users is called beta release. And at the same time, software that is developing the first development is open to the general public outside specific organizations.
Beta versions are called users, beta testers. Generally they are the customers of the specific developer organization. Those who do this work voluntarily and free of charge. The full version of the software is almost free or at a lower cost.
At the end of the Android application, the beta version means 'b'. From 0.9 to 1.0, the bets are considered as beta releases.
Release Candidate
This will be released after the correction of the fatal bugs, which are meant to be the final version, which are meant to be released by release candidate (RC), all versions of the software. This time the product is intended to be more reliable. All the features of design, code and testing are almost done in this step. The next one or more beta cycles are to find bugs and work out solutions. Even though it is not used in Android, you know.
After that the final version of the application was released. If the final is '0.1, 0.2' then the front becomes '1.0'. After this 1.01, 1.13, 1.26, these types of versions are minor updates to the software. Moving from 1.x to 2.x means something major updated.
It happens a lot, major.minor
[.build [.revision]] = v2.3.11.238
Example:
Z Launcher - version 0.1 [Taran alpha]
PerAppFonts - version 0.3 Beta [Beta is written Beta, then there is nothing to see the version] Note Everything - version 4.2.8 [It
in the form of major.minor.build]
Advanced Task Killer Pro - version 1.9.7B92 [Some of the minor updates are still in beta version, b] Similarly a (alpha)
There is no need to know anything, whatever you ask is:
