Features/Host Version: Difference between revisions

Line 17:

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.

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.

== Benefit to Sugar ==

Line 24:

Line 26:

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

TBD

== How To Test ==

''This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be.''

TBD

''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''

~~''A good "how to test" should answer these four questions:''~~

* ''What special hardware / data / etc. is needed (if any)?

* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?

* ''What specific actions do I perform to check that the feature is working like it's supposed to?

* ''What are the expected results of those actions?''

== User Experience ==

@@ Line 17: / Line 17: @@
 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.
+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.
 == Benefit to Sugar ==
@@ Line 24: / Line 26: @@
 == 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?''
+TBD
 == How To Test ==
-''This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.''
+TBD
-''Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.''
-''A good "how to test" should answer these four questions:''
-* ''What special hardware / data / etc. is needed (if any)?
-* ''How do I prepare my system to test this feature? What packages need to be installed, config files edited, etc.?
-* ''What specific actions do I perform to check that the feature is working like it's supposed to?
-* ''What are the expected results of those actions?''
 == User Experience ==