Bug 806346
Summary: | Update to latest stable version 1.0.x | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Pavel Lisý <pavel.lisy> |
Component: | nginx | Assignee: | Jeremy Hinegardner <jeremy> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | el5 | CC: | affix, jamielinux, jeremy |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-03-23 16:53:18 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: |
Description
Pavel Lisý
2012-03-23 13:57:44 UTC
Updating a major version of a package is, in the vast majority of cases, against the EPEL policy. https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#A_major_version_update "this update should be avoided if possible at all. If there really is no other way out to fix a serious bug then it rare cases it might be acceptable to build the new version for the testing branch and mention the update and the needed adjustments in the release notes for the next update. An additional compat- packages with the old libs is necessary if the ABI changed" Since the 0.8.x branch of nginx is still supported by upstream, I think it is correct to keep it at this level for EPEL 5. Should a critical bug come through nginx that is not fixed in 0.8.x, or if 0.8.x goes out of support then it would be appropriate to update nginx in EPEL 5 to the 1.0.x releases. For instance, if the recent security bug for nginx had not been fixed in 0.8, I would have updated nginx to 1.0.14. -jeremy |