Changes

* (http://wiki.sugarlabs.org/go/Development_Team/sugar-port will take care for the activities needs for a working activity on 0.82 for example)

* (http://wiki.sugarlabs.org/go/Development_Team/sugar-port will take care for the activities needs for a working activity on 0.82 for example)

<strong>Decoupling of Sucrose</strong>

<strong>Decoupling of Sucrose</strong> [[User:Alsroot|Alsroot]] 16:14, 21 May 2009 (UTC)

The major idea is to have tough core(with stable release cycle) + unlimited count of activities.<br>

The major idea is to have tough core(with stable release cycle) + unlimited count of activities.<br>

* core(glucose), six months(or so) release cycle, w/o any activities only API

* core(glucose), six months(or so) release cycle, w/o any activities only API

* bridge([[Development_Team/sugar-port|sugar-port]] for example) between all(in ideal) already deployed sugars and activities i.e. it provides backwards compatibility(so the same activity code will work on all sugars) and at the same time provides features from newest sugar(so the same activity code will use last sugar's features)

* bridge([[Development_Team/sugar-port|sugar-port]] for example) between all(in ideal) already deployed sugars and activities i.e. it provides backwards compatibility(so the same activity code will work on all sugars) and at the same time provides features from newest sugar(so the same activity code will use last sugar's features)

* the rest of sugar world i.e. fructose/honey (but now there is no differences between them)

* the rest of sugar world i.e. fructose/honey (but now there is no differences between them)<br>imho another point - activities have more shorter release cycle then core(glucose) has

And of course deployers can form any sets from these components

And of course deployers can form any sets from these components