Notice to user

Release life cycle

As in most software lifecycles, there is a release lifecycle that refers to the different phases of the development process and maturity of the software versions. The phases of the release lifecycle of Net iD Portal that may or will be made available to customers are:

  • BETA
    The phase is known as beta-release and will only be available externally for temporary tests of new or customized features ordered by a customer.

  • RC (Release Candidate)
    The phase is known as release-candidate and refers to a version of Net iD Portal Front with potential to be a final release. A RC release may be made available for customers that needs to test new functionality of Net iD Portal Front before the FRC or GA releases. The RC release can be upgraded to the FRC and GA releases.

RC releases shall not be used in production and is not supported as a part of SecMaker support service.
  • FRC (Final Release Candidate)
    The phase FRC is used to test the new version at customers’ production sites to find possible “real life” issues that have not been found during the release testing at SecMaker. The release has gone through complete release testing at SecMaker and is considered as good as a GA release. The FRC is normally released four weeks before the GA release.

FRC releases may be used in production and is supported as a part of SecMaker support service. The FRC must however be updated to the GA release when available.
  • GA (General Availability)
    The phase is also known as the term “release to manufacturing” and is the public final release version.

Version identifiers

SecMaker product and product component names include version number using sequence-based software versioning.

A complete product version number has three components:

  • Major release identifier: X.y.z
    Used when making major changes such as incompatible API changes. It may include minor and update level changes.

  • Minor release identifier: x.Y.z
    Used when, for example, adding functionality in a backwards-compatible manner.

  • Update identifier: x.y.Z
    Used when making backwards-compatible bug fixes.