fredriktjarnberg
May 3, 2011
  7216
(2 votes)

CMS 6 R1 and R2 public API diff.

We have gotten a request from Stefan Forsberg to publish a change log of API changes for CMS 6 R2. We are continuously running an internal tool to catch binary breaking changes before they are committed to our repository (as part of our gated check-in build). In order to commit the change the problem needs to be fixed (remove the breaking change) or acknowledged. This removes unintentional breaking changes completely and also reduces intentional breaking changes to a minimum. An acknowledged API diff (marked as “Ignored” in our log) will end up in the release notes document. Note that we are only tracking signature changes (whether a signature (type or member) has been added or removed between two releases). Also note that our tool will not trap the change that was discussed in Stefan’s post since it is not binary breaking change.

So here it is: CMS 6 R2 API changes (compared with CMS 6).

We will look into improving the reporting for upcoming releases maybe using the proposed tool http://inca-app.com/.

May 03, 2011

Comments

May 3, 2011 07:27 PM

THanks Fredrik, really appreciate the quick response and feedback!

Please login to comment.
Latest blogs
Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 1 of 2)

How Niteco's Upgrade Machine   uses orchestrated AI coding agents to deliver a buildable baseline and a running CMS, then hands over for...

Hung Le Hoang | May 11, 2026

Commerce 15 and CMS 13: Optimizely’s Next Step Toward AI-Powered, Graph-First Commerce

Optimizely is preparing to release Commerce 15 in mid-May 2026 , positioning this as a foundational shift—not just an upgrade. The direction is...

Augusto Davalos | May 7, 2026

The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026