Sitecore delivers Content Hub through an industry-standard SaaS (Software as a Service) model, which allows us to provide customers with a continuously improved product. This article describes our definitions in this area.
Sitecore constantly collects feedback from our customers through our User Research Program, which is a part of the Sitecore’s Collaborative program, in order for us to identify areas where the product can be improved.
Our teams prioritize the most impactful items based on how they affect satisfaction of our customers, customer’s business outcomes, and Content Hub’s strategic product roadmap.
Sitecore development team works on the items in the backlog using agile methodologies to meet the highest quality standards.
Sitecore engineers write automated tests to validate the functionality and quality of our code and conduct manual testing and user acceptance testing to maximize customer satisfaction.
Sitecore uses a deployment pipeline to automate the build, test, and deployment processes, which means that our customers get the latest updates and fixes without any manual intervention.
The changes are deployed to environments outside of office hours in your location, with no or minimal disruption to customer's experience.
Releases dates will progressively replace semantic versioning to identify different versions of Content Hub. Each version is associated with a specific release date. The release date allows customers to keep track of when new features and improvements have been introduced.
Customers can use this information to identify when specific functionality was added to the product using the release notes or other available documentation and determine if they need to update their processes or workflows to take advantage of these features.
- New updates and fixes are released to Content Hub frequently, with minimal user disruption or downtime.
- Releases include new functionality, general improvements, and bug fixes.
- Releases are designed to improve the performance, stability, and security of the product.
- Changes are deployed to the production environment with minimal disruption to users’ experience, and customers benefit from the latest updates and fixes without any additional cost or effort.
- To provide the best possible customer experience and minimize disruption, Sitecore will endeavor to avoid breaking changes as much as possible. Occasionally, to keep providing the service, Sitecore may have no alternative to address a necessary breaking change via a specialized breaking change release.
- A breaking change release may include the removal of the existing functionality or changing the way it integrates with other systems and may require updates to integrations, workflows, or configurations.
- Breaking change releases will be announced at least 30 days in advance, and documentation will be provided.
- The changes to non-production environments will be deployed two weeks before the production release, to test and update any configuration before they go live.
- Sitecore teams monitor the release for any issues or feedback to ensure that everything is working as intended and meets expectations.
- Sitecore analyzes the data and customers' feedback to evaluate the impact of the new functionality and make any necessary adjustments.
- New feedback or bug reports are incorporated into the Sitecore backlog for future releases.
- Sitecore continuously improves and enhances Content Hub to meet customers' needs and deliver more value.
Notes:
- Content Hub customers don't need to install, maintain, or upgrade any software.
- Content Hub can be accessed online anytime.
- The latest updates and fixes are provided without any additional cost or effort.
- The SaaS delivery model allows Sitecore to provide you with a more reliable, scalable, and secure product that meets your business needs.
If you have any questions or feedback, reach out to Sitecore Support.
Check out the Legal Hub for our legal terms, including our latest SaaS Service Level Agreement (SLA).