Difference between revisions of "Deployment Platform/Software"
Jump to navigation
Jump to search
| Line 15: | Line 15: | ||
:: By purpose: | :: By purpose: | ||
| − | ::* '''Client side''' | + | ::* '''Client side'''<br>Stable Sucrose [[:Category:Platform Cycle|releases]] - software to run on users' computers; |
| − | + | ::* '''Server side'''<br>[[#Server_Kit|Server Kit]] - to form school servers. | |
| − | |||
| − | ::* '''Server side''' | ||
| − | |||
:: By the supporting time: | :: By the supporting time: | ||
| − | ::* '''Short-term support''' (STS)<br>Targeting | + | ::* '''Short-term support''' (STS)<br>Targeting to individual usage and based on Sucrose six months release cycle. |
| − | ::* '''Long-term support''' (LTS)<br>Targeting | + | ::* '''Long-term support''' (LTS)<br>Targeting to Sugar deployments that can't switch between Sucrose releases every six months. |
| − | :* '''Development oriented'''<br> | + | :* '''Development oriented'''<br>[[#Doers' Kit|Doers' Kit]] - targeting to developers who code within the Sugar Learning Platform. |
| − | |||
| − | |||
| − | * '''Community software'''<br>The rest of software created on top of the Base one. In contrast to Base, this kind of software is being provided via [[# | + | * '''Community software'''<br>The rest of software created on top of the Base one. In contrast to Base, this kind of software is being provided via [[#Sugar Network|Sugar Network]]. |
|- | |- | ||
|} | |} | ||
Revision as of 01:44, 25 March 2012
Harmonic Distribution version cycle: | 1.0 | Factory |
Software Map
|
The whole software within the Harmonic Distribution is structured as:
|
Doers' Kit
Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar.
- Sweets, Zero Install based Package Management System for Sugar.
- sugar-lint, utility to lint various source files.
- gatch, support long or ever standing, all time being on top, downstream patchset for the base branch in a Git repository.
- Sugar via Sweets, several Sucrose versions via Sweets.
Server Kit
For detailed information, see Server Kit's home page.
Distribution via Sugar Network
The high-level overview is looks like:
- software creators
upload source bundles to the Sugar Network; only sources, even if it is binary based activities; - Sugar Network
if uploaded software needs building, it will send it to OBS; - on users side
Sweets library will:- read Sugar Network to find out information about implementations of software that user requested to launch;
- according to the local environment, it will download proper implementation;
- if there is no proper binary implementation, it will download sources and will build them in local environment.