Know The Procedure Of Releasing Padvish New Versions

Introduction

The symbol of a good and dynamic product, especially in the field of technology and security is continuously improved and its new version and updated versions are released. Padvish products are also not excluded from this general rule, and to cover the needs of its new clients and adding new facilities, fixing shortcomings, and improving security, continuously new versions of Padvish are released.

But all these modifications, in any case, are a kind of change. Network managers know that in big networks, each type of change and upgrade needs a proper process to immigrate to the new version, so this upgrade is done with minimum worry and trouble.

This document describes the procedure for testing and publishing new versions of Padvish to help with a regular and continuous upgrade process

The pre-release procedure for Padvish’s new version

It is good to know that each Padvish version, generally, follows the below process to distribute and control the quality so can be publically released:

1. 1. Distributing process: designing, distributing, and initial tests are performed by Padvish distribution teams. This process includes continuous and periodic weekly processes based on Scrum methodology which is planned, implemented, and finally tested at regular and specific intervals, capabilities, and improvements. On average, several new versions of Padvish are produced and tested internally daily.
   2. Test while distribution: alongside with Padvish distribution team, there is another team that has the duty to test and control the quality of the final product.
      This team also, along with the development team, reviews, and tests the new capabilities and improvements every week.

In the end and when the new features are completed and ready for public release, the test will begin before release.

1. Capability test: in a period of a few days to one month, all new features added to the product (in contrast with the previous version) will be tested. During this period, each detected defect (from a typing error to the most important one) will be fixed daily and the operation of quality test and control will continue again.
2. Functional test: after the version reaches a relatively stable state without trouble, will enter the functional test phase. At this time all distribution activities on this version will be stopped and the function of this version on every operating system and different terms will be generally observed. With regards to high variety (more than twenty operation systems that are supported by Padvish) and the extent of tested features, a functionality test will normally take a month to accomplish.
3. Assign the release of the new version: after completing the above tests and testing the feature and their function, the technical committee reports the detected shortcomings that were tested and makes a decision about releasing a new version.

From now on the public release of Padvish’s new version begins.

Definition of terms and procedures of releasing Padvish

Each version of Padvish follows the below procedure – after following the internal test:

1. Beta version (trial): the version that has passed internal and in vitro tests and has no fundamentally known defect. This version is provided as a test for voluntary customers but is not ready to release yet.
2. Stable candidate version: after passing the Beta period, the version reached to stable candidate version. In this situation, the version used for Padvish’s new install or necessary and controlled upgrades, but still the public announcement of upgrading the new version does not send to previous Padvish customers.
3. Stable version: after passing the precautionary period and making sure of the proper function of the product, the version reaches its stable situation. At this time the public announcement of upgrading will be announced and the version will send to users by an automatic updating mechanism

Actually, each Padvish version follows each of the above stages once for home use and once for organizational use.

• Hot-fix version: despite the above procedure, the hot-fix version is a version that releases temporarily and for quick fixing of trouble. This version (to fasten up the release) passes the least necessary test and is just installed for a customer or system that encounters a problem and does not publically release.
• After a while, the hot-fix version will enter the beta release procedure and finally reach the stable version stage.

Public release procedure of Padvish’s new version

Despite passing tests in vitro situations, releasing a new version does not happen fast. Rather, a process is performed to fully ensure that there are no incompatibilities and problems in real environments and along with other software:

1. Home beta (trial) period: releasing a new version begins with a public announcement. In this stage, users who are interested to accompany us in the Padvish progress process have the opportunity to become familiar with its new features before other users. The trial period of the home beta version, in principle, is a month and client feedback and opinions will be collected and will be applied to Padvish, if necessary.
2. Releasing home stable candidate version: after passing the home beta period, Padvish’s new version will reach “stable candidate” and upload on the Padvish website for you to download.
3. Releasing Enterprise Beta version: contemporary to home stable candidate version, the Enterprise Beta period will begin. During this period some of the volunteer Enterprise customers, begin the upgrade process under control.
4. Releasing the home stable version: after a while of releasing the stable candidate version, this version reaches the stable version. At this time Padvish automatic update system will upgrade the client of the previous version to the new one.
5. Releasing Enterprise stable version: the last stage for a version is to reach the Enterprise stable status. In this stage and with regards to passing the long period of test in a real environment and making sure of the stability of the new version, a public announcement to upgrade will be announced to users.
6. Public release of the Enterprise stable version: the last stage of a version is reaching Enterprise stable status. In this stage and with regards to passing a long period of tests in a real situation and making sure of the stability of the new version, a public announcement will inform all users to upgrade.

Hot-fix releasing procedure

The above procedure, regularly, shows the releasing procedure of a new version of Padvish. In the situation that a defect must be overcome fast, it will be done by releasing a hot-fix version.

A Hot-fix version is a version that produced to fix a limited defect with minimum changes, and its installation must be limited to the system(s) that are encounter that specific defect. After passing time and doing sufficient tests, changes and improvements of this version will be released to public users in the regular releasing procedure.