From Fedora Project Wiki
Line 119: Line 119:
== 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 "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  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 "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: Still in Mono 2.10 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Revision as of 13:23, 21 March 2014


Mono 3.2

Summary

Update the Mono stack in Fedora from 2.10 to 3.2

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

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)

Release Notes