ArcGIS Solutions releases follow a semantic versioning specification. This specification defines versions according to a major.minor scheme and sets expectations so you can mitigate risk, avoid business disruptions, and plan a smooth upgrade process when necessary.
When you sign in and deploy a major or minor version, a folder will be created in your organization under My Content. Any new or updated items will be placed in the folder. Existing items will not be updated or deleted.
The following table summarizes the main differences between each type of release, and more detail can be found in subsequent sections:
| Release | Example | New functionality | Deployment considerations |
|---|---|---|---|
Major | 2.0 | Yes | Significant changes to existing workflows or information products, and any changes to layers or data structures in the solution |
Minor | 2.2 | Yes | New information products, enhancements to existing information products, and bug fixes |
Major releases
Major releases introduce changes to workflows and related information products supported in ArcGIS Solutions, and they require the implementation of new workflows. They may also include changes to layers and data structures. Changes to layers and data structures require data to be loaded into new layers.
Major releases of ArcGIS Solutions are infrequent. Organizations need to develop a plan for major releases that ensures the smooth transition of workflows, information products, and source data.
Minor releases
Minor releases introduce changes that are compatible with existing layers in a solution. These changes include new information products, enhancements to existing information products, bug fixes, and support for new ArcGIS software versions (for example, ArcGIS Pro or ArcGIS Enterprise).
Minor releases may occur more frequently. Organizations can deploy minor releases alongside existing information products included in a solution and modernize workflows incrementally.