• It's hard to communicate to your users that you have made some definitive, significant change,
• It's hard to know what to support for how long, you obviously can't support every release indefinitely.

I think there is growing insight into this, on both sides of the original "cadence" debate. A tale of two philosophies, perhaps with a unifying theory A few years back, at AKademy in Glasgow, I was in the middle of a great discussion about six month cycles. I was a passionate advocate of the six month cycle, and interested in the arguments against it. The strongest one was the challenge of making "big bold moves". "You just can't do some things in six months" was the common refrain. "You need to be able to take a longer view, and you need a plan for the big change." There was a lot of criticism of GNOME for having "stagnated" due to the inability to make tough choices inside a six month cycle (and with perpetual backward compatibility guarantees). Such discussions often become ideological, with folks on one side saying "you can evolve anything incrementally" and others saying "you need to make a clean break". At the time of course, KDE was gearing up for KDE 4.0, a significant and bold move indeed. And GNOME was quite happily making its regular releases. When the KDE release arrived, it was beautiful, but it had real issues. Somewhat predictably, the regular-release crowd said "see, we told you, BIG releases don't work". But since then KDE has knuckled down with regular, well managed, incremental improvements, and KDE is looking fantastic. Suddenly, the big bold move comes into focus, and the benefits become clear. Well done KDE On the other side of the fence, GNOME is now more aware of the limitations of indefinite regular releases. I'm very excited by the zest and spirit with which the "user experience MATTERS" campaign is being taken up in Gnome, there's a real desire to deliver breakthrough changes. This kicked off at the excellent Gnome usability summit last year, which I enjoyed and which quite a few of the Canonical usability and design folks participated in, and the fruits of that are shaping up in things like the new Activities shell. But it's become clear that a change like this represents a definitive break with the past, and might take more than a single six month release to achieve. And most important of all, that this is an opportunity to make other, significant, distinctive changes. A break with the past. A big bold move. And so there's been a series of conversations about how to "do a 3.0, in effect, how to break with the tradition of incremental change, in order to make this vision possible. It strikes me that both projects are converging on a common set of ideas:

• Rapid, predictable releases are super for keeping energy high and code evolving cleanly and efficiently, they keep people out of a deathmarch scenario, they tighten things up and they allow for a shakeout of