On 23 May 2015 22:20:29 CEST, ToddAndMargo <toddandma...@zoho.com> wrote: >On 05/23/2015 01:10 PM, Jamie Duncan wrote: >> How far back should red hat port fixes? The policy is public and >adhered >> to... > >Hi Jamie, > >They should just follow their word. They state 2020. >Support means support. Freezing all the bugs in >is not support. > >And Red Hat has seemed to have lost interest in 6 >now that they have 7. > >Here is another example: > >"livecd-tools" is horrible. The stick you create refuses >to boot in most computers. The "persistence" is trashed. >There is a 3GB barrier on ext3 partitions. Yada, yada, yada. > >https://bugzilla.redhat.com/show_bug.cgi?id=1220107 > > "I'll make updates for specific problems, but I'm not > going to backport anything to rhel6." > >In other words, don't hold your breath. > >-T
First of all, with bz I actually meant a bugzilla filed in the Red Hat Bugzilla. You need to understand that there is a separation between upstream project bug trackers and the distribution bugtrackers (which isn't even only related to RHEL, it goes for all distributions). Red Hat is most likely be involved in upstream projects of packages they ship. But that doesn't mean that their involvement is instantly seen in RHEL or Fedora. But patches *may* be backported from an upstream project if there is a fix to be found there. If an issue is reported against RHEL, and in particular from paying customers, they often fix the issue and most commonly in _cooperation_ with the upstream project. Once the fix is upstream, it is backported to RHEL. Red Hat's mantra is "upstream first". Sometimes that isn't possible, of course, and then temporary fixes may be implemented until a proper upstream fix can replace the temporary fix. But all this requires that there is a bugzilla which is filed against a specific RHEL release. Otherwise Red Hat may not beware of the issue, as RHEL doesn't have bleeding edge package versions - due to its goal of long term stability. So when you complain about an unfixed issue in qemu in a specific RHEL/SL release and point at the upstream bugtracker, upstream have all rights to say that the EL release is outdated and is fixed in a newer upstream release. But that fix won't hit RHEL until there is a RHEL bugzilla on this issue. That is what triggers a process where Red Hat will evaluate if and how to fix that issue in RHEL. -- kind regards, David Sommerseth
