Adobe Commerce simplifies upgrades

on

 

Adobe Commerce simplifies upgrades

It is important to keep your Adobe Commerce instance up-to-date in order to maintain a platform with the most recent features and that is reliable, secure, performant, as well as reliable. The Adobe Commerce product team is committed to ensuring that customers can make predictable, repeatable and hassle-free upgrades. We have made many changes to our release process over the last 18 months. These include a predictable release cycle and policy, beta and prerelease programs, and simplified release vehicles. The upgrade process has been simplified with the introduction quality patches, an upgrade compatibility tool and a new marketplace extension compliance strategy. As part of our continued efforts to simplify the upgrade process, we are excited to announce the new Upgrade best practices documentation, enhancements to the upgrade compatibility tool, and updated Marketplace compatibility policies.

Upgrading Best Practices

Adobe Commerce is well-known for its flexibility, customization and adaptability. The powerful extensibility features allow merchants to modify the UI, extend core services and integrate with other systems. It is crucial to do these customizations correctly in order to ensure that upgrades are efficient. That is why we are excited to announce our Upgrade best practices guide drawn from the vast knowledge and experience of our partners, merchants, and Adobe experts. This guide explains in detail:

  • The factors that affect the complexity of an upgrade
  • How to calculate the cost of an upgrade
  • Best practices in development and coding standards
  • Plan and execute an upgrade
  • Testing after a upgrade
Upgrade best practices

Enhancements to compatibility tools

The upgrade compatibility instrument is a command line interface (CLI), which analyzes customizations for a particular Adobe Commerce instance and flags any code that may need to be updated before an upgrade. The upgrade compatibility tool was initially designed to validate compatibility with PHP and the GraphQL api. This release expanded our coverage. The tool now supports:

  • Validate modifications to core filesAdobe strongly discourages customizing the core product code. We have added a checkpoint to enable customers and partners to quickly identify modifications to core code and to understand the consequences. This tool will allow you to identify potential issues early in development, prevent future upgrade problems and reduce TCO.
  • Export the report as a JSON file: The community provided feedback and this improvement was made. The tool now exports all issues to JSON files so that you can view, share and manage them without having to run it again.
  • Better handling VBE validationsVBEs (Vendor Bundled Extensions) are not part Adobe Commerce core code, but are supported and tested by Adobe. This update allows us to validate VBEs with the same method we use for core codes. This will make it easier for users to understand customizations and core codes/VBEs.
  • Provide error codesTo help you understand, identify, and resolve issues during an upgrade, we introduced error codes. Warning and error messages give a clear description of the problem and a suggested solution.
Sample upgrade compatibility report

Based on feedback from the community, we are expanding the functionality of the upgrade compatibility instrument. You can join our #upgrade-compatibility-tool slack channel to get support from the Adobe product team and the community, as well as to help guide the future direction of this tool.

Marketplace Compatibility Policy Extensions

Adobe is taking proactive steps to ensure that extensions on the market are compatible and of high quality. A new compatibility policy has been introduced that requires extensions vendors to confirm their compatibility within the first 90 days. Patch releases must be made within 30 days. Extensions not meeting these guidelines will be removed from the Marketplace after the deadline expires. The Commerce Marketplace Extension Quality Program also validates submissions for code quality, baseline functionality, and absence of malware. This policy gives merchants confidence in the extensions that they use to support their business needs.

Plan for future upgrades

With PHP 7.3 reaching end of support in December 2021, and Adobe Commerce 2.3 reaching end of support in April 2022, it is important that our customers update their environments to the latest version of Adobe Commerce. This will allow PCI compliance, as well as provide access to security updates, support, new functionality, and ongoing security updates. Marketplace extensions are an important part of upgrading and can cause major problems if they are not compatible with the target version. The new Marketplace compatibility policy will accelerate the availability of extensions for new versions of Adobe Commerce, making it easier for customers. The new Upgrade best practices guide and updates to the upgrade compatibility tool provide partners and customers with the assets they need to plan for and simplify their upgrade process.

We encourage you to upgrade if you're still using older versions of PHP or Adobe Commerce.

https://www.connectpos.com/the-hottest-new-feature-connectpos-facial-recognition/

https://www.connectpos.com/implement-omnichannel-magento-pos-system/

https://www.connectpos.com/how-to-make-a-successful-holiday-season-with-connectpos/

https://www.connectpos.com/hottest-features-in-quarter-4-of-2018/

https://www.connectpos.com/a-point-of-sale-that-can-boost-your-bottom-line/

https://www.connectpos.com/shipping-strategy/

Comments

Post a Comment