This page defines the release process of the Traveler App and Driver App to the transport operator.
Traveler App release process #
The Traveler Application is deployed for each operator in the operator’s own store.
| Action | Owner | Details |
| 1. Deploy | ZF | ZF validation is complete and app is deployed in the operator’s store. Release notes and documentation are up to date. |
| 2. Submit for review | Operator | Shall be done as soon as possible, as review process from Apple and Android are long and may fail. |
| 3. Release | Operator | Operator acceptance test is successful. Android and iOS reviews are successful. Operator can complete the last step in the stores to have the app released to the public stores. |
NOTE: At some point, ZF may decide to do a “forced update” of an old application version to force travelers to move to the latest version. This shall happen for old versions that are used by only a small percentage of persons. The Operator will be notified before this happens.
Driver App release process #
The Driver Application is used by multiple operators and is hosted in ZF store.
| Action | Owner | Details |
| 1. Deploy | ZF | ZF validation is complete and app is Release notes and documentation are up to date. ZF validation is complete and app is deployed to the internal testing track. It will stay there for 7 days providing time for the operator to try it and train the drivers. |
| 2. Release | ZF | After 7 days it is promoted to the open testing track and force updated in the Driver’s devices, in case the latest app is not installed. |
