Attention! Knowledge of how to administer *nix systems is required for operations described in this section. Please, create a full Virtual appliance system backup before performing operations described below.
When developing your solutions based on theBitrixEnv/VMBitrix.CRM, tracking of both its file version updates and new features will be required. Such updates can be received by enabling repository of the BitrixEnv/VMBitrix.CRM beta version. Tracking can also be done by connecting repository for virtual appliance source data, which allows tracking all changes and modifications.
Attention! Packet source codes are available for BitrixEnv/VMBitrix.CRM, starting from version 7.3.0.
The beta version and its source codes are available for BitrixEnv/VMBitrix.CRM, starting from version 7.3.10.
Rollback to the stable release of installed BitrixEnv/VMBitrix.CRM beta version is not available. A new stable version release is required. For example, for beta version 7.3.10, an update to the new stable version 7.4 is required. Otherwise, a stable version of virtual appliance can be installed again from scratch.
Beta version numbering
To provide a "window" for numbering of stable versions, beta versions will have a higher number than the current stable version of BitrixEnv/VMBitrix.CRM. For example, current standard release – 7.3.2, beta version – 7.3.10. Prior to version 7.3.10, only stable versions can be released, but from version 7.3.10 and later – beta versions. For a new release, e. g. 7.4.xx, the sequence will be the same: prior 7.4.10 – stable versions, 7.4.10 and later – betas and etc.
Beta version features
All corrections, additional updates and new features, released in beta - will be included in the next stable version.
Beta version life cycle
Approximately 2-4 months, after that all updates will be included in the stable version release.
How to enable and disable BitrixEnv/VMBitrix.CRM beta version