Changes

Platform Team/Package Management System (view source)

Revision as of 02:12, 20 December 2009

391 bytes removed , 02:12, 20 December 2009

Line 57: Line 57:

Technically, service could be a part of glucose(or some of its releases) but from activity POV it doesn't make much sense, if activity requires some service, [[Activity_Team/Services/Saccharin|Saccharin]] will do nothing if requested service/version is a part of installed glucose or install proper service(via 0install). Various activities on the same system could use various versions of the same service, in that case [[Activity_Team/Services/Saccharin|Saccharin]](via 0install) will just provide proper version to particular activity.

−

~~=== Versioning scheme ===~~

−

~~Service are welcome to use API changes based versioning scheme(except obvious cases then service uses upstream versions):~~

−

~~<major-version>.<minor-version>~~

−

* the major version starts from ''0''(premature state) and exposes the fact of API backwards compatibility breakage

−

* the minor version is for bugfixes and features that don't break backwards compatibility

== Documentation ==

Alsroot

Bots, Bureaucrats, Check users, Administrators, Widget editors

5,705

edits