Bug 1474836 - RPM 4.14
RPM 4.14
Product: Fedora
Classification: Fedora
Component: Changes Tracking (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Igor Gnatenko
ChangeAcceptedF27, SystemWideChange
Depends On:
  Show dependency treegraph
Reported: 2017-07-25 09:29 EDT by Jan Kurik
Modified: 2017-08-15 04:40 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Kurik 2017-07-25 09:29:10 EDT
This is a tracking bug for Change: RPM 4.14
For more details, see: https://fedoraproject.org//wiki/Changes/RPM-4.14

Update RPM to the upcoming 4.14 release.
Comment 1 Jan Kurik 2017-08-10 02:18:11 EDT
On 2017-Aug-01, we have reached the Fedora 27 Change Checkpoint: Completion deadline (testable).

At this point, all accepted changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be enabled at Change Completion deadline as well.

Change tracking bug should be set to the MODIFIED state to indicate it achieved completeness.

Incomplete and non testable Changes will be reported to FESCo for 2017-Aug-11 meeting.

Please set this bug to the MODIFIED state to indicate it is already in the testable state, or provide an update describing the current state of implementation for this Change.

Thank you,
Comment 2 Igor Gnatenko 2017-08-10 15:40:49 EDT
We've pushed first 4.14 snapshot an hour ago and rebuilt everything what links into it due to SONAME bump.

So we consider change testable even it's something everyone tests every day :)
Comment 3 Jan Kurik 2017-08-15 04:40:49 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.

Note You need to log in before you can comment on or make changes to this bug.