Features/Evince Introspection Bindings: Difference between revisions

(8 intermediate revisions by the same user not shown)

Line 1:

[[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

[[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>). -->

Line 17:

Line 16:

* Targeted release: 0.96

* Last updated: 31 Jan 2012

* Percentage of completion: 90%

* Percentage of completion: 100%

== Initial information ==

Line 78:

Line 77:

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

Line 90:

Line 88:

== How To Test ==

~~== User Experience ==~~

Need be tested in a F17 based image

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

Evince 3.4

== ~~Contingency Plan~~ ==

== Release Notes ==

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

This change is a internal implementation issue. To the users should be almost equal than the previous version.

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

~~''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]]

@@ Line 1: / Line 1: @@
 <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
 [[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>). -->
@@ Line 17: / Line 16: @@
 * Targeted release: 0.96
 * Last updated: 31 Jan 2012
-* Percentage of completion: 90%
+* Percentage of completion: 100%
 == Initial information ==
@@ Line 78: / Line 77: @@
 == 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 ==
@@ Line 90: / Line 88: @@
 == How To Test ==
-== User Experience ==
+Need be tested in a F17 based image
-''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 ==
+Evince 3.4
-== Contingency Plan ==
+== Release Notes ==
-''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 ==
+This change is a internal implementation issue. To the users should be almost equal than the previous version.
-''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 ==
-''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]]