From Fedora Project Wiki
mNo edit summary
(draft 2)
Line 43: Line 43:
* Other developers:
* Other developers:
** Testing and/or minor fixes of dependant packages
** Testing and/or minor fixes of dependant packages
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
* Release engineering: [https://pagure.io/releng/issues #Releng issue number]
** Separate Koji tag for package rebuild will be needed.
** Separate Koji tag for package rebuild will be needed.
Line 51: Line 50:


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
All existing user binaries built against MPFR 3.1.5 will need to be rebuilt against MPFR 4.0.0.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
* No special hardware / data / etc. is needed.
 
* To test, install mpfr-4.0.0, then rebuild and test existing user binaries.
Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
* Try to locally rebuild your packages with mpfr-4.0.0.
 
* Report failures and other problems to us.
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this change? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the change is
working like it's supposed to?
3. What are the expected results of those actions?
-->
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== User Experience ==
== 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. -->
The MPFR dependent packages should behave as they did with mpfr-3.1.5.
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Dependencies ==
== Dependencies ==
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
    dnf repoquery --whatrequires mpfr
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Contingency Plan ==
== Contingency Plan ==
 
*Contingency mechanism: We would like to get a special buildroot tag to be able to rebuild necessary the packages with Ruby 2.5. If anything goes wrong, the tag could be easily dropped and previous version of Ruby 2.4 and its dependencies stays intact. The tag would be merged into F28 after everything is rebuild.
<!-- 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 deadline: Mass Rebuild
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? No
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Blocks product? No
* Contingency deadline: N/A (not a System Wide Change)  <!-- 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 product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
Documentation can be found upstream at www.mpfr.org/mpfr-4.0.0.
 
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Release Notes ==
== Release Notes ==
Line 114: Line 86:
<!-- 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:ChangePageIncomplete-->


<!-- Select proper category, default is Self Contained Change -->
[[Category:SystemWideChange]]
[[Category:SelfContainedChange]]
<!-- [[Category:SystemWideChange]] -->

Revision as of 16:27, 7 January 2018

mpfr-4.0.0

Summary

Update the MPFR package to version 4.0.0.

Owner

Current status

  • Targeted release: Fedora 28
  • Last updated: 2018-01-07
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The purpose of this change is to update the Fedora MPFR package to the latest version (4.0.0), released on the 25th December 2017. Due to a soname bump, this change will rebuild all packages that depend on MPFR.

Benefit to Fedora

The MPFR team have released many optimisations, bugfixes and features since the current version (3.1.5), released back on the 27th September 2016. This change will allow several important Fedora packages, including the GCC, to take advantage of this.

Refer to http://www.mpfr.org/mpfr-4.0.0/#changes for the complete list of changes.

Scope

  • Proposal owners:
    • Rebuild of packages that depend on MPFR
    • Minor specfile corrections and testing
  • Other developers:
    • Testing and/or minor fixes of dependant packages
  • Release engineering: #Releng issue number
    • Separate Koji tag for package rebuild will be needed.
    • List of deliverables: N/A (not needed for this Change)
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

All existing user binaries built against MPFR 3.1.5 will need to be rebuilt against MPFR 4.0.0.

How To Test

  • No special hardware / data / etc. is needed.
  • To test, install mpfr-4.0.0, then rebuild and test existing user binaries.
  • Try to locally rebuild your packages with mpfr-4.0.0.
  • Report failures and other problems to us.

User Experience

The MPFR dependent packages should behave as they did with mpfr-3.1.5.

Dependencies

   dnf repoquery --whatrequires mpfr

Contingency Plan

  • Contingency mechanism: We would like to get a special buildroot tag to be able to rebuild necessary the packages with Ruby 2.5. If anything goes wrong, the tag could be easily dropped and previous version of Ruby 2.4 and its dependencies stays intact. The tag would be merged into F28 after everything is rebuild.
  • Contingency deadline: Mass Rebuild
  • Blocks release? No
  • Blocks product? No

Documentation

Documentation can be found upstream at www.mpfr.org/mpfr-4.0.0.

Release Notes

Retrieved from "https://fedoraproject.org/w/index.php?title=Changes/mpfr-4.0.2&oldid=508809"