Activity Team/Obsolete/Services Supervisor

< Activity Team‎ | Obsolete
Revision as of 01:33, 26 December 2009 by Alsroot (talk | contribs) (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> == …')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Summary

A privileged service which supervises activity run cycle, exposes startup progress, upgrades dependencies in background and provides triggers infrastructure.

Contacts

User:alsroot

Current status

How many branches are stable, note that some activities could be stuck to particular stable branch, so do not delete your stable branches if they still work in declared sugar environments. See Versioning guide.

Stable branch Sugar range Support status/Notes
0 0.82-1.00 is comming

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 Supervisor/Testing

Comments and Discussion

Sources

Link to source repository
Repositories on http://git.sugarlabs.org/ in service category are welcome.