Release judgment mechanism・External releases are subject to release judgment

07/12/202020/10/2021Release Judgment

Release judgment criteria and methods change depending on the type of release

The first of the four mechanisms for determining software release is the type of release, but in the previous article, we introduced the types of external and internal releases. The reason why there are so many different types of releases is that the criteria and methods for determining whether or not a release can be made differ depending on the type of release .

Whether release judgment is required depends on the type of release

How does the type of release relate to the determination of a release ? The type of release does not affect the decision to release the software. It doesn’t affect the release decision, but the release type is used before that to decide if the task of release decision is necessary or not .　

There are two types of software releases, one for internal use and the other for external use . The word release is also used when software vendors provide software to customers, and when software is handed over from the development department to the test department at the software development site, the word release is often used.

And it is the release for the outside that requires the work of release judgment as a company . However, there are several types of external releases, including the official version, prototype version, and trial version. It depends on the company which type of release the release decision is made for.

The important thing is that the company has a clear idea of what type of release it will make a release decision on . If it is not clearly decided, it may happen that the software is in the hands of the customer without a release decision.

For the official version of the software, this always requires a release judgment. But what about the evaluation version, trial version, and trial version? There is also the idea that release judgment is necessary because it is software that is in the hands of end users, and it is also possible to think that release judgment is unnecessary because the software is provided on the premise that bugs are latent in the first place.

Release judgment criteria and methods change depending on the type of release

When making a release judgment for evaluation version, trial version, or trial version software, the method of judging whether or not to release and the criteria for judgment are different from the official version software. In the first place, it is assumed that the latent bugs have not been completely removed, but then what quality should be released, who decides whether to release it by what procedure, in- house different from the official version You will need to make various decisions.

What is the correct answer depends on the market in which the software is provided and the quality required of the software. And because it changes, if you do not clarify what kind of internal rules you have, there is a risk that mistakes will occur in unexpected places.

The official version for external use is absolutely necessary for release judgment

There are external releases in various situations, but of these, the release judgment work is absolutely necessary only for the official external release . So, first of all, it is necessary to clarify the release mechanism and judgment criteria for this official version of the software.

However, if there are software releases other than the official version as external releases, you will need the criteria and method of judging the release for each type of release, so be careful not to forget it. ..

Internal releases can be local rules within the department

There are various releases for internal use. Since the work of releasing is that the software is handed over to the test engineer etc. from the hands of the software engineer, it is necessary to make some judgment as to whether or not it is okay to release it for internal use. In that sense, judgment criteria and judgment mechanisms are necessary for internal releases as well.

However, since the release for internal use is only a part of the internal work of software development, the judgment criteria and mechanism can be considered as closed rules within the development organization if necessary, so Father Gutara is here. I didn’t pay much attention.

Release type and version number

By the way, in actual software development, it is often managed by assigning a finer release version number (major version, minor version, build number, etc.) in addition to these release types . At the software development site, depending on the development method, software may be released every day, so if you do not divide it by an ID number called a version number, it will be difficult to understand something. Therefore, it is common to use different version numbers and release types, such as releasing Ver.2.4.1.103 as the α version and releasing it to the end user as a function evaluation version of the XX function.

If you go too far in this area, you will get stuck in the software development site and you will not be able to get out of it, so I will stop here, but the version number attached to each software has such a background, degree Please remember.