Features/Publish Sugar Version
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.
- Name: Gonzalo Odiard
- Email: <email@example.com>
- 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.
The change in Sugar is ready to land
The change in Browse already landed:
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).
No UI involved.
How To Test
Add a note to the developers about this variable.