Features/Evince Introspection Bindings - Revision history

Godiard at 19:09, 5 November 2013

2013-11-05T19:09:03Z

← Older revision		Revision as of 15:09, 5 November 2013
Line 1:		Line 1:
	<noinclude>		<noinclude>
	[[Category:~~Feature Page Incomplete]]~~		[[Category:FeatureLanded\|Evince Introspection Bindings]]
	~~[[Category:Feature~~\|Evince Introspection Bindings]]
	<!-- You can add categories to tie features back to real deployments/schools requesting them, for example		<!-- 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>). -->		[[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>). -->

2012-01-31T17:44:57Z

Current status

2012-01-31T16:01:49Z

Dependencies

2012-01-31T16:01:28Z

User Experience

← Older revision		Revision as of 12:01, 31 January 2012
Line 90:		Line 90:

	Need be tested in a F17 based image		Need be tested in a F17 based image

	~~== 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 ==		== Dependencies ==

2012-01-31T16:00:55Z

Documentation

← Older revision		Revision as of 12:00, 31 January 2012
Line 96:		Line 96:
	== Dependencies ==		== Dependencies ==


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

	== Release Notes ==		== Release Notes ==

2012-01-31T16:00:38Z

Release Notes

← Older revision		Revision as of 12:00, 31 January 2012
Line 101:		Line 101:

	== 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~~.''
			This change is a internal implementation issue. To the users should be almost equal than the previous version.

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

2012-01-31T15:58:46Z

How To Test

← Older revision		Revision as of 11:58, 31 January 2012
Line 88:		Line 88:

	== How To Test ==		== How To Test ==

			Need be tested in a F17 based image

	== User Experience ==		== User Experience ==

2012-01-31T15:58:09Z

Contingency Plan

← Older revision		Revision as of 11:58, 31 January 2012
Line 94:		Line 94:
	== Dependencies ==		== Dependencies ==


	~~== 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 ==		== Documentation ==

2012-01-31T15:57:35Z

Benefit to Sugar

← Older revision		Revision as of 11:57, 31 January 2012
Line 78:		Line 78:

	== Benefit to Sugar ==		== 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~~.''		Have a working Read activity. Evince does not include the old bindings anymore.

	== Scope ==		== Scope ==

2012-01-31T15:56:33Z

Current status