[PD] consolidate backward- and MaxMSP compatibility in Cyclone (was: Purpose of Cyclone)

[katja]

On Wed, Dec 23, 2015 at 4:44 AM, Dan Wilcox <danomatika at gmail.com> wrote:
> What about versioning? If people *have* to have older compatibility, then
> why can’t they just run an older version of cyclone? Newer development can
> take place on the current version and you can clearly note api
> changes/updates in a CHANGELOG. Say tag cyclone right now as version 1.0.0
> and all further development is version 2.0.*

Versioning is important but it can't solve all issues that arise when
diverging. While it is easy for a user to update to a specified
version of a library with deken, Pd patches already out there 'in the
wild' (to quote Jonathan) don't specify which version they need.

Katja