Changes

Jump to: navigation, search

Features/Publish Sugar Version

1,515 bytes added, 10:11, 21 July 2015
Created page with "<noinclude> . </noinclude> == Summary == Some activities need know what Sugar version is running. The principal case is Browse that need report to ASLO w..."
<noinclude>
[[Category:Feature|.]]
</noinclude>
== Summary ==

Some activities need know what Sugar version is running. The principal case is Browse that need report to ASLO when check for available activities.
Sugar will publish a env variable SUGAR_VERSION that can be read by the activities.

== Owner ==
* Name: [[User:Godiard| Gonzalo Odiard]]

* Email: <godiard@gmail.com>

== Current status ==
* Targeted release: 0.108
* Last updated: July 21, 2015
* Percentage of completion: 100%

== Benefit to Sugar ==
Until now, we needed release a new version of Browse with every Sugar release, and with the version harcoded.
But that Browse activity can run in older Sugar versions, then you can have information mismatched.

== Scope ==
The change in Sugar is ready to land

https://github.com/godiard/sugar/commit/d5fd43b94681e93466a58c0bc81945b578bf33af

The change in Browse already landed:

https://github.com/sugarlabs/browse-activity/commit/a6fcd2c4f356b0b008ec41e14dfe0ecb431ccae8

Would be good add this information to Log activity too.
Developers should have in account check if the env variable exists or not, because activities can run in older Sugar releases, where this env variable is not available (check the Browse example).


==UI Design==

No UI involved.

== How To Test ==

== User Experience ==

No changes

== Dependencies ==

No dependencies

== Contingency Plan ==

== Documentation ==


== Release Notes ==

Add a note to the developers about this variable.

== Comments and Discussion ==
628
edits

Navigation menu