5,705
edits
Changes
Jump to navigation
Jump to search
Line 62:
Line 62: − * Regular per 6 month releases synced with regular releases of major GNU/Linux distributions+ − * Long Time Supporting (LTS) releases that coordinated with LTS releases of GNU/Linux distributions (if possible), that should simplify sugar supporting in the field − # new Platform Team release a sugar product, snapshot of (maybe not all) core(and not core) components+ − # modularizing sugar core+ − # sugar-toolkit as a stabilizing instrument within several (non-LTS) core releases+ − + − − − # original Platform Team purposes are natural for new Platform+Development team − # new Platform Team is more a ream of coordinators rather than core developers − # core components have its own [self]organized maintaining/developing teams − # ...
User:Alsroot/Sugar Architecture (view source)
Revision as of 18:56, 29 October 2010
, 18:56, 29 October 2010→Sugar distribution
==== Sugar distribution ====
==== Sugar distribution ====
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.
There are two types of Sugar distributions:
* Regular, per 6 months, releases that are synced with regular releases of major GNU/Linux distributions.
* Long Term Support (LTS) releases that are synced with LTS releases of major GNU/Linux distributions (if possible).
Having LTS releases should simplify sugar deployments since, in most cases, 6 months is too short major releases cycle.
==== Doer's environment ====
==== Doer's environment ====