So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to regular service(s) with proper [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|versioning scheme]] as well e.g. if glucose's activity API wasn't backwards compatibility broken since 0.82(glucose-0.x service) all activities that requires ''glucose 0'' will be launched but instead of launching activities with requirements ''glucose 1'', user will be warned about outdated sugar environment. | So, developers use a set of services that have their own [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|API changes based]] schedules. Glucose [[Activity Team/Services/Glucose|could be]] [[Documentation Team/Services/Native packages usage|wrapped]] to regular service(s) with proper [[Documentation_Team/Services/Service_Developers_Guide#Versioning_scheme|versioning scheme]] as well e.g. if glucose's activity API wasn't backwards compatibility broken since 0.82(glucose-0.x service) all activities that requires ''glucose 0'' will be launched but instead of launching activities with requirements ''glucose 1'', user will be warned about outdated sugar environment. |