Sitecore har igennem en længere periode haft en anbefalet version som ikke nødvendigvis er den seneste. Hvad betyder dette?
Følgende er teksten fra websiden “Sitecore’s Recommended Version Policy“ på sdn.sitecore.net. Siden er beskyttet med password og derfor ikke tilgængelig for alle kunder. Men er gengives teksten:
As part of our commitment to continually improving our software and listening to our customer’s feedback, Sitecore regularly releases new versions of our CMS product. Each release undergoes careful quality assurance procedures to minimize the number of issues. Nonetheless, Sitecore only assigns the “Recommended Version” stamp to specific, carefully selected releases.
Some of our customers have found this confusing.
To understand our recommended version policy, it’s important to remember that people install Sitecore CMS for many different reasons. For example, a Sitecore CMS installation can be:
- A production installation that runs an important website for a customer.
- The development environment for an upcoming website. It may take several weeks or months before the website is deployed.
- A training website that helps developers learn about the product.
Our recommended version policy is aimed at production installations that run important websites for our customers.
Sitecore has a very agile approach to development. As a result, we release a steady stream of updates and feature releases for our product. This constant stream of improvements can place a burden on system administrators; who must decide whether or not to install the latest update.
Our recommended release policy helps administrators make these decisions, by reducing the risk for our customers and limiting the number of upgrades that we recommend.
When we release a new version of our CMS product, it does not immediately become the recommended version. This indicates that production installations that are working fine do not need to update to the new release.
Not every release is destined to become a recommended release. Sometimes we select a later version as the new recommended release. We work closely with the Sitecore development teams and with our partner/developer community when we decide which version should become a recommended release. Once again, our focus is on limiting the number of upgrades that our customers must perform.
However, it is important to remember that Sitecore fully supports every new release including those that aren’t recommended versions.
Before you decide which version of Sitecore you should use on a new production environment, you should investigate the later, non-recommended versions. If there is a later version that contains some new features that your website requires or resolves some known issues that might affect your website, it makes very good sense to install that version. If you subsequently decide to upgrade your website to a later release, you can investigate Sitecore’s Recommended Versions.
When in doubt, we recommend that you discuss this with your Sitecore partner before making a decision.
Sitecore’s Product Version Numbering
Every Sitecore product uses the following versioning system:
<Level 1>.<Level 2>.<Level 3> (rev. <Level 4>) — Sitecore.NET 6.2.0 (rev. 091012 Hotfix 330275-1)
For new releases, an increase in the version number at the various levels provides information about the release.
The following list describes what an increase in the version number at each level indicates:
- <Level 1> — indicates a major new version of the product. Developers, users, and partners should attend supplemental training to keep their certification status up-to-date. Internal sales training, documentation, and training materials will be updated. Major new versions require the greatest effort to upgrade. On average, upgrades for this level of release will take several weeks to implement.
- <Level 2> — indicates a release that introduces new features, these are typically UI changes and updates of, for example, XSLT files, ASPX files, or APIs. Documentation and training materials will be updated. Upgrades at this level require a moderate amount of effort to implement. On average, upgrades for this level of release will take 1-2 weeks to implement.
- <Level 3> — indicates a release that contains minor structural changes. Upgrades at this level require a minimal amount of effort. On average, upgrades for this level of release require less than a week to implement.
- (rev. <Level 4>) — indicates a release that contains bug fixes. Upgrades at this level require a minimal amount of effort. On average, upgrades for this level require a few hours to implement.
The fourth level numbering is a date — yymmdd-n — and n is used if more than one build is made on the same day.
Bemærk at Pentia generelt set – på nye løsninger og ved opgraderinger – anbefaler vores kunder at anvende den seneste version fra Sitecore. Det er vores oplevelse at en løbende opgradering til nyeste version af Sitecore giver en bedre værdi end “the big bang” når Sitecore opdaterer deres anbefalede version – hvilket ikke sker så ofte som vi gerne så hos Pentia.
Desuden er Sitecore – som det kan læses i ovenstående – committet til den samme support på den nyeste som på den anbefalede, og alt andet lige er der lavet flere rettelser, optimeringer og nyskabelser i den nyeste end i den anbefalede.
Kontakt os for mere information om hvordan vi kan opgradere din løsning.