Virto Commerce Release Strategy

Overview

Virto Commerce has always prided itself on the fast pace of innovation and rapid development of new functionality. We publish new releases for different modules with features, enhancements, and fixes daily.

There are three release channels: Stable, Edge and Preview.

Depending on your requirements and development cycle, you can choose Stable, Edge and Preview Release Strategy.

Stable Releases

Releases in the Stable channel have passed our full regressions, E2E and load testing and are recommended to all users, to avoid issues and maximize capabilities.

Every Quarter, we publish a new Stable Release in Stable Release Module Manifest on GitHub. You can use it with Virto Commerce CLI to apply updates.

If we fix a bug, we release a hotfix for the two latest stable releases.

We recommend using it for maintenance updates and new solution development.

Edge Releases

Edge channel provides the chance to be among the first to try the latest updates, performance improvements and new features, all with minimal risk.

We publish Edge releases for different modules every day. You can find information about releases on Virto Commerce GitHub and Module Manifest.

By default, Virto Commerce CLI works with Edge releases.

We recommend using it if you want to keep up to date and get access to some features faster.

Preview Release

Releases in the Preview channel show what we’re working on right now. There are still sometimes bugs present, as we want you, our community to share what’s new as soon as possible.

Usually, we create a Preview release for either PR or contribution, so we can verify implementation and align it in the early stage.

How to install the latest edge release

Virto Commerce CLI (vc-build) helps automate all installation and update processes.

Virto Commerce CLI should be installed.
Run this command to install Virto Commerce CLI.
dotnet tool install -g VirtoCommerce.GlobalTool

Create a clean folder for Virto Commerce for example C:\vc-platform-edge

In the command line go to the vc-platform folder

cd C:\vc-platform-edge

Install latest edge release for platform and modules from commerce bundle

vc-build install

How to update to latest edge release

In the command line go to the vc-platform folder

cd C:\vc-platform-edge

Install latest edge release for platform and modules from commerce bundle

vc-build update

How to install stable release

Create a clean folder for Virto Commerce for example C:\vc-platform-stable

Open vc-modules/bundles at master · VirtoCommerce/vc-modules (github.com) and select stable release folder.

Today, it is v3.

Download package.json file.

Rename vc-package.json file and copy to c:\vc-platform-stable folder.

vc-package.json - file is used to maintain the list of installed modules with their versions. This allows vc-build to easily restore the platform with the modules when on a different machine, such as a build server, without all those packages.

When you vc-build install, vc-build creates default vc-package.json in the folder automatically.

You can customize vc-package.json file with your set of modules either Virto Commerce or Custom modules.

In the command line go to the vc-platform folder

cd C:\vc-platform-stable

Install latest edge release for platform and modules from commerce bundle

vc-build install

How to update to latest stable release

Open vc-modules/bundles at master · VirtoCommerce/vc-modules (github.com) and select next stable release folder.

Download package.json file.

Open C:\vc-platform-stable\vc-package.json in any text editor and update Virto Commerce based on versions in package.json.

Save vc-package.json file.

In the command line go to the vc-platform folder

cd C:\vc-platform-stable

Install latest stable release for platform and modules from vc-package.json file.

vc-build install

How to install a specific version of platform or module

You can use Virto Commerce to install a specific version either platform or module.

vc-build install -platform -version <version>
vc-build install -module <module> -version <version>

Tips

  1. On a local machine, we recommend creating a new clean folder for every stable update. It helps to prevent unexpected behaviours in the cloud where CI creates a platform image from scratch.
  2. Keep vc-package.json under source control, ex: GitHub, Azure DevOps, etc. It helps you have a history of modifications.
  3. Creates vc-package.json boilerplate with the latest version number of the platform by running vc-build init
  4. You can customize the location of vc-package.json file by using command argument -PackageManifestPath ./somedir/somename.json. Ex: vc-build install -PackageManifestPath /path/package.json .
  5. Virto Commerce CLI prevents appsettings.json from modifications during the update.
  6. You can find the preview version of modules in Pull Requests and modules_v3.json at github
  7. Review all features of Virto Commerce CLI at github.

Summary

Virto Commerce provides three options: Stable, Edge and Preview, called channels, to manage how often Virto Commerce is updated with new features.

You can choose the best approach.

We expect that your Virto Commerce Solution is kept up to date and we can continuously deliver new features and innovation to you as easily as we did when you start development.