Bug 1247605

Summary: python-futures-3.0.3 is available
Product: [Fedora] Fedora EPEL Reporter: Alan Pevec <apevec>
Component: python-futuresAssignee: Terje Røsten <terje.rosten>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: extras-qa, terje.rosten, upstream-release-monitoring
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1231408 Environment:
Last Closed: 2015-08-29 10:35:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1231408    
Bug Blocks:    

Description Alan Pevec 2015-07-28 12:21:47 UTC
Please update to futures 3.0 in EPEL7

Scratch build after merging master to epel7 branch worked:
http://koji.fedoraproject.org/koji/taskinfo?taskID=10509921

+++ This bug was initially created as a clone of Bug #1231408 +++

Latest upstream release: 3.0.3
Current version/release in rawhide: 3.0.2-1.fc23
URL: https://github.com/agronholm/pythonfutures

Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy

More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring

Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.

Comment 1 Alan Pevec 2015-07-28 12:25:05 UTC
Required for OpenStack Liberty:
https://review.openstack.org/179967

Comment 2 Terje Røsten 2015-08-29 10:35:26 UTC
Seems to be fixed.