< Changes
Elsupergomez (talk | contribs) No edit summary |
Elsupergomez (talk | contribs) (→Scope) |
||
Line 72: | Line 72: | ||
<!-- What work do the feature owners 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 feature owners 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?--> | ||
Update mono spec and build in koji until is ready. | |||
* Other developers: | * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- What work do other 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 other 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?--> | ||
* Release engineering: | * Release engineering: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuid required? If a rel-eng ticket exists, add a link here. --> | ||
* Policies and guidelines: | * Policies and guidelines: <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
Revision as of 13:26, 21 March 2014
Mono 3.2
Summary
Update the Mono stack in Fedora from 2.10 to 3.2
Owner
- Name: Claudio Rodrigo Pereyra Diaz
- Email: <elsupergomez@fedoraproject.org>
- Release notes owner:
Current status
- Targeted release: Fedora 21
- Last updated: (DATE)
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Support for Mono versions 3.0 and 2.10 is been discontinued. No further development of bug fixing is planned for those branches. Mono 3.2 is the active branch an have many improvements . See upstream notes http://www.mono-project.com/Release_Notes_Mono_3.2
Benefit to Fedora
Fedora aims to showcase the latest in free and open source software - we should have the most recent release of Mono 3.2
Scope
- Proposal owners:
Update mono spec and build in koji until is ready.
- Other developers:
- Release engineering:
- Policies and guidelines:
Upgrade/compatibility impact
Mono 3.2 includes most of the features of Mono 2.10. Most applications that use Mono should continue to function properly after update.
How To Test
Interested testers do not need special hardware. If you have a favorite Mono application, please test it with Mono 3.2 and verify that it still works as you expect.
User Experience
User should note speedy improvemts running Mono applications. Some application grant futures for use most recent version of Mono.
Dependencies
Has no dependencies found
Contingency Plan
- Contingency mechanism: Still in Mono 2.10
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product <-- Applicable for Changes that blocks specific product release/Fedora.next -->
Documentation
N/A (not a System Wide Change)