Difference between revisions of "Deployment Platform/Software"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{Template:Harmonic Distribution Cycle Linkbar}} | {{Template:Harmonic Distribution Cycle Linkbar}} | ||
| − | == | + | == Software Map == |
| − | + | {| border="0" | |
| + | |- | ||
| + | |- valign="top" align="left" | ||
| + | | [[File:Harmonic Distribution Software.png]] | ||
| + | | The whole software within the Harmonic Distribution is structured as: | ||
| − | + | * '''Base software'''<br>Provided from Sweets Distribution in form of native packages. Base software is separated by targeted audience: | |
| − | + | :* '''Using oriented'''<br>For regular usage. This kind of software exists in two dimensions: | |
| − | + | :: By purpose: | |
| − | + | ::* '''Client side''' software to run on users' computers: | |
| + | ::** Stable Sucrose [[:Category:Platform Cycle|releases]]. | ||
| + | |||
| + | ::* '''Server side''' software to form school servers: | ||
| + | ::** [[#Server_Kit|Server Kit]] components. | ||
| + | |||
| + | :: By the supporting time: | ||
| + | |||
| + | ::* '''Short-term support''' (STS)<br>Targeting on individual usage and based on Sucrose 6 months release cycle. | ||
| + | ::* '''Long-term support''' (LTS)<br>Targeting on Sugar deployments, that can't switch between Sucrose releases every 6 months. | ||
| + | |||
| + | :* '''Development oriented'''<br>Targeting on developers who code within the Sugar Learning Platform. | ||
| + | :** [[#Glucose development|Development version of Glucose]]; | ||
| + | :** [[#Doers' Kit|Doers' Kit]]. | ||
| + | |||
| + | * '''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 [[#Distribution via Sugar Network|Sugar Network]]. | ||
| + | |- | ||
| + | |} | ||
| + | |||
| + | == Doers' Kit == | ||
Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar. | Sugar Doers Kit (SDK) is a set of tools and libraries to help people code in Sugar. | ||
| Line 20: | Line 43: | ||
* [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sugar via Sweets]], several Sucrose versions via Sweets. | * [[Platform_Team/Guide/Sweets_Usage#Sugar_via_Sweets|Sugar via Sweets]], several Sucrose versions via Sweets. | ||
| − | + | == Server Kit == | |
* [[Platform_Team/Server_Kit/sugar-server|sugar-server]] | * [[Platform_Team/Server_Kit/sugar-server|sugar-server]] | ||
| Line 31: | Line 54: | ||
For detailed information, see [[Platform_Team/Server_Kit|Server Kit]]'s home page. | For detailed information, see [[Platform_Team/Server_Kit|Server Kit]]'s home page. | ||
| − | == | + | == Distribution via Sugar Network == |
| − | |||
| − | |||
The high-level overview is looks like: | The high-level overview is looks like: | ||
| Line 43: | Line 64: | ||
** according to the local environment, it will download proper implementation; | ** 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. | ** if there is no proper binary implementation, it will download sources and will build them in local environment. | ||
| + | |||
| + | == Glucose development == | ||
Revision as of 07:45, 23 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.