Difference between revisions of "Features/Dotted Activity Versions"

From Sugar Labs
Jump to: navigation, search
Line 7: Line 7:
== Owner ==
== Owner ==
''This should link to your home wiki page so we know who you are''
* Name: [[Users:Erikos| Simon Schampijer]]
* Name: [[Erikos:AcountName| Simon Schampijer]]
''Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or technical issues need to be resolved''
* Email: simon AT sugarlabs DOT org
* Email: <your email address so we can contact you, invite you to meetings, etc.>
== Current status ==
== Current status ==

Revision as of 01:54, 9 February 2010


This Feature adds a minor part to the activity version. The idea is to reuse the existing activity_version field as the major part (integer). A new field will be introduced that will be the minor part (fraction) of the new floating point activity version.


  • Email: simon AT sugarlabs DOT org

Current status

  • Targeted release: 0.88
  • Last updated: Sun Dec 6 03:13:02 UTC 2009
  • Percentage of completion: 0%

Detailed Description

A new field is added to the activity.info file (activity_minor_version). Internally the activity version will become represented as a float, constructing the value of the minor and major part if the minor part is available. Otherwise the activity version is converted to a float.

Benefit to Sugar

Let activity developers release bugfix versions and do not mess them with already released new versions(e.g. bugfix for several-versions-ago release w/o breaking/confusing-users existed versioning scheme).


This feature enhance the versioning scheme of activities.

UI Design

The activity version is only visible in the activity list.

How To Test

- add the minor part to an activity.info file of an activity - you should be able to change the favorite status in the activities list of new and old style activities - you should be able to install activities (check newer and older versions of the same activity, too)

User Experience

If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.


Regular glucose dependencies.

Contingency Plan

None necessary, revert to previous release behaviour.


Release Notes

Comments and Discussion