Changes

: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.

: Not sure what the original plans wrt the technical implemention of this feature were but I would assume the harder part of solving this problem is spreading the word among activity developers to update their .xo bundles accordingly.

:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task.  [[User:Sj|+sj]]  [[User Talk:Sj|<font color="#ff6996">+</font>]]

:: iirc, the original idea was roughly to have a monotonically increasing series of host #s which would define the point in the sugar devolution when the activity was finished and tested, with the idea that a later version of Sugar would be likely to run an older activity but not vice versa. If you are thinking in terms of 'on which of six platforms has this been tested' then this .info field may not be ideally suited to the task.  [[User:Sj|+sj]]  [[User Talk:Sj|<font color="#ff6996">+</font>]]

::: Mmm, that's a very good point. Do we want to distinguish just between progressing versions or also between different flavors of the same version?

::: Mmm, that's a very good point. Do we want to distinguish just between progressing versions or also between different flavors of the same version? [[User:ChristophD|ChristophD]]]

[[User:ChristophD|ChristophD]]]

Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.

Someone, preferably the activity authors themselves, would need to check activities against the various Sugar versions which are in use and document their findings. This however could also be a nice entry-level task for people who want to start contributing to Sugar.