Difference between revisions of "Updated Activities from the Mirabelle list"

Latest revision as of 14:49, 5 November 2013

Summary

All Activities shipped in the Mirabelle release will continue to be shipped in Mango Lassi if they pass a basic smoke test. These Activities will be updated so that Mango Lassi ships the latest stable version of their code, which may mean that some Activities that were in Mirabelle will have improvements or new features in their Mango Lassi version.

Owner

Name: Mel Chua (I would love to do this feature with someone else and mentor them through the feature process, so if you'd like to learn how this works with guidance, please contact me and I'll help you with it through the entire release cycle.)
Email: mel at sugarlabs dot org

Current status

Targeted release: Mango Lassi
Last updated: Mchua 16:02, 2 August 2010 (EDT)
Percentage of completion: 50%

Detailed Description

I think #Summary pretty much covers it.

Benefit to Sugar

More recent version of Activities get deployed and used, and hopefully feedback on those more recent version will be received.

Scope

For each Activity shipped in Mirabelle...

Get the latest stable version of the Activity from either ASLO or git
Smoke-test to see if that version of the Activity works. If yes, move on; if no, roll back a stable version until it does.
Update the Fedora package for that Activity to that version of its code.
Document (for Marketing, on a talking-points list when there is one for the Mango Lassi version of SoaS) any significant feature improvements for that Activity that have occurred between its Mirabelle version and its Mango Lassi version.

That's it; the updated packages will be automatically pulled into the Mango Lassi image.

UI Design

Not applicable.

How To Test

Using the image under test, run each Activity from Mirabelle through the standard SoaS Activity smoke-test (which needs to be written).

User Experience

Users who have experienced the prior Mirabelle release of SoaS will notice that their old familiar Activities are still there, but that some have new features.

Dependencies

This feature depends on individual Activities, as it is a pull of their updated code.

Contingency Plan

None necessary, revert to previous release behaviour.

Documentation

No documentation, though we can and probably should link to individual usage documentation for each of these Activities being shipped.

Release Notes

We can't write this section until we have release notes for each upstream (Activity) being updated.

Comments and Discussion

See discussion tab for this feature

@@ Line 1: / Line 1: @@
-[[Category:Feature|<Feature Name>]]
+[[Category:FeatureLanded|Updated Activities]]
-<!-- You can add categories to tie features back to real deployments/schools requesting them, for example
-[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). -->
-</noinclude>
-'''Comments and Explanations:'''
+== Summary ==
-There are comments (in italic) providing guidance to fill out each section, see also the [[Features/Policy|Feature Policy Page]] for a more detailed explanation of the new-feature process. '''Copy the source to a ''new page'' named Features/''Your Feature Name'' before making changes!  DO NOT EDIT THIS TEMPLATE.'''
+All Activities shipped in the [[Sugar on a Stick/Mirabelle|Mirabelle]] release will continue to be shipped in [[Sugar on a Stick/Mango Lassi|Mango Lassi]] if they pass a basic smoke test. These Activities will be updated so that Mango Lassi ships the latest stable version of their code, which may mean that some Activities that were in Mirabelle will have improvements or new features in their Mango Lassi version.
-<!-- All fields on this form are required to be accepted.
- We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
-<!-- The actual name of your feature page should look something like: Features/Your Feature Name.  This keeps all features in the same namespace -->
-== Summary ==
-''A sentence or two summarizing what this feature is and what it will do. This information is used for the overall feature summary page for each release.''
 == Owner ==
-''This should link to your home wiki page so we know who you are''
+* Name: [[User:Mchua|Mel Chua]] (I would ''love'' to do this feature with someone else and mentor them through the feature process, so if you'd like to learn how this works with guidance, please contact me and I'll help you with it through the entire release cycle.)
-* Name: [[User:AcountName| Your Name]]
+* Email: mel at sugarlabs dot org
-''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: (SUGAR_VERSION)
+* Targeted release: [[Sugar on a Stick/Mango Lassi|Mango Lassi]]
-* Last updated: (DATE)
+* Last updated: [[User:Mchua|Mchua]] 16:02, 2 August 2010 (EDT)
-* Percentage of completion: XX%
+* Percentage of completion: 50%
 == Detailed Description ==
-''Expand on the summary, if appropriate.  A couple of sentences suffices to explain the goal, but the more details you can provide the better.''
+I think [[#Summary]] pretty much covers it.
 == Benefit to Sugar ==
-''What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?''
-''Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.''
+More recent version of Activities get deployed and used, and hopefully feedback on those more recent version will be received.
 == 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?''
+For each Activity shipped in Mirabelle...
+# Get the latest stable version of the Activity from either ASLO or git
+# Smoke-test to see if that version of the Activity works. If yes, move on; if no, roll back a stable version until it does.
+# Update the Fedora package for that Activity to that version of its code.
+# Document (for Marketing, on a talking-points list when there is one for the Mango Lassi version of SoaS) any significant feature improvements for that Activity that have occurred between its Mirabelle version and its Mango Lassi version.
+That's it; the updated packages will be automatically pulled into the Mango Lassi image.
 ==UI Design==
-''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''
+Not applicable.
 == How To Test ==
-{{:{{PAGENAME}}/Testing}}
+Using the image under test, run each Activity from Mirabelle through the standard SoaS Activity smoke-test (which needs to be written).
 == 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.''
+Users who have experienced the prior Mirabelle release of SoaS will notice that their old familiar Activities are still there, but that some have new features.
 == Dependencies ==
-''What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time?  Other upstream projects like Python?''
+This feature depends on individual Activities, as it is a pull of their updated code.
 == Contingency Plan ==
-''If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.''
+None necessary, revert to previous release behaviour.
 == Documentation ==
-''Is there upstream documentation on this feature, or notes you have written yourself?  Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.''
+No documentation, though we can and probably should link to individual usage documentation for each of these Activities being shipped.
 == 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.''
+We can't write this section until we have release notes for each upstream (Activity) being updated.
 == Comments and Discussion ==
-* See [[{{TALKPAGENAME}}|discussion tab for this feature]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page. -->
+* See [[{{TALKPAGENAME}}|discussion tab for this feature]]