779
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − <!-- 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:''' − − 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 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 --> Line 22:
Line 10: − + − + − + − ''Expand on the summary, if appropriate. A couple of sentences suffices to explain the goal, but the more details you can provide the better.''+ + − ''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.''+ − ''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?''+ + + + + + + + + − ''Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.''+ + − {{:{{PAGENAME}}/Testing}}+ + + − ''If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.''+ + − ''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?''+ + − ''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.''+ + − ''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.''+ + − + + − +
Updated Activities from the Mirabelle list (view source)
Revision as of 15:02, 2 August 2010
, 15:02, 2 August 2010no edit summary
[[Category:Feature|<Feature Name>]]
[[Category:Feature|<Feature Name>]]
== Summary ==
== Summary ==
== Current status ==
== Current status ==
* Targeted release: (SUGAR_VERSION)
* Targeted release: [[Mangolassi]]
* Last updated: (DATE)
* Last updated: [[User:Mchua|Mchua]] 16:02, 2 August 2010 (EDT)
* Percentage of completion: XX%
* Percentage of completion: 50%
== Detailed Description ==
== Detailed Description ==
I think [[#Summary]] pretty much covers it.
== Benefit to Sugar ==
== Benefit to Sugar ==
More recent version of Activities get deployed and used, and hopefully feedback on those more recent version will be received.
== Scope ==
== 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 Mangolassi version of SoaS) any significant feature improvements for that Activity that have occurred between its Mirabelle version and its Mangolassi version.
That's it; the updated packages will be automatically pulled into the Mangolassi image.
==UI Design==
==UI Design==
Not applicable.
== How To Test ==
== 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 ==
== 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 ==
== Dependencies ==
This feature depends on individual Activities, as it is a pull of their updated code.
== Contingency Plan ==
== Contingency Plan ==
None necessary, revert to previous release behaviour.
== Documentation ==
== Documentation ==
No documentation, though we can and probably should link to individual usage documentation for each of these Activities being shipped.
== Release Notes ==
== 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 ==
== 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]]