Difference between revisions of "Platform Team/Package Management System"
| Line 34: | Line 34: | ||
So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose. | So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose. | ||
| + | The corner stone of Sugar Services proposal is Saccharin service. This service provides installing/upgrading mechanism for all other services. The rest of services is just variety of sugar libraries/dbus-services. | ||
| + | === List of services === | ||
| + | * ''saccharin'', core service | ||
| + | * ''widgets'', UI layer which could assimilate various sugar releases changes e.g. let activity developers use new toolbars even in 0.82 environment and do not use many ''ifs'' in code | ||
| + | * ''bugsreport'' | ||
| + | * ''sugargames'' | ||
| + | * ... | ||
| − | + | === Versioning scheme === | |
| − | + | Each service has API changes based versioning scheme | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | <major-version>.<minor-version> | |
| − | + | * the major version starts from ''0''(premature state) and describes API backwards compatibility breakage | |
| − | + | * the minor version is for bugfixes and features that don't break backwards compatibility | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Benefit to Sugar == | == Benefit to Sugar == | ||
Revision as of 07:25, 14 December 2009
Summary
Increase level of compartmentalization in Sucrose.
Owner
This should link to your home wiki page so we know who you are
- Name: Your Name
Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved
- Email: <your email address so we can contact you, invite you to meetings, etc.>
Current status
- Targeted release: ASAP
- Last updated: Sun Jul 12 15:48:08 UTC 2009
- Percentage of completion: 0%
Detailed Description
This proposal assumes that the core of sugar development(in common sense) is variety of developers rather then developers who are taking part in sugar core(glucose) development. So, it's all about seeing from activity/3rd-party developers.
From such new core POV, sugar development process will look like:
- variety of sugar activities
- that use Sugar Services
So, developers use a set of services that have theirs own API changes based schedules. Existed glucose could be treated as a big service and splited to several components but thats not a task for this proposal. Instead, it's about proposing basic infrastructure of Sugar Services and several services that are not part of glucose.
The corner stone of Sugar Services proposal is Saccharin service. This service provides installing/upgrading mechanism for all other services. The rest of services is just variety of sugar libraries/dbus-services.
List of services
- saccharin, core service
- widgets, UI layer which could assimilate various sugar releases changes e.g. let activity developers use new toolbars even in 0.82 environment and do not use many ifs in code
- bugsreport
- sugargames
- ...
Versioning scheme
Each service has API changes based versioning scheme
<major-version>.<minor-version>
- the major version starts from 0(premature state) and describes API backwards compatibility breakage
- the minor version is for bugfixes and features that don't break backwards compatibility
Benefit to Sugar
Make sugar environment more straightforward by decoupling core from other stuff and using tough and well maintainable dbus API to let activities run on all (in ideal) deployed Sugar platforms.
Scope
Sugar core parts.
How To Test
Not yet implemented
User Experience
Not yet implemented
Dependencies
Not yet implemented
Contingency Plan
None necessary, revert to previous release behaviour.
Documentation
Release Notes
Not yet implemented