If you’ve been updating your apps to new versions of Cesium each month, you’ve probably noticed an increase in the number of breaking changes to the Cesium API starting with b26 in March.
Our goal, of course, isn’t to make development hard. It is the opposite. As mentioned earlier, we are working towards stabilizing the API to make it more consistent, concise, and easier to use. To see what’s coming, track the issues with the breaking change label. I expect breaking changes to significantly slowdown by late summer, which will position us for a 1.0 some time later. In the meantime, upgrading to each new Cesium release will be the easiest way to keep up with the changes.