Difference between revisions of "Activity Team/Obsolete/Services Env"
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | {{Obsolete | corresponding project was never created}} | ||
+ | |||
<noinclude>{{TOCright}} | <noinclude>{{TOCright}} | ||
[[Category:Activity Team]] | [[Category:Activity Team]] |
Latest revision as of 16:45, 25 November 2010
SummaryAccess to various sugar environment settings. This library is a part of Polyol group. ContactsCurrent statusFor regular services: How many branches are stable for what Sugar Platforms, 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.
For wrappers to native packages: This service is a wrapper for native package thus its versions are versions of accessible packages in current users' environment. Detailed DescriptionExpand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better. DependenciesWhat 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? DocumentationIs 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. If auto-documentation field is set in service.info file, API documentation will be generated on this page: How To TestActivity Team/Obsolete/Services Env/Testing Comments and DiscussionSources |