Difference between revisions of "Features/Dotted Activity Versions"

From Sugar Labs
Jump to: navigation, search
Line 1: Line 1:
<noinclude>{{TOCright}}
+
<noinclude>{{Dated|See this [http://www.mail-archive.com/sugar-devel@lists.sugarlabs.org/msg16943.html discussion thread] for more up-to-date information}}
 
[[Category:Feature Accepted 0.88]]
 
[[Category:Feature Accepted 0.88]]
 
[[Category:Feature|Dotted Activity Versions]]
 
[[Category:Feature|Dotted Activity Versions]]

Revision as of 07:47, 7 October 2010

Warning.png
This page has been marked as important but in need of updating as of May 2016.
See all dated pages
There may be relevant discussion on the talk page.

See this discussion thread for more up-to-date information

Summary

This Feature adds a minor part to the activity version. It will 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.

Owner

  • Email: simon AT sugarlabs DOT org

Current status

  • Targeted release: 0.88
  • Last updated: Tue, 09. Feb 2010
  • Percentage of completion: 80%

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).

Scope

This feature enhance the versioning scheme of activities. An optional field is added to the activity config file activity.info.

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.

Dependencies

Regular glucose dependencies.

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

Documentation needs to be adjusted.

Release Notes

Comments and Discussion