System setup for standard products

The subsequent setup assumes that the distributor side includes a combined development/maintenance environment. This combined environment supports the maintenance of already released Feature Packs, development of a new Feature Pack, and the physical creation of solutions and Feature Packs.

Note: The examples use these conventions for VRC naming:

  • Version: B61<X>

    X = M aintenance, D evelopment

  • Release: a<Y>

    Y = Feature Pack number

  • Customer: <zzzz>

    zzzz = extension/localization code

This diagrams shows the results over time:

When the initial master product, B61_a, which is referred to as Feature Pack 0, is released, then the maintenance starts for B61_a in the maintenance VRC B61M_a. The development of the new Feature Pack is carried out in B61D_a1. All fixes in B61M_a are ported to B61D_a1. In the PMC registry of B61D_a1, these fixes are registered as obsolete solutions. After B61D_a1 is frozen, a final Feature Pack is created for the Feature Pack and installed in the same environment. Now you can perform maintenance on the Feature Pack.

Note: The SCM revision data is not available in the Feature Pack VRC B61_a1. The export or import software does not support the transfer of revisions. Because the original development VRC B61D_a1 is still present, you can still view revisions.

Currently, you can maintain B61M_a and B61M_a1, Feature Pack 0 and Feature Pack 1, in parallel. First, port bug fixes that are created for Feature Pack 0 between the freeze moment and the time of installation of Feature Pack 1. Feature Pack 2, B61D_a2, is currently in development.

You can repeat this cycle unlimited times for each new Feature Pack.