5,705
edits
Changes
Platform Team/Package Management System (view source)
Revision as of 10:05, 19 December 2009
, 10:05, 19 December 2009→Activity developers
=== Activity developers ===
=== Activity developers ===
Sugar Services makes sense only for activities that have non Sugar Platform dependencies and support more then one Sucrose release cycles.
Sugar Services makes sense only for activities that have non Sugar Platform dependencies or support more then one Sucrose release cycles.
For such activities development focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support several branches for the same service simultaneously.
For such activities development focus is shifting from Sucrose to API of services they are using. More over activity could be stuck to particular service API version(of course if service developers still support this branch) and Sugar Services will support several branches for the same service simultaneously.