Versioning policy

Akeneo connector for SFCC B2C's versioning policy is designed to provide our users with a clear understanding of how we manage and release software versions. Akeneo goal is to enhance the performance, security, and functionality of our connector. 

Our versioning policy explains the structure of version numbers, release schedules, and the significance of each release type, whether it's a major release with groundbreaking features or a minor release with bug fixes and enhancements. This policy aims to help you stay informed about the evolution of Adobe Commerce, ensuring you can plan for updates and optimizations that best suit your e-commerce needs.

Akeneo connector for SFCC B2C follows a standard convention for naming evolutions and bug fixes in its versioning policy. This convention ensures consistency and clarity in communicating the nature of each software update. Major releases, typically containing significant new features and enhancements, are denoted by a change in the first digit of the version number (e.g., from version 2.0 to 3.0). Minor releases, which primarily include bug fixes and smaller enhancements, are indicated by a change in the second digit (e.g., from version 2.0 to 2.1).

This naming convention helps users easily distinguish between major updates that may bring substantial changes and minor updates that focus on stability and refinement. It allows you to make informed decisions about when to upgrade your Adobe Commerce platform based on your specific needs and priorities.

For more information of the installation and upgrade process, please refer to setting up the connectors articles.

Release note

You can also follow the app store release notes for more details.