10,579
edits
Changes
Talk:Platform Team/Package Management System (view source)
Revision as of 09:07, 26 December 2009
, 09:07, 26 December 2009no edit summary
=== Sugar developers ===
=== Sugar developers ===
Services are intended to decentralize Sugar development process. For example, if you have some idea in mind, you can start pushing it through the Sucrose release queue to get it in the next (maybe not nearest) release. However, since the release process is binary—either your feature is included or not—Services offers more flexibility.
Services are intended to decentralize Sugar development process. If you have some idea in mind, you can start pushing it through the Sucrose release queue to get it in the next (maybe not nearest) release. However, since the release process is binary—either your feature is included or not—Services offers more flexibility. For example:
* some features are of arguable general benefit; Sugar Services would allow interested end users to efficiently test (and even deploy) such features;
* some feature are only stable in limited environments; Sugar Services would allow deployment in limited environmets without the risk of destabilizing the rest of Sugar.
A developer benefits from 0install [http://0install.net/goals.html features] by:
A developer benefits from 0install [http://0install.net/goals.html features] by: