Difference between revisions of "Features/Dotted Activity Versions"
| Line 23: | Line 23: | ||
In case of backwards compatibility(how <0.88 and >=0.88 users will see new version), there could be several options: | In case of backwards compatibility(how <0.88 and >=0.88 users will see new version), there could be several options: | ||
| − | * use two separate ''activity.info'' fields for version, existed ''activity_version'' and new one with new full version.<br> | + | * use two separate ''activity.info'' fields for version, existed ''activity_version'' and new one with new full version.<br><0.88 user will see ''activity_version'', and >=0.88 version from new field |
| − | <0.88 user will see ''activity_version'', and >=0.88 version from new field | ||
| − | * reuse existed ''activity_version'' field as a major part of dotted version and new field for minor part<br> | + | * reuse existed ''activity_version'' field as a major part of dotted version and new field for minor part<br><0.88 user will see only ''activity_version'' and >=0.88 ''activity_version''.''new_field'' version |
| − | <0.88 user will see only ''activity_version'' and >=0.88 ''activity_version''.''new_field'' version | ||
| − | * reuse existed ''activity_version'' field as a minor part of dotted version and new field for major part<br> | + | * reuse existed ''activity_version'' field as a minor part of dotted version and new field for major part<br><0.88 user will see only ''activity_version'' and >=0.88 ''new_field''.''activity_version'' version |
| − | <0.88 user will see only ''activity_version'' and >=0.88 ''new_field''.''activity_version'' version | ||
== Benefit to Sugar == | == Benefit to Sugar == | ||
Revision as of 22:25, 5 December 2009
Summary
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).
Owner
This should link to your home wiki page so we know who you are
- Name: Your Name
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: <your email address so we can contact you, invite you to meetings, etc.>
Current status
- Targeted release: 0.88
- Last updated: Sun Dec 6 03:13:02 UTC 2009
- Percentage of completion: 0%
Detailed Description
In case of backwards compatibility(how <0.88 and >=0.88 users will see new version), there could be several options:
- use two separate activity.info fields for version, existed activity_version and new one with new full version.
<0.88 user will see activity_version, and >=0.88 version from new field
- reuse existed activity_version field as a major part of dotted version and new field for minor part
<0.88 user will see only activity_version and >=0.88 activity_version.new_field version
- reuse existed activity_version field as a minor part of dotted version and new field for major part
<0.88 user will see only activity_version and >=0.88 new_field.activity_version version
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
What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
UI Design
Nothing.
How To Test
Features/Dotted Activity Versions/Testing
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
Release Notes
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.