From Fedora Project Wiki
Line 64: Line 64:
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
Keep mono stack update with many new features and more compatible with .net plattaform.  
+
Keep mono stack update with many new features and more compatible with .net platform.
 
 
 
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
 
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?-->
  

Revision as of 18:57, 11 January 2016

Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.


Mono 4.2

Summary

Update the Mono stack in Fedora to 4.2 aca Cyle 6

Owner

Current status

  • Targeted release: Fedora 24
  • Last updated: 2016-01-11
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

Mono 4.2 is the last release of Cycle 6 from Xamarin. See more details at Mono 4.2.1

Benefit to Fedora

Keep mono stack update with many new features and more compatible with .net platform.

Scope

  • Proposal owners:

Mono 4.2 is in rawhide now. Most of the application must work fine with this update. See [1]

  • Other developers: N/A (not a System Wide Change)

Need check proper build on alternative platforms like ppc64 and s390

  • Release engineering: N/A (not a System Wide Change)
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Need check that all app depend on mono work fine.

N/A (not a System Wide Change)

How To Test

N/A (not a System Wide Change)

User Experience

N/A (not a System Wide Change)

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

Documentation

N/A (not a System Wide Change)

Release Notes