Views: 1010 (Data available since 06.02.2017)

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.


Attention!
  • 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

  1. If you have a stable Virtual Appliance version, you need to update BitrixEnv/VMBitrix.CRM to the version 7.3.2 and later.

  2. Then there are 2 options available:
    • if the pool is not created:
      • enable: 2. Manage localhost > 7. Enable or disable beta version of bitrix-env > 1. Enable bitrix-env beta versions.
      • disable: 2. Manage localhost > 7. Enable or disable beta version of bitrix-env > 1. Disable bitrix-env beta versions.

    • if the pool is created:
      • enable: 1. Manage Hosts in the pool > 10. Enable or disable bitrix-env beta versions > 1. Enable bitrix-env beta versions.
      • disable: 1. Manage Hosts in the pool > 10. Enable or disable bitrix-env beta versions > 1. Disable bitrix-env beta versions.

      For VMBitrix.CRM (because the pool is created immediately after virtual appliance is installed):
      • enable: 2. Manage localhost > 7. Enable or disable beta version of bitrix-env > 1. Enable bitrix-env beta versions
      • disable: 2. Manage localhost > 7. Enable or disable beta version of bitrix-env > 1. Disable bitrix-env beta versions

  3. Then the packets must be updated via the Virtual Appliance menu or via command:

    yum clean all && yum update
    

How to determine, which repository is used: beta or stable?

Execute command:

yum clean all
The string with repo list will have bitrix-beta, for stable bitrix. For example:
Cleaning repos: base bitrix-beta bitrix-source epel ...

How to return the stable version

Beta version cannot be rolled back to the stable version. 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.

Beta version source data

Source codes can be downloaded the same way as stable version source codes.



Courses developed by «Bitrix», Inc.