fredriktjarnberg
Optimizely
May 3, 2011
visibility 7512
star star star star star
(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!

error Please login to comment.
Latest blogs
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026