Features/Sugar 0.90 - Revision history

FGrose: remove outdated category

2014-08-16T21:44:16Z

remove outdated category

← Older revision		Revision as of 17:44, 16 August 2014
Line 54:		Line 54:

	== Comments and Discussion ==		== Comments and Discussion ==

	~~[[Category:FeatureAcceptedSoaS4]]~~

Pbrobinson: /* Comments and Discussion */

2010-06-21T20:19:57Z

Comments and Discussion

← Older revision		Revision as of 16:19, 21 June 2010
Line 54:		Line 54:

	== Comments and Discussion ==		== Comments and Discussion ==

			[[Category:FeatureAcceptedSoaS4]]

Pbrobinson at 19:19, 14 June 2010

2010-06-14T19:19:07Z

← Older revision		Revision as of 15:19, 14 June 2010
Line 36:		Line 36:
	== How To Test ==		== How To Test ==

	A ~~stna~~		A standard QA testing procedure is being defined.

	== User Experience ==		== 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~~.''
			The experience will be the new upstream Sugar Sucrose release.

	== Dependencies ==		== 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?''~~		Dependent on upstream release. Will update and include further details as they become avail.

	== Contingency Plan ==		== 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~~.''		If 0.90 doesn't come out in time ship either the current development release or roll back to the current stable release. Decision will be based on timelines and other delays.

	== Documentation ==		== 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.''

	The below links are not sorted, but are here for reference when this feature proposal is being written up in more detail. Not all of them may be useful, as a warning for the next person to tackle this page. [[User:Mchua\|Mchua]] 19:04, 11 June 2010 (EDT)

	* http://cgit.sugarlabs.org/soas/mainline/tree/make_fake_device.sh?h=blueberry#n44
	* http://lists.sugarlabs.org/archive/soas/2010-January/000715.html
	* http://lists.sugarlabs.org/archive/soas/2010-January/000654.html
	* http://cgit.sugarlabs.org/soas/mainline/tree/livecd-iso-to-bootable-tree.sh?h=blueberry
	* http://lists.sugarlabs.org/archive/soas/2010-January/000656.html
	* http://lists.sugarlabs.org/archive/soas/2010-January/000683.html

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

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

Pbrobinson: Created page with '== Summary == Update to the latest Sugar 0.90 stable release. == Owner == ''This should link to your home wiki page so we know who you are'' * Name: [[User:Pbrobinson| Peter R...'

2010-06-14T19:10:37Z

Created page with '== Summary == Update to the latest Sugar 0.90 stable release. == Owner == ''This should link to your home wiki page so we know who you are'' * Name: [[User:Pbrobinson| Peter R...'

New page

== Summary ==

Update to the latest Sugar 0.90 stable release.

== Owner ==

''This should link to your home wiki page so we know who you are''
* Name: [[User:Pbrobinson| Peter Robinson]]
* Email: pbrobinson at gmail dot com

== Current status ==
* Targeted release: SoaS v4
* Last updated: [[User:Pbrobinson| Peter Robinson]]
* Percentage of completion: 0%

== Detailed Description ==

We want to provide the latest version of the Sugar desktop environment as well as more activities to allow further building upon the collaborative environment.

Developers interested in working on the Sugar interface or writing activities can have a development platform without needing an XO laptop.

The includes all the core activities included in the Sucrose release.

== Benefit to SoaS ==

Latest upstream Sugar release

== Scope ==

Update packages to the latest release, add any new packages as necessary.

==UI Design==

Defined by upstream.

== How To Test ==

A stna

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

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

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

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

The below links are not sorted, but are here for reference when this feature proposal is being written up in more detail. Not all of them may be useful, as a warning for the next person to tackle this page. [[User:Mchua|Mchua]] 19:04, 11 June 2010 (EDT)

* http://cgit.sugarlabs.org/soas/mainline/tree/make_fake_device.sh?h=blueberry#n44
* http://lists.sugarlabs.org/archive/soas/2010-January/000715.html
* http://lists.sugarlabs.org/archive/soas/2010-January/000654.html
* http://cgit.sugarlabs.org/soas/mainline/tree/livecd-iso-to-bootable-tree.sh?h=blueberry
* http://lists.sugarlabs.org/archive/soas/2010-January/000656.html
* http://lists.sugarlabs.org/archive/soas/2010-January/000683.html

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

== Comments and Discussion ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]