From Fedora Project Wiki
(start ipython feature)
 
(Add scope and some other minor edits.)
Line 31: Line 31:
== Scope ==
== 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?-->
<!-- 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?-->
The main changes takes place in the ipython package. Other packages depending on ipython will pull all ipython packages, when they require the "ipython" package, which might be unnecessary and waste disc space. This can be improved, when those package specificaly pull in those dependencies they need.
For a list of packages and description see Detailed Description above.


== How To Test ==
== How To Test ==
Line 52: Line 55:
== 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, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
<!-- 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, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
None.


== 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 you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- 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 you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
None necessary, revert to old version/package structure.


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*
* [http://ipython.org/ipython-doc/rel-0.13/whatsnew/version0.13.html Upstream Release Notes / Documentation]


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

Revision as of 12:49, 2 July 2012


Feature Name

Summary

Update ipython to version 0.13 with reorganizing the package structure to better fit the new upstream structure.

Owner

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-07-02
  • Percentage of completion: 00%


Detailed Description

Benefit to Fedora

Scope

The main changes takes place in the ipython package. Other packages depending on ipython will pull all ipython packages, when they require the "ipython" package, which might be unnecessary and waste disc space. This can be improved, when those package specificaly pull in those dependencies they need.

For a list of packages and description see Detailed Description above.

How To Test

User Experience

Dependencies

None.

Contingency Plan

None necessary, revert to old version/package structure.

Documentation

Release Notes

Comments and Discussion