5,705
edits
Changes
Jump to navigation
Jump to search
Line 55:
Line 55: − − It is all about moving responsibility from developers [of particular tracked project] to Platform Team about how Sugar looks and behaves. Line 63:
Line 61: + +
User:Alsroot/Sugar Architecture (view source)
Revision as of 01:14, 2 November 2010
, 01:14, 2 November 2010→Implementation
Tracked projects are analogs of Sucrose components. The key difference is that Sucrose project itself is not a core project any more, it is an independent project (like other [[#Sugar_Universe|ones]]) and Platform Team is just tracking its life cycle to consider possibility of including its particular release to the [[#Sugar_distribution|distribution]]. It looks how GNU/Linux distributions package upstream projects.
Tracked projects are analogs of Sucrose components. The key difference is that Sucrose project itself is not a core project any more, it is an independent project (like other [[#Sugar_Universe|ones]]) and Platform Team is just tracking its life cycle to consider possibility of including its particular release to the [[#Sugar_distribution|distribution]]. It looks how GNU/Linux distributions package upstream projects.
Platform Team may consider possibility to support particular branches of tracked projects to fulfil deployments' needs.
Platform Team may consider possibility to support particular branches of tracked projects to fulfil deployments' needs.
The major purpose of Sugar distribution is providing a set of releases of tracked projects that are being well tested in particular environment (a set of versioned dependencies). That should help Sugar distributors to deploy Sugar. In ideal situation, they need test Sugar distribution only on their hardware.
The major purpose of Sugar distribution is providing a set of releases of tracked projects that are being well tested in particular environment (a set of versioned dependencies). That should help Sugar distributors to deploy Sugar. In ideal situation, they need test Sugar distribution only on their hardware.
It is all about moving responsibility from developers [of particular tracked project] to Platform Team about how Sugar ''product'' looks and behaves.
There are two types of Sugar distributions:
There are two types of Sugar distributions: