Latest revision as of 13:54, 15 February 2016

Mono 4.2

Summary

Update the Mono stack in Fedora to 4.2 aca Cyle 6

Owner

Name: Claudio Rodrigo Pereyra Diaz
Email: <elsupergomez@fedoraproject.org>
Release notes owner:

Current status

Targeted release: Fedora 24
Last updated: 2016-02-15
Tracker bug: #1308558

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:

Need check proper build on alternative platforms like ppc64 and s390

Release engineering: N/A
- List of deliverables: N/A

Policies and guidelines: N/A

Trademark approval: N/A

Upgrade/compatibility impact

Need check that all app depend on mono work fine.

How To Test

Interested testers do not need special hardware. Take a given Mono application and test it against the Mono from rawhide or at this copr repo and verify it works:

* http://copr.fedoraproject.org/coprs/tpokorra/mono/

Any issue will be reported in github https://github.com/elsupergomez/lbs-mono-fedora or https://github.com/tpokorra/lbs-mono-fedora

User Experience

User should note speedy improvement running Mono applications.

Dependencies

N/A (not a System Wide Change)

Contingency Plan

Contingency mechanism: Keep with Mono 4.0 from F23
Contingency deadline: Alpha Freeze
Blocks release? No
Blocks product? None

Documentation

https://fedoraproject.org/wiki/Packaging:Mono

https://github.com/mono/mono

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | 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.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
 <!-- Self Contained or System Wide Change Proposal?
 Use this guide to determine to which category your proposed change belongs to.
@@ Line 57: / Line 55: @@
 CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development
 -->
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1308558 #1308558]
 == Detailed Description ==
@@ Line 71: / Line 69: @@
 <!-- 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?-->
-Mono 4.2 is in rawhide now. Most of the application must work fine with this update. See [http://koji.fedoraproject.org/koji/buildinfo?buildID=708832]
+Mono 4.2 is in rawhide now. Most of the application must work fine with this update. See [http://koji.fedoraproject.org/koji/packageinfo?packageID=30]
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 77: / Line 75: @@
 Need check proper build on alternative platforms like ppc64 and s390
-* Release engineering: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: N/A <!-- 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.
 Please work with releng prior to feature submission, and ensure that someone is on board to do any process development work and testing; don't just assume that a bullet point in a change puts someone else on the hook.-->
-** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
-* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines: N/A <!-- 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. -->
-* Trademark approval: N/A (not needed for this Change)
+* Trademark approval: N/A
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
@@ Line 112: / Line 110: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-N/A (not a System Wide Change)
+Interested testers do not need special hardware. Take a given Mono application and test it against the Mono from rawhide or at this copr repo and verify it works:
+ * http://copr.fedoraproject.org/coprs/tpokorra/mono/
+Any issue will be reported in github https://github.com/elsupergomez/lbs-mono-fedora or https://github.com/tpokorra/lbs-mono-fedora
 == User Experience ==
 <!-- 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 -->
-N/A (not a System Wide Change)
+User should note speedy improvement running Mono applications.
 == Dependencies ==
@@ Line 128: / Line 130: @@
 <!-- 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: Keep with Mono 4.0 from F23  <!-- 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. -->
-* Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: Alpha Freeze   <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
+* Blocks product? None <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
 == Documentation ==
@@ Line 150: / Line 152: @@
 -->
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF24]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
 <!-- The Wrangler announces the Change to the devel-announce list and changes the category to Category:ChangeAnnounced (no action required) -->
-<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangePageIncomplete-->
+<!-- After review, the Wrangler will move your page to Category:ChangeReadyForFesco... if it still needs more work it will move back to Category:ChangeReadyForWrangler-->
 <!-- Select proper category, default is Self Contained Change -->
 <!--[[Category:SelfContainedChange]] -->
 [[Category:SystemWideChange]]

Search

Changes/Mono4.2: Difference between revisions