Bug 748184

Summary: ristretto 0.2.0 is available
Product: [Fedora] Fedora Reporter: Christoph Wickert <christoph.wickert>
Component: ristrettoAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ristretto-0.2.0-1.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-25 03:23:27 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:    
Bug Blocks: 748255    

Description Christoph Wickert 2011-10-22 20:19:11 UTC
Latest upstream release: 0.2.0
Current version in Fedora Rawhide: 0.1.1
URL: http://archive.xfce.org/src/apps/ristretto/0.2/

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

Comment 1 Fedora Update System 2011-10-22 20:20:35 UTC
ristretto-0.2.0-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/FEDORA-2011-14586

Comment 2 Christoph Wickert 2011-10-22 20:35:39 UTC
I propose this bug for F16-accepted because the UI in ristretto 0.2.0 has changed, therefor we need to update now or never. An update during the lifecycle of F16 would the user experience and therefor violate our updates policy.

If we do not update, F16 will be excluded from any further upstream updates even before it is released.

Comment 3 Fedora Update System 2011-10-25 03:23:27 UTC
ristretto-0.2.0-1.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.