Difference between revisions of "Activity Team/Obsolete/Services Glucose"
(Created page with '<noinclude>{{TOCright}} Category:Activity Team <!-- You can add categories to tie service back to real deployments/schools requesting them, for example --> </noinclude> == …') |
(No difference)
|
Revision as of 03:10, 26 December 2009
Summary
Let activity and service developers rely on present of particular glucose release.
Contacts
Current status
| Stable branch | Sugar range | Support status/Notes |
|---|---|---|
| 0 | 0.82- 0.84 | |
| 0.1 | 0.86 - |
Detailed Description
Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.
Dependencies
What other services or 0install packages depend on this service? Are there changes outside the developers' control on which completion of this service depends? In other words, does your service depend on completion of another service owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Documentation
Is there upstream documentation on this service, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
How To Test
Activity Team/Obsolete/Services Glucose/Testing
Comments and Discussion
Sources
Link to source repository
Repositories on http://git.sugarlabs.org/ in service category are welcome.