Elsupergomez (talk | contribs) |
Elsupergomez (talk | contribs) |
||
| Line 109: | Line 109: | ||
<!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | <!-- If this change proposal is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
User should note speedy improvemts running Mono applications. | |||
Some application grant futures for use most recent version of Mono. | |||
== Dependencies == | == Dependencies == | ||
Revision as of 13:19, 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:
Need update Mono spec
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
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
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- 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)