From Fedora Project Wiki
(draft 1)
 
m
Line 42: Line 42:
 
** Minor specfile corrections and testing
 
** Minor specfile corrections and testing
 
* Other developers:
 
* Other developers:
** Packages that depend on MPFR will be automatically rebuilt, but packages may need testing and/or minor tweaks with the new API/ABI.
+
** 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.
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]:
+
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not needed for this Change)
 
* Policies and guidelines: 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)
 
* Trademark approval: N/A (not needed for this Change)

Revision as of 15:34, 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

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