Changes

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 ==